> ## Documentation Index > Fetch the complete documentation index at: https://docs.phare.io/llms.txt > Use this file to discover all available pages before exploring further. # Changelog > Follow the updates and improvements made to the Phare platform in 2026. Private status pages ## 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 datatables ## 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.
Mistral Small 4 model ## 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 ## 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.
Custom region threshold ## 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 and light status page logo ## 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.
List of available ilert alert rules ## 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 ## 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 ## 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. Dark theme status pages ## 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/).
Incident data table of a monitor ## 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.
Terraform provider Phare in beta ## 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 incident updates API endpoints ## 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 project API 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 key ## 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).
Create update and recover incidents using the Phare API ## 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 ## 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.
Monitor SMTP ports ## SMTP ports now available for monitoring SMTP ports can now be monitored like other services over TCP. The usual ports are supported: **25**, **465**, **587**, and **2525**, making it easier to keep an eye on your in-house mail servers.