## Status page timezone
You can now choose the timezone of each status page in its settings. Status pages used to split the availability history into days using UTC, while some dates were displayed in the visitor's timezone, which was confusing and could make incidents appear on a different day than expected.
The selected timezone is now used consistently on RSS / ATOM / Slack feed as well as the status page homepage and incident report page.
## Granular incidents on status pages
The status page availability history has been improved to show incidents more accurately. Instead of coloring the entire daily bar as soon as an incident occurs, each day now displays a marker for its incidents, colored by their impact level. A short degraded performance episode no longer looks like a full day of outage, giving your users a more faithful picture of your service reliability.
## Tags
You can now organize your monitors, incidents and status pages with tags. Tags are free-form labels such as `environment:production`, `server:main` or `priority-1`, defined when creating or editing a resource. They are shared across your whole organization, so the same taxonomy can be reused everywhere, and they are created automatically the first time you use them.
On the dashboard, data-tables now include a **Tags** filter that lets you combine multiple tags to narrow down results. Tags can also be used to filter resources through the API, and are sent in webhooks.
You can now create ICMP monitors to track the availability and latency of your servers, network devices, and infrastructure using ICMP echo requests (ping). Unlike HTTP(S) and TCP checks that require open ports or running services, ICMP checks allow you to monitor host reachability and network health with minimal overhead.
Monitor response time charts now display quantile-based data with **P75**, **P90**, and **P99** percentiles.
While averages can obscure transient latency spikes, quantile distributions give you an accurate view of latency and real-world performance, making it easier to pinpoint intermittent slowdowns and performance degradation.
The billing page has been updated with a new design to clarify current usage and forecast data across your monthly quotas at a glance.
Additionally, the create and edit monitor pages now show a clear estimate of the monitoring events quota required by your monitor configuration. This makes it easy to understand the quota impact of your check interval and selected regions before saving changes.
## Monitor display names on status pages
You can now define a custom **Display name** for each monitor on your status page, allowing you to have technical internal monitor name while keeping your status page user friendly.
## Scheduled maintenance windows
You can now plan and schedule maintenance windows in advance to avoid false alarms, keep your SLA metrics accurate, and more importantly keep your customers informed during planned downtime.
Maintenance windows can be configured with different monitoring mode:
* **Pause**: Halts monitoring checks during the maintenance window so no requests hit your servers.
* **Mute**: Keeps checks running and collects performance data in the background, but suppresses all notification channels to prevent alert fatigue.
* **Normal**: Nothing changes during maintenance windows, you get alerted of incidents as usual.
Maintenance windows can be linked to multiple status page at once to cover advanced use. Public and private status pages now automatically display upcoming notices for maintenance windows.
Explore the new [maintenance windows feature](/uptime/maintenance-windows) to learn more.
## Status pages component groups
You can now organize your monitors into customizable, collapsible groups (such as "API Services" or "Databases") to give visitors a clearer view of system health.
Drag and drop monitors into groups, reorder sections on the fly, and collapse groups directly on your public status pages.
Read the [status pages documentation](/uptime/status-pages) to learn more.
## Private status pages
You can now restrict access to your status pages using three complementary control mechanisms, available on the Scale plan.
### IP allowlist
Grant automatic access to specific IP addresses or CIDR ranges. Requests from listed addresses bypass all other checks, making it the most seamless option for office networks or VPN exit nodes.
### Access token
Append a secret `token` query parameter to any status page URL to grant access, great for programmatic access. Works on the main page, feeds, and badge endpoints. When a browser visits with a valid token, a session cookie is set for 1 hour so subsequent visits don't need the token.
### Access password
Visitors are prompted with a login screen before they can view the page. Simple and effective for internal pages shared with team members or customers.
Read the [status pages access controls documentation](/uptime/status-pages#access-control) to learn more.
## Ordering
It is now possible to order all data-tables on your Phare dashboard.
Order incidents by recovery date, monitors alphabetically, certificates by expiration dates, combined with filtering and text search this allows you to display the data you need for your workflow.
## Updated AI model
Phare updated the AI model used for to generate [incident summary and post-mortems](/uptime/incidents#incident-ai) from Magistral small to Mistral Small.
Mistral Small offers better performance, lower costs, optimized underlying architecture and a jump from 24B to 119B tokens.
## Partial API updates
The [update monitor](/api-reference/uptime/monitors/update-a-monitor) and [update incident](/api-reference/uptime/incidents/update-an-incident) endpoints now accepts partial update. This means you can update only the fields you want to change, leaving the rest unchanged and making the API more practical to use.
Support for more entities will be added in the near future, until all update endpoints support partial payloads.
## Monitor region threshold
Monitor can now individually configure in how many regions they must be detected as down to trigger an incident. This allow you to fine tune your incident detection strategy to your specific needs.
## Support for dark & light status page branding
It is now possible to show different logos and favicons on your status page depending on the theme shown.
## Upgraded ilert integration
You can now forward 5 alert events to your ilert account, and they all got upgraded with way more data than before. The following events are now compatible:
* Incident created
* Incident propagated
* Incident recovered
* Monitor certificate discovered
* Monitor certificate expiring
Checkout the full [ilert documentation](/integrations/ilert) to get started.
## Single region failure detection
When monitoring from multiple regions, incidents were only triggered if at least two regions reported a failure, meaning a real regional outage could go completely undetected. Incidents are now flagged as soon as any single region goes down, regardless of how many regions you're monitoring from.
This change ensures your monitoring coverage actually reflects reality, with zero silent failures.
## 2FA recovery codes
It's now possible to get recovery codes when you have two-factor authentication (2FA) enabled on your account. This will allow you to recover your account if you ever loose access to your 2FA device.
## Status pages got a massive upgrade
Phare’s status pages just received a major upgrade. You can now fully customise the design with adjustable text and background colours, rounded or squared layouts, and flexible border styles to properly match your brand. And more importantly, DARK MODE IS FINALLY HERE, easier on the eyes and long overdue.
There’s now a complete uptime and incident history view, so users can clearly see what happened and when. A new RSS feed also makes it simple to stream real-time updates straight into Slack.
Phare status pages remain in the [top 1% for carbon efficiency with an A+ rating](https://www.websitecarbon.com/website/status-phare-io/).
## Monitor incidents datatable
The monitor page now includes a datatable showing all incidents for that monitor. You can search, filter, and sort incidents directly from the table, making it easier to track and review past issues.
## Official Terraform provider (beta)
Phare now has an official Terraform provider, available in beta. You can manage your projects, monitors, alert rules and status pages directly from your Terraform configuration. This has been one of the most requested features over the last three years, and it’s finally here after a huge amount of work.
Check out the [Terraform documentation](/integrations/terraform) to get started.
## New API endpoints for incident updates
Five new API endpoints are now available to help you manage incident updates through the API:
For organization-scoped API keys:
* [List incident updates](https://docs.phare.io/api-reference/uptime/incidents/updates/list-incident-updates)
* [Get an incident update](https://docs.phare.io/api-reference/uptime/incidents/updates/get-an-incident-update)
* [Create an incident update](https://docs.phare.io/api-reference/uptime/incidents/updates/create-an-incident-update)
* [Update an incident update](https://docs.phare.io/api-reference/uptime/incidents/updates/update-an-incident-update)
* [Delete an incident update](https://docs.phare.io/api-reference/uptime/incidents/updates/delete-an-incident-update)
Check out the [Phare API documentation](https://docs.phare.io/api-reference/introduction) for all available endpoints.
## New API endpoints for project management
Five new API endpoints are now available to help you manage your projects directly through the API:
For organization-scoped API keys:
* [List projects](https://docs.phare.io/api-reference/platform/projects/list-projects)
* [Get a project](https://docs.phare.io/api-reference/platform/projects/get-a-project)
* [Create a project](https://docs.phare.io/api-reference/platform/projects/create-a-project)
* [Update a project](https://docs.phare.io/api-reference/platform/projects/update-a-project)
* [Delete a project](https://docs.phare.io/api-reference/platform/projects/delete-a-project)
Check out the [Phare API documentation](https://docs.phare.io/api-reference/introduction) for all available endpoints.
## Organization-scoped API keys
You can now create organization-scoped API keys. These keys provide access to all projects within your organization and allow full project management, including the ability to create and manage projects.
**Project-scoped API keys** remain available and are still best for setups where projects must stay clearly separated, such as agencies or larger organizations.
**Organization-scoped API keys** are ideal for small teams, startups, and infrastructure provisioning. Most API requests with these keys require a [project selection header](/api-reference/introduction#project-selection).
## New API endpoints for incident management
Three new API endpoints are available to give you more possibilities to automate your incident workflows:
* [Create an Incident](https://docs.phare.io/api-reference/uptime/incidents/create-an-incident)
* [Update an Incident](https://docs.phare.io/api-reference/uptime/incidents/update-an-incident)
* [Recover an Incident](https://docs.phare.io/api-reference/uptime/incidents/recover-an-incident)
Check out the Phare [API documentation](https://docs.phare.io/api-reference/introduction) for all available endpoints.
## More control over incident timing and history
Incidents can now be created with precise start and end times, and existing incidents can be adjusted if the original timing was off. This helps keep status pages accurate when something was detected late or when special circumstances change how an incident should be reported.
It’s also now possible to choose what type of status page update should be published at creation time. This is just a shortcut: all update types can still be posted later if needed.
## Outgoing webhook schema upgrades
Schemas now support loops, and the default schemas for every alert event have been revamped to expose richer data out of the box. The new placeholder syntax uses `{{ entity.property }}` and is documented in the [Outgoing Webhooks docs](/integrations/outgoing-webhook#payload-customization).
## Improved notification preferences
Important organization-level notifications are now sent to all admins, not just the organization owner. In addition, every user can opt out of individual notification types from personal settings.
This removes the single-owner bottleneck while keeping you in control of what lands in your inbox.
## Custom quota notification thresholds
Notification thresholds for billable quotas are now fully configurable. Instead of fixed alerts at 80% and 100%, each quota can trigger notifications at values that actually match how you monitor usage.
This is useful if you want earlier warnings for critical quotas or fewer alerts for ones you don't care about.
## Legal and billing emails per organization
Organizations can now configure separate **Legal** and **Billing** email addresses. The legal email is used for privacy policy and terms of service updates, while the billing email receives invoices and other payment-related notifications.
If your legal and finance departments are actually just you, feel free to send both emails to yourself and role-play.
## Native ilert integration
Phare now integrates natively with [ilert](https://www.ilert.com/?utm_campaign=316508387-Phare%20Uptime\&utm_source=integration\&utm_medium=organic)! Connect your ilert account to receive incident alerts directly in your existing incident management workflow, ensuring your team stays informed and can respond quickly to any issues.
Read more about the [ilert integration](/integrations/ilert) in the documentation.