# Account settings and security Source: https://docs.phare.io/account-settings Update profile preferences, contact details, and two-factor authentication. Account settings are managed from the [user settings](https://app.phare.io/user/settings) page. This page covers preferences, contact details, password updates, and two-factor authentication. > [!NOTE] > > If your organization uses [single sign-on](/user-management#single-sign-on), your email, password, and two-factor authentication are managed by your identity provider. ## Profile preferences Use the preferences section to tailor the dashboard experience: * **Timezone**: Controls how dates and times are displayed. * **Time format**: Toggle between 24h and 12h formats. ## Notification preferences Notification preferences control organization-level email alerts. These notifications are sent to the members who can act on them, so only admins and the owner receive them and see these preferences: * **Quota threshold notifications**: Get alerted when one of your organization’s quota threshold is reached. * **Integration issues notifications**: Get alerted when one of your organization’s integration is experiencing issues. * **Uptime issues notifications**: Get alerted when one of your organization’s uptime resource is experiencing issues. ## Email Update the account email used for alerts and sign-in. A password confirmation step is required when changing the email address. ## Phone number Add a phone number to receive SMS and Voice alerts. A verification code is sent after entry, with options to resend or cancel the verification flow. ## Password Change the account password by entering the current password, a new password, and a confirmation. ## Two-factor authentication Two-factor authentication (TOTP) adds a second step during sign-in. Setup uses a QR code and a confirmation code, with a manual TOTP URI available if needed. Compatible apps include 2FAS, Authy, FreeOTP, and Google Authenticator. # API Introduction Source: https://docs.phare.io/api-reference/introduction Create programmatic interactions with the Phare API. This API lets you interact programmatically with the Phare platform, enabling integration and automation for most tasks available in the control panel. To manage Phare as code you can use the first-party [Terraform provider](/integrations/terraform). ## Create an API key > [!NOTE] > > Only team members with the **Owner** or **Admin** [role](/user-management#roles) can create an API key in your organization. To access the Phare API, create an API key with the right access. This can be done in the [control panel](https://app.phare.io/organization/api-keys). ## Choosing the right scope [https://iframe.mediadelivery.net/embed/238508/67722b0a-5db6-4eb3-88ba-a2f9f574f388?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true](https://iframe.mediadelivery.net/embed/238508/67722b0a-5db6-4eb3-88ba-a2f9f574f388?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true) ### Project-scoped API keys Project-scoped API keys are limited to a single project and are designed for setups where projects must remain clearly separated. They work best for agencies and larger organizations, where each project is owned by a different team. * Access is restricted to one specific project * Cannot create or manage other projects * Cannot manage integrations and organization-wide alert rules, which belong to the whole organization * No additional project headers are required when making API requests ### Organization-scoped API keys Organization-scoped API keys provide access across all projects in an organization and allow full project management. They are well suited for small teams, startups, and infrastructure provisioning. * Access to all projects in the organization * Can create and manage projects * Requires a [project selection header](#project-selection) on most requests ## Permissions Permissions restrict what an API key can do, resource by resource. This helps apply the principle of least privilege and limits what a key can do if it is misused. Each resource can be given one of the following access levels: * **None**: The API key can't access the resource. * **Read**: The API key can list and get the resource. * **Write**: The API key can also create, update and delete the resource. Writing always includes reading. ![API key permissions with None, Read or Write access per resource](https://mintcdn.com/phare/41y9aOGqtf3eXiL4/images/api-reference/api-key-permissions.avif?fit=max\&auto=format\&n=41y9aOGqtf3eXiL4\&q=85\&s=0790e82a05a66398a8fc0fb9fd2d8a44) | Resource | Access levels | Covers | | :- | :- | :- | | Monitors | None, Read, Write | Monitors, their report and SSL certificates | | Reports | None, Read | The uptime report of a project | | Incidents | None, Read, Write | Incidents, their updates and comments, writing includes editing and deleting the ones written by others | | Maintenance windows | None, Read, Write | Maintenance windows, writing includes cancelling and completing them | | Status pages | None, Read, Write | Status pages, their current status and badges | | Projects | None, Read, Write | Projects, writing includes muting them and choosing their members | | Alert rules | None, Read, Write | Alert rules, writing organization-wide alert rules requires an organization-scoped API key | | Integrations | None, Read, Write | The integrations installed in the organization, writing requires an organization-scoped API key | | Members | None, Read | The members of the organization and their pending invites | Each endpoint of this reference names the permission it requires, made of the resource and the access level, like `monitors:read` or `maintenance_windows:write`. When an API key is missing a permission, the API responds with a `403` status code naming the permission required: ```json theme={null} { "message": "The monitors:write permission is required to perform this action." } ``` > [!NOTE] > > You can create as many keys as necessary to fit your use case. ## Authentication The Phare API uses Bearer Token Authentication to secure access to its endpoints. To authenticate your requests, include the API key in the Authorization header of your HTTP requests: ```bash theme={null} Authorization: Bearer YOUR_API_KEY ``` ## Project selection If you're using an organization-scoped API key, every endpoint except `/projects` most endpoints will require you to add an HTTP header to specify which project to operate on. You can specify the project by its `ID` or `Slug`: * **X-Phare-Project-Id**: The project's numeric ID * **X-Phare-Project-Slug**: The project's slug Example using the project slug: ```bash theme={null} curl \ -X GET "https://api.phare.io/uptime/monitors" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "X-Phare-Project-Slug: luminous-guiding-tower" ``` Example using the project ID: ```bash theme={null} curl \ -X GET "https://api.phare.io/uptime/monitors" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "X-Phare-Project-Id: 123" ``` Project-scoped API keys always act on their scoped project and do not require a project selection header. ## Rate limiting Access to the API is currently rate limited to **100 calls per minute** across the organization. All API keys share the same limit. Calls made through the [MCP server](/integrations/mcp) don't count toward this limit, they have [their own](/integrations/mcp#rate-limiting). ## Security Never share your API key publicly. If you suspect that your API key has been compromised, revoke it immediately through your control panel and generate a new one. *** If an API endpoint is missing or a custom rate limit is needed, [contact support](mailto:support@phare.io). Phare can help find a solution that fits the use case. # Create an alert rule Source: https://docs.phare.io/api-reference/platform/alert-rules/create-an-alert-rule post /alert-rules Create an alert rule notifying an integration each time an event happens in the project, or in every project with the `organization` scope. The app of the integration must support the event. Requires the `alert_rules:write` permission. # Delete an alert rule Source: https://docs.phare.io/api-reference/platform/alert-rules/delete-an-alert-rule delete /alert-rules/{alertRuleId} Delete an alert rule by ID, its event stops notifying its integration. The integration is kept. Requires the `alert_rules:write` permission. # Get an alert rule Source: https://docs.phare.io/api-reference/platform/alert-rules/get-an-alert-rule get /alert-rules/{alertRuleId} Get an alert rule by ID, with its event, integration, rate limit and settings. Requires the `alert_rules:read` permission. # List alert rules Source: https://docs.phare.io/api-reference/platform/alert-rules/list-alert-rules get /alert-rules Get a paginated list of the alert rules notifying an integration when an event happens in the project: the project alert rules first, then the organization-wide ones. Requires the `alert_rules:read` permission. # Update an alert rule Source: https://docs.phare.io/api-reference/platform/alert-rules/update-an-alert-rule post /alert-rules/{alertRuleId} Update an alert rule by ID, the fields left out keep their current value. Changing its event or integration replaces their settings, send the settings of the new event or integration. Requires the `alert_rules:write` permission. # Get API info Source: https://docs.phare.io/api-reference/platform/get-api-info get / Get basic API information # Create an integration Source: https://docs.phare.io/api-reference/platform/integrations/create-an-integration post /apps/{app}/integrations Create an integration of an app for the whole organization, then used by alert rules to deliver their notifications. The apps connected from the dashboard, like Slack, Discord and Telegram, cannot be created this way, and the SMS app requires a Scale plan subscription. Requires the `integrations:write` permission. ### Supported apps Only the following apps can be created through the API, each with its own `settings`: | App | `app` key | Settings | | - | - | - | | [Email](/integrations/email) | `email` | `members` | | [ilert](/integrations/ilert) | `ilert` | `integration_key` | | [ntfy](/integrations/ntfy) | `ntfy` | `hostname`, `topic`, `access_token` | | [Outgoing webhook](/integrations/outgoing-webhook) | `outgoing_webhook` | `url`, `secret` | | [Pushover](/integrations/pushover) | `pushover` | `user_key`, `api_key` | | [SMS](/integrations/sms) | `sms` | `members` | > [!NOTE] > > The SMS integration requires a Scale plan subscription. ### Why some apps are not supported Some integrations need a step that can't be done with an API request, so they can only be created from the [control panel](https://app.phare.io/organization/apps): * **Slack** and **Discord**: You need to sign in to Slack or Discord and approve the Phare app in your browser. * **Telegram**: The Phare bot is connected to your chat by opening a link or scanning a QR code on your device. Requests for these apps return a `403` error. Once created in the control panel, they can still be [listed](/api-reference/platform/integrations/list-integrations), [fetched](/api-reference/platform/integrations/get-an-integration), [deleted](/api-reference/platform/integrations/delete-an-integration), and used in [alert rules](/api-reference/platform/alert-rules/create-an-alert-rule) through the API. # Delete an integration Source: https://docs.phare.io/api-reference/platform/integrations/delete-an-integration delete /apps/{app}/integrations/{integrationId} Delete an integration by ID. Integrations used by alert rules cannot be deleted, delete those alert rules or move them to another integration first. Requires the `integrations:write` permission. An integration used by alert rules can't be deleted, delete or update these alert rules first. # Get an integration Source: https://docs.phare.io/api-reference/platform/integrations/get-an-integration get /apps/{app}/integrations/{integrationId} Get an integration of an app by ID. Its credentials are write-only and never returned. Requires the `integrations:read` permission. # List integrations Source: https://docs.phare.io/api-reference/platform/integrations/list-integrations get /apps/{app}/integrations Get a paginated list of the integrations of an app, newest first. Filter them by name. Integrations belong to the organization and deliver the notifications of the alert rules. Requires the `integrations:read` permission. # Update an integration Source: https://docs.phare.io/api-reference/platform/integrations/update-an-integration post /apps/{app}/integrations/{integrationId} Update an integration by ID. The fields and settings left out keep their current value, credentials included. Requires the `integrations:write` permission. > [!WARNING] > > Slack, Discord, and Telegram integrations can only be updated from the control panel, see [why some apps are not supported](/api-reference/platform/integrations/create-an-integration#why-some-apps-are-not-supported). # Create a project Source: https://docs.phare.io/api-reference/platform/projects/create-a-project post /projects Create a project grouping monitors, incidents, maintenance windows, status pages and alert rules, with the users who can access it as members. Requires an organization-scoped API key. Requires the `projects:write` permission. > [!WARNING] > > This endpoint can only be used with an [organization-scoped](/api-reference/introduction#organization-scoped-api-keys) API key. # Delete a project Source: https://docs.phare.io/api-reference/platform/projects/delete-a-project delete /projects/{projectId} Delete a project by ID with everything it contains: monitors with their incidents and check history, maintenance windows, status pages with their custom domain certificates, project alert rules and API keys. This cannot be undone. Requires an organization-scoped API key, and the last project of an organization cannot be deleted. Requires the `projects:write` permission. > [!WARNING] > > This endpoint can only be used with an [organization-scoped](/api-reference/introduction#organization-scoped-api-keys) API key. # Get a project Source: https://docs.phare.io/api-reference/platform/projects/get-a-project get /projects/{projectId} Get a project by ID, with the IDs of its members and its incident settings. Requires the `projects:read` permission. # List projects Source: https://docs.phare.io/api-reference/platform/projects/list-projects get /projects Get a paginated list of the projects you can access, newest first, with the IDs of their members. Requires an organization-scoped API key. Requires the `projects:read` permission. > [!WARNING] > > This endpoint can only be used with an [organization-scoped](/api-reference/introduction#organization-scoped-api-keys) API key. # Update a project Source: https://docs.phare.io/api-reference/platform/projects/update-a-project post /projects/{projectId} Update a project by ID, the fields left out keep their current value. A `members` list replaces the current members. Requires the `projects:write` permission. # Get a user Source: https://docs.phare.io/api-reference/platform/users/get-a-user get /users/{userId} Get a user of the organization by ID, with their email address and role. Requires the `members:read` permission. > [!NOTE] > > All users in the organization can be viewed by project-scoped API keys # List users Source: https://docs.phare.io/api-reference/platform/users/list-users get /users Get a paginated list of the users of the organization, newest first. Filter them by email address to find the user IDs used by the project members and the email and SMS recipients. Requires the `members:read` permission. > [!NOTE] > > All users in the organization can be viewed by project-scoped API keys # Create an incident Source: https://docs.phare.io/api-reference/uptime/incidents/create-an-incident post /uptime/incidents Create a manual incident affecting monitors of the project, for an outage the monitors did not catch. It triggers the `uptime.incident.created` alert rules, unless it is created already recovered with `recovery_at`. Status pages show its title once an incident update is published. Requires the `incidents:write` permission. # Delete an incident Source: https://docs.phare.io/api-reference/uptime/incidents/delete-an-incident delete /uptime/incidents/{incidentId} Delete an incident by ID with its updates, comments and timeline, it disappears from the status pages and the reports. This cannot be undone and triggers no alert rule. Requires the `incidents:write` permission. # Get an incident Source: https://docs.phare.io/api-reference/uptime/incidents/get-an-incident get /uptime/incidents/{incidentId} Get an incident by ID, with its impact, status, state, dates and affected monitors. Requires the `incidents:read` permission. # List incidents Source: https://docs.phare.io/api-reference/uptime/incidents/list-incidents get /uptime/incidents Get a paginated list of the incidents of the project, newest first: the ones opened by failing monitors and the manual ones. Filter them by monitor or tag. Requires the `incidents:read` permission. # Recover an incident Source: https://docs.phare.io/api-reference/uptime/incidents/recover-an-incident post /uptime/incidents/{incidentId}/recover Recover an ongoing incident by ID, setting its recovery date to the current date, and trigger the `uptime.incident.recovered` alert rules. Requires the `incidents:write` permission. # Update an incident Source: https://docs.phare.io/api-reference/uptime/incidents/update-an-incident post /uptime/incidents/{incidentId} Update an incident by ID, the fields left out keep their current value. A `monitors` list replaces the affected monitors of a manual incident and is ignored on the incidents opened by monitors. Setting `recovery_at` on an ongoing incident recovers it and triggers the `uptime.incident.recovered` alert rules, and the changes are logged in its timeline. Requires the `incidents:write` permission. # Create an incident update Source: https://docs.phare.io/api-reference/uptime/incidents/updates/create-an-incident-update post /uptime/incidents/{incidentId}/updates Publish an update of an incident on the status pages and trigger the `uptime.incident_update.published` alert rules. Its state raises the state of the incident, and the `resolved` state recovers an ongoing incident. Requires the `incidents:write` permission. # Delete an incident update Source: https://docs.phare.io/api-reference/uptime/incidents/updates/delete-an-incident-update delete /uptime/incidents/{incidentId}/updates/{incidentUpdateId} Delete an incident update by ID, it disappears from the status pages and the state of the incident is recalculated, a recovered incident stays recovered. Only its author or a user with the `incidents:moderate` permission can delete it. Requires the `incidents:write` permission. # Get an incident update Source: https://docs.phare.io/api-reference/uptime/incidents/updates/get-an-incident-update get /uptime/incidents/{incidentId}/updates/{incidentUpdateId} Get an incident update by ID, with its state, message, publication date and author. Requires the `incidents:read` permission. # List incident updates Source: https://docs.phare.io/api-reference/uptime/incidents/updates/list-incident-updates get /uptime/incidents/{incidentId}/updates Get a paginated list of the updates of an incident, the messages published on the status pages, newest first. Requires the `incidents:read` permission. # Update an incident update Source: https://docs.phare.io/api-reference/uptime/incidents/updates/update-an-incident-update post /uptime/incidents/{incidentId}/updates/{incidentUpdateId} Update the state and message of an incident update by ID, the state of the incident is recalculated. Its publication date cannot be changed, no alert rule is triggered and the `resolved` state does not recover the incident. Only its author or a user with the `incidents:moderate` permission can update it. Requires the `incidents:write` permission. # Cancel a maintenance window Source: https://docs.phare.io/api-reference/uptime/maintenance-windows/cancel-a-maintenance-window post /uptime/maintenance-windows/{maintenanceWindowId}/cancel Cancel a scheduled or in-progress maintenance window by ID and trigger the `uptime.maintenance_window.cancelled` alert rules, the monitors it paused are resumed. Completed or already cancelled maintenance windows cannot be cancelled. Requires the `maintenance_windows:write` permission. ### Lifecycle & State Requirements Only maintenance windows in the `scheduled` or `in_progress` state can be cancelled. Trying to cancel a maintenance window in a different state will return a `403 Forbidden` response. ### What happens on cancellation? When a maintenance window is cancelled: 1. The maintenance window state changes to `cancelled`. 2. If the window was `in_progress` with `pause` monitoring mode, attached monitors are immediately resumed. Unless they were already paused before the start of the maintenance window, or an overlapping maintenance window with `pause` monitoring mode is still ongoing. 3. Connected status pages are updated immediately to remove upcoming or active maintenance announcements. 4. The `uptime.maintenance_window.cancelled` alert event is dispatched to any configured alert rules. # Complete a maintenance window Source: https://docs.phare.io/api-reference/uptime/maintenance-windows/complete-a-maintenance-window post /uptime/maintenance-windows/{maintenanceWindowId}/complete Complete an in-progress maintenance window by ID and trigger the `uptime.maintenance_window.completed` alert rules, the monitors it paused are resumed and `ends_at` is set to the current time if it is in the future. Only in-progress maintenance windows can be completed. Requires the `maintenance_windows:write` permission. ### Lifecycle & State Requirements Only maintenance windows in the `in_progress` state can be marked as completed. Trying to complete a maintenance window in a different state will return a `403 Forbidden` response. ### What happens on completion? When a maintenance window is marked as completed: 1. The window state changes to `completed`. 2. Any monitors attached to the window that were paused (when using the `pause` monitoring mode) are automatically resumed. Unless they were already paused before the start of the maintenance window, or an overlapping maintenance window with `pause` monitoring mode is still ongoing. 3. Connected status pages are updated immediately to remove upcoming or active maintenance announcements. 4. The `uptime.maintenance_window.completed` alert event is dispatched to any configured alert rules. # Create a maintenance window Source: https://docs.phare.io/api-reference/uptime/maintenance-windows/create-a-maintenance-window post /uptime/maintenance-windows Schedule a maintenance window for monitors of the project, shown right away on the linked status pages. It starts at `starts_at` and ends at `ends_at` on its own, and its `monitoring_mode` sets what happens to the monitors meanwhile: `pause` pauses them, `mute` keeps checking them without incident alerts, `normal` only announces the maintenance. Requires the `maintenance_windows:write` permission. ### Monitoring modes Choose how monitoring checks and alert notifications should behave during maintenance: * **`pause`**: Pauses all checks on attached monitors. No incidents are created, keeping your SLA and uptime metrics intact. Paused monitors are automatically resumed when the window ends. * **`mute`**: Keeps running checks in the background to record telemetry and latency data, but silences all alert notifications (e.g. Slack, email, SMS). * **`normal`**: Checks and alerts operate as usual, but the maintenance window is announced on connected status pages. ### Timings & Format * **`starts_at`**: Must be formatted in ISO 8601 with minute precision (e.g. `2026-09-05T14:30:00Z`). Seconds must be set to `:00`. Must be greater than or equal to the current time and within 1 year. * **`ends_at`**: Must be after `starts_at` and within 1 year. # Delete a maintenance window Source: https://docs.phare.io/api-reference/uptime/maintenance-windows/delete-a-maintenance-window delete /uptime/maintenance-windows/{maintenanceWindowId} Delete a maintenance window by ID in any state, it disappears from the status pages and the monitors it paused are resumed. This cannot be undone and triggers no alert rule. Requires the `maintenance_windows:write` permission. # Get a maintenance window Source: https://docs.phare.io/api-reference/uptime/maintenance-windows/get-a-maintenance-window get /uptime/maintenance-windows/{maintenanceWindowId} Get a maintenance window by ID, with its state, schedule, monitoring mode, monitors and status pages. Requires the `maintenance_windows:read` permission. # List maintenance windows Source: https://docs.phare.io/api-reference/uptime/maintenance-windows/list-maintenance-windows get /uptime/maintenance-windows Get a paginated list of the maintenance windows of the project, newest first. Filter them by state, monitor, status page or tag. Requires the `maintenance_windows:read` permission. # Update a maintenance window Source: https://docs.phare.io/api-reference/uptime/maintenance-windows/update-a-maintenance-window post /uptime/maintenance-windows/{maintenanceWindowId} Update a maintenance window by ID. The `monitoring_mode`, `starts_at`, `ends_at`, `monitors` and `status_pages` fields can only be modified while the maintenance window is scheduled, except for `ends_at` which can be extended while the maintenance window is in progress. Requires the `maintenance_windows:write` permission. ### State-specific mutability rules Depending on the current state of the maintenance window, certain fields cannot be modified: * **`scheduled`**: All fields can be updated. * **`in_progress`**: You can update `title`, `description`, and extend `ends_at` (must be greater than or equal to the current `ends_at`). The `starts_at` date, `monitoring_mode`, `monitors`, and `status_pages` cannot be changed while maintenance is ongoing. * **`completed` / `cancelled`**: Only `title` and `description` can be modified (for example, to add post-maintenance notes). Timings, monitoring mode, and attached monitors/status pages cannot be changed. # Create a monitor Source: https://docs.phare.io/api-reference/uptime/monitors/create-a-monitor post /uptime/monitors Create an HTTP, TCP or ICMP monitor checking a service at a regular interval from 1 to 10 regions, it opens an incident once the failures are confirmed. The first check runs right away when the organization has monitoring events left in its quota, and the `uptime.monitor.created` alert rules are triggered. Requires the `monitors:write` permission. # Delete a monitor Source: https://docs.phare.io/api-reference/uptime/monitors/delete-a-monitor delete /uptime/monitors/{monitorId} Delete a monitor by ID with its check history, its status page components, and the incidents and maintenance windows of this monitor only, the ones shared with other monitors are kept. This cannot be undone, and triggers the `uptime.monitor.deleted` alert rules. Requires the `monitors:write` permission. # Get a monitor Source: https://docs.phare.io/api-reference/uptime/monitors/get-a-monitor get /uptime/monitors/{monitorId} Get a monitor by ID, with its current status, response time, request settings and check regions. Requires the `monitors:read` permission. # Get a monitor report Source: https://docs.phare.io/api-reference/uptime/monitors/get-a-monitor-report get /uptime/monitors/{monitorId}/report Get the availability, downtime, incident count, MTTR and MTBF of a monitor by ID, with its incidents, between two past dates up to 1 year apart, the last 30 days by default. Requires the `monitors:read` permission. > [!NOTE] > > To get an uptime report for all monitors in a project check out the [Reports](/api-reference/uptime/reports/get-a-report) endpoint # List monitors Source: https://docs.phare.io/api-reference/uptime/monitors/list-monitors get /uptime/monitors Get a paginated list of the monitors of the project, newest first, with their current status and response time. Filter them by tag. Requires the `monitors:read` permission. # Pause a monitor Source: https://docs.phare.io/api-reference/uptime/monitors/pause-a-monitor post /uptime/monitors/{monitorId}/pause Pause a monitor by ID, its checks stop until it is resumed. Its ongoing incidents stay open. Requires the `monitors:write` permission. # Resume a monitor Source: https://docs.phare.io/api-reference/uptime/monitors/resume-a-monitor post /uptime/monitors/{monitorId}/resume Resume a paused monitor by ID, its checks start again and the next one runs right away when the last one is older than its interval. Requires the `monitors:write` permission. # Update a monitor Source: https://docs.phare.io/api-reference/uptime/monitors/update-a-monitor post /uptime/monitors/{monitorId} Update a monitor by ID, the fields left out keep their current value and the ones sent replace it entirely, like the whole `request` object. A check runs right away when the organization has monitoring events left in its quota, and the changes are logged in the timeline of its ongoing incidents. Requires the `monitors:write` permission. # Get report Source: https://docs.phare.io/api-reference/uptime/reports/get-a-report get /uptime/reports Get the availability, downtime, incident count, MTTR and MTBF of every monitor of the project and their aggregates, between two past dates up to 1 year apart, the last 30 days by default. Requires the `reports:read` permission. > [!NOTE] > > To get an uptime report for a particular monitors check out the [Monitor report](/api-reference/uptime/monitors/get-a-monitor-report) endpoint # Create a status page Source: https://docs.phare.io/api-reference/uptime/status-pages/create-a-status-page post /uptime/status-pages Create a public status page showing monitors of the project, online right away at `{subdomain}.status.phare.io`. A custom domain needs a CNAME record pointing to `cname.status.phare.io`, its SSL certificate is then issued automatically. Logos and favicons can only be uploaded with a `multipart/form-data` request. Requires the `status_pages:write` permission. # Delete a status page Source: https://docs.phare.io/api-reference/uptime/status-pages/delete-a-status-page delete /uptime/status-pages/{statusPageId} Delete a status page by ID with its components and custom domain certificate, it goes offline right away. The monitors, incidents and maintenance windows it showed are kept. This cannot be undone. Requires the `status_pages:write` permission. # Get a status page Source: https://docs.phare.io/api-reference/uptime/status-pages/get-a-status-page get /uptime/status-pages/{statusPageId} Get the settings of a status page by ID, with its components. The status it shows is returned by its current status. Requires the `status_pages:read` permission. # Get a status page current status Source: https://docs.phare.io/api-reference/uptime/status-pages/get-a-status-page-current-status get /uptime/status-pages/{statusPageId}/current-status Get what a status page shows right now: the impact of its active incidents or maintenance, its availability over its timeframe, the status of each component and its published active incidents. Requires the `status_pages:read` permission. # List status pages Source: https://docs.phare.io/api-reference/uptime/status-pages/list-status-pages get /uptime/status-pages Get a paginated list of the status pages of the project, newest first, with their components. Filter them by tag. Requires the `status_pages:read` permission. # Update a status page Source: https://docs.phare.io/api-reference/uptime/status-pages/update-a-status-page post /uptime/status-pages/{statusPageId} Update a status page by ID, the fields left out keep their current value. A `components` list replaces the current components, and a new `domain` replaces its custom domain certificate, issued automatically once the domain has a CNAME record pointing to `cname.status.phare.io`. Logos and favicons can only be uploaded with a `multipart/form-data` request. Requires the `status_pages:write` permission. # Billing and quotas Source: https://docs.phare.io/billing-quotas Track usage, manage quotas, and review plan details. Plan details and current pricing live on the [pricing page](https://phare.io/pricing). ## Quota types Phare tracks usage with the following quotas: | Quota | Description | | :- | :- | | Monitoring events | Number of HTTP, TCP and ICMP ping checks you can use each month, usage depends on your monitoring strategy. | | AI generations | Number of AI incident summaries and postmortem that you can generate each month. | | SMS / Voice alerts | Number of SMS or Voice alert that you can receive each month. | ## Usage and quotas ![Phare billing dashboard](https://mintcdn.com/phare/fzCvvHJOL_TypLyp/images/billing-quotas/phare-billing.avif?fit=max\&auto=format\&n=fzCvvHJOL_TypLyp\&q=85\&s=78ad97090294be1ae59ce7e46f9b1a21) The billing page shows live usage for the current billing period, with data updated every hour. Each quota displays: * **Included quota**: Usage included with the plan. * **Additional quota**: Optional limits that can be added on paid plans. * **Free overage (+10%)**: A buffer shown in the usage view. * **Forecast**: A projected usage marker for the current period. ## Additional quotas Additional quotas act as an upper limit for the invoice. Unused quota is not billed, and limits can be adjusted at any time. Additional quotas are available on the Scale plan. The Hobby plan does not include additional usage. ## Billing portal The billing portal provides subscription management, payment method updates, and access to past invoices. It is managed by Paddle, Phare's payment provider. # Changelog Source: https://docs.phare.io/changelog Follow the updates and improvements made to the Phare platform in 2026. **Nov 9, 2026** ## Encrypted monitor headers and integration credentials ![Monitor user agent secret and headers, with an encrypted Authorization header value](https://mintcdn.com/phare/UN6YNHMj1Kp4iWhS/images/changelog/143-encrypted-monitor-headers.avif?fit=max\&auto=format\&n=UN6YNHMj1Kp4iWhS\&q=85\&s=b689b2039f785a97bdb4b11613c189f4) You can now choose to encrypt the value of a monitor header, keeping your `Authorization` token or an API key secret. An encrypted value is never shown again once saved, not in the dashboard, the API, the MCP, or the alert payloads. The user agent secret and the credentials of your integrations, such as the ntfy access token, the Pushover keys, the ilert integration key and the outgoing webhook signing secret, are now encrypted the same way and similarly hidden from the API, MCP or any other payloads. Existing known headers, named like usual credentials, such as `Authorization`, `X-API-Key` or `Cookie`, were encrypted automatically. Check your monitors to lock the other headers that hold a secret. Check out the [monitors documentation](/uptime/monitors#encrypted-headers) for more details. **Nov 5, 2026** ## Viewer and Responder roles ![Member role selection with the Viewer, Responder, Member and Admin roles](https://mintcdn.com/phare/41y9aOGqtf3eXiL4/images/changelog/142-viewer-and-responder-roles.avif?fit=max\&auto=format\&n=41y9aOGqtf3eXiL4\&q=85\&s=2e89357799528493c77498766be7c516) Two new roles are available to give your team the access it needs, no more and no less: * **Viewer**: read-only access to every resource of their projects, perfect for stakeholders and support teams following an outage. * **Responder**: viewer, and manage incidents, their updates and comments, and maintenance windows. Ideal for on-call engineers who communicate during an incident without touching the monitoring configuration. Check out the [user management documentation](/user-management#roles) for the permissions of each role. **Nov 5, 2026** ## Granular API key permissions ![API key permissions with None, Read or Write access per resource](https://mintcdn.com/phare/41y9aOGqtf3eXiL4/images/changelog/141-api-key-permissions.avif?fit=max\&auto=format\&n=41y9aOGqtf3eXiL4\&q=85\&s=882fc97d76bbdbb4fbc06b6653548749) API keys can now be restricted resource by resource instead of product by product. Monitors, reports, incidents, maintenance windows, status pages, projects, alert rules, integrations and members each get their own **None**, **Read** or **Write** access. Existing API keys were converted to the new permissions and keep the same access. Check out the [API documentation](/api-reference/introduction#permissions) to choose the right permissions for your keys. **Nov 1, 2026** ## New Phare design ![New Phare design](https://mintcdn.com/phare/fzCvvHJOL_TypLyp/images/changelog/140-new-phare-design.avif?fit=max\&auto=format\&n=fzCvvHJOL_TypLyp\&q=85\&s=ddbe0aedb21af61183f0b5fca1fdc3ca) The Phare website and brand got a makeover. It's quite a big change, and I hope you'll like the new direction: more mature and more playful at the same time. The logo and fonts also changed slightly, most of the dashboard is unchanged, so you'll still feel at home ;) **Oct 25, 2026** ## Single sign-on ![Single sign-on](https://mintcdn.com/phare/fzCvvHJOL_TypLyp/images/changelog/139-single-sign-on.avif?fit=max\&auto=format\&n=fzCvvHJOL_TypLyp\&q=85\&s=afaca8ba6c62e27254bdc5f101b45528) You can now let your members log in to Phare with the identity provider of your organization through OpenID Connect. Single sign-on is available on the Scale plan, and works with Okta, Microsoft Entra ID, Google Workspace, Auth0, JumpCloud, OneLogin, Keycloak, authentik, ZITADEL and any other OpenID Connect identity provider. Check out the [single sign-on documentation](/user-management#single-sign-on) to set it up with your identity provider. **Oct 11, 2026** ## New API endpoints for integration management Three new API endpoints are now available to manage your integrations directly through the API: * [Create an integration](/api-reference/platform/integrations/create-an-integration) * [Update an integration](/api-reference/platform/integrations/update-an-integration) * [Delete an integration](/api-reference/platform/integrations/delete-an-integration) Email, ilert, ntfy, outgoing webhook, Pushover and SMS integrations are supported. Slack, Discord and Telegram integrations require an authorization step in your browser or on your device, so they can only be created from the dashboard. Check out the [Phare API documentation](/api-reference/introduction) for all available endpoints. **Oct 10, 2026** ## Status page timezone ![Status page timezone selection](https://mintcdn.com/phare/NPVinYjksH4L2cnQ/images/changelog/138-status-page-timezone.avif?fit=max\&auto=format\&n=NPVinYjksH4L2cnQ\&q=85\&s=b13ec741df9aaf14e634da939af52bc5) 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. **Oct 9, 2026** ## Granular incidents on status pages ![Status page availability history with granular incident markers](https://mintcdn.com/phare/31Zq9Rz_lZlpupDF/images/changelog/137-status-page-granular-incidents.avif?fit=max\&auto=format\&n=31Zq9Rz_lZlpupDF\&q=85\&s=2637c20fbfcfe04ba2aec3e570d3a21b) 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. **Oct 6, 2026** ## Tags ![Resource tagging](https://mintcdn.com/phare/JR-7YFU4XYCVaUrW/images/changelog/136-tags.avif?fit=max\&auto=format\&n=JR-7YFU4XYCVaUrW\&q=85\&s=8fc14c7fa30ec386e856fb4913d0a9ee) 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. **Sep 30, 2026** ## ICMP monitoring ![Uptime monitoring with ICMP ping](https://mintcdn.com/phare/nw70bdsbHq3m9M7W/images/changelog/135-icmp-monitoring.avif?fit=max\&auto=format\&n=nw70bdsbHq3m9M7W\&q=85\&s=91491a95e9c7b8ea8af86ebc7e328458) 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. **Sep 28, 2026** ## Quantile-based monitoring charts ![Uptime monitoring performance chart with quantile filters](https://mintcdn.com/phare/PVzsxFZn_BU8xfvc/images/changelog/134-quantile-monitoring-chart.avif?fit=max\&auto=format\&n=PVzsxFZn_BU8xfvc\&q=85\&s=e3cfb992c78c0348cbcdf96dbbf6f6da) 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. **Sep 28, 2026** ## Redesigned billing and monitor quota estimation ![Billing dashboard showing current and forecasted uptime monitoring usage](https://mintcdn.com/phare/PVzsxFZn_BU8xfvc/images/changelog/132-new-billing-dashboard.avif?fit=max\&auto=format\&n=PVzsxFZn_BU8xfvc\&q=85\&s=9a8ddb0946b220f8ca7de7fdaaa7d84d) The billing page has been updated with a new design to clarify current usage and forecast data across your monthly quotas at a glance. ![Monitoring events quota review when creating or updating a monitor](https://mintcdn.com/phare/PVzsxFZn_BU8xfvc/images/changelog/133-monitor-usage-review.avif?fit=max\&auto=format\&n=PVzsxFZn_BU8xfvc\&q=85\&s=0dcd156835240f5c5f6c7525d6246ad1) 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. **Sep 13, 2026** ![Status page monitor display name](https://mintcdn.com/phare/BOt4tdJU9XP0KPro/images/changelog/131-status-page-display-name.avif?fit=max\&auto=format\&n=BOt4tdJU9XP0KPro\&q=85\&s=7990473cf7523544f01f1ddb99f25887) ## 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. **Sep 13, 2026** ## Hide response times on status pages Status pages display the 75th percentile (P75) response time over the last 7 days next to each monitor by default. You can now toggle off **Response times** in your status page settings to hide them completely. **Aug 30, 2026** ![Maintenance windows](https://mintcdn.com/phare/fzCvvHJOL_TypLyp/images/changelog/130-maintenance-windows.avif?fit=max\&auto=format\&n=fzCvvHJOL_TypLyp\&q=85\&s=1eac63c26e67ecebeba0da8e1b95c5d8) ## 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. **Jul 30, 2026** ![Status page component groups](https://mintcdn.com/phare/johGXle6KHzsYkqJ/images/changelog/129-status-page-component-groups.avif?fit=max\&auto=format\&n=johGXle6KHzsYkqJ\&q=85\&s=e4f1a4dbc4aa3988e581a372a5fbdaca) ## 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. **Jun 12, 2026** ## Data processing agreement (DPA) A formal Data Processing Agreement (DPA) is now publicly available to help customers meet GDPR compliance requirements when using Phare without having to submit a formal request. Read the full [Data Processing Agreement](https://phare.io/legal/data-processing-agreement) to learn more. **May 17, 2026** ![Private status pages](https://mintcdn.com/phare/PCGQBvexy0-vi11C/images/changelog/128-private-status-pages.avif?fit=max\&auto=format\&n=PCGQBvexy0-vi11C\&q=85\&s=cdd148935c418b40a9ad46a51cd4ad8c) ## 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. **May 3, 2026** ![Ordering datatables](https://mintcdn.com/phare/Z-AeAUsJcqAet-w4/images/changelog/127-ordering.avif?fit=max\&auto=format\&n=Z-AeAUsJcqAet-w4\&q=85\&s=31fc451429be819ad935ef99e9d360b9) ## 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. **May 3, 2026** ![Mistral Small 4 model](https://mintcdn.com/phare/Z-AeAUsJcqAet-w4/images/changelog/126-mistral-small-4.avif?fit=max\&auto=format\&n=Z-AeAUsJcqAet-w4\&q=85\&s=db451c660a1d2f95859f2211a768c831) ## 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. **Apr 6, 2026** ![Partial API updates](https://mintcdn.com/phare/KTiOfLopTTHS8nmi/images/changelog/125-partial-api-update.avif?fit=max\&auto=format\&n=KTiOfLopTTHS8nmi\&q=85\&s=5c0f574bd9ac792f9aa94081f49f2c5f) ## 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. **Apr 6, 2026** ![Custom region threshold](https://mintcdn.com/phare/KTiOfLopTTHS8nmi/images/changelog/124-region-threshold.avif?fit=max\&auto=format\&n=KTiOfLopTTHS8nmi\&q=85\&s=8cde85c1cccea17218f5ca6cddf53095) ## 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. **Mar 27, 2026** ![Support for dark and light status page logo](https://mintcdn.com/phare/CjZad_C4z-Me8PfK/images/changelog/123-dark-light-logo.avif?fit=max\&auto=format\&n=CjZad_C4z-Me8PfK\&q=85\&s=86c0662b4cab3a62829e5648cdaef4f2) ## 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. **Mar 16, 2026** ![List of available ilert alert rules](https://mintcdn.com/phare/mCut4ZkBgx6c8dX9/images/changelog/122-upgraded-ilert.avif?fit=max\&auto=format\&n=mCut4ZkBgx6c8dX9\&q=85\&s=fe0b6a1a713a191e46ee153fa0f27bba) ## 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. **Mar 16, 2026** ![Single region failure](https://mintcdn.com/phare/mCut4ZkBgx6c8dX9/images/changelog/121-single-region-failure.avif?fit=max\&auto=format\&n=mCut4ZkBgx6c8dX9\&q=85\&s=ba4eae0fdfd0c76fd698a0ec6c4e139f) ## 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. **Mar 7, 2026** ![2fa recovery codes](https://mintcdn.com/phare/ArhfbdYE4ZurYdya/images/changelog/120-2fa-recovery-codes.avif?fit=max\&auto=format\&n=ArhfbdYE4ZurYdya\&q=85\&s=4edf6b7ea21fcececb2ded49c6c49b4c) ## 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. **Feb 28, 2026** ![Dark theme status pages](https://mintcdn.com/phare/u79Zh--bFbMNPbDG/images/changelog/119-dark-status-pages.avif?fit=max\&auto=format\&n=u79Zh--bFbMNPbDG\&q=85\&s=25fa376228e9dafb22c9b879e2357f9e) ## 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/). **Feb 25, 2026** ![Incident data table of a monitor](https://mintcdn.com/phare/sDNDrkFr89fJLUCi/images/changelog/118-uptime-monitor-incidents.avif?fit=max\&auto=format\&n=sDNDrkFr89fJLUCi\&q=85\&s=5221e680bdb048c338ef06a38dacdeda) ## 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. **Feb 22, 2026** ![Terraform provider Phare in beta](https://mintcdn.com/phare/EY08_wLCD7Kd1oAM/images/changelog/117-terraform-provider-phare-beta.avif?fit=max\&auto=format\&n=EY08_wLCD7Kd1oAM\&q=85\&s=7a2a520e44c15bc88408e9ca9fede006) ## 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. **Feb 22, 2026** ![New incident updates API endpoints](https://mintcdn.com/phare/6Yn35VSGUzYNqMu7/images/changelog/116-incident-updates-endpoints.avif?fit=max\&auto=format\&n=6Yn35VSGUzYNqMu7\&q=85\&s=eeb09cde16e791c59ffab194c1a56ec8) ## 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. **Feb 8, 2026** ![New project API endpoints](https://mintcdn.com/phare/8AzwksM7vEumg-KK/images/changelog/115-projects-api-endpoints.avif?fit=max\&auto=format\&n=8AzwksM7vEumg-KK\&q=85\&s=8b48ef426230b41c2cc6c1e216e5ff4e) ## 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. **Feb 8, 2026** ![Organization scoped API key](https://mintcdn.com/phare/7Dj278i2kJPWdWm0/images/changelog/114-organization-scoped-api-key.avif?fit=max\&auto=format\&n=7Dj278i2kJPWdWm0\&q=85\&s=6d843e2168cfaedccfb9442db456efad) ## 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). **Feb 8, 2026** ![Create update and recover incidents using the Phare API](https://mintcdn.com/phare/nXCeT7_kcimDDEyw/images/changelog/112-incidents-write-api.avif?fit=max\&auto=format\&n=nXCeT7_kcimDDEyw\&q=85\&s=8e8ce58971a213dfaac8783940a0d100) ## 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. **Feb 4, 2026** ![More control over incident timing](https://mintcdn.com/phare/JTNyCVKzXHIHP2Wx/images/changelog/111-incident-timing.avif?fit=max\&auto=format\&n=JTNyCVKzXHIHP2Wx\&q=85\&s=c9d297fce728bd1a9db3d6cd2be92a66) ## 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. **Jan 26, 2026** ![Monitor SMTP ports](https://mintcdn.com/phare/nXCeT7_kcimDDEyw/images/changelog/113-monitor-smtp-ports.avif?fit=max\&auto=format\&n=nXCeT7_kcimDDEyw\&q=85\&s=a0b6b0fc28cc203b00a9c3da2806a2c5) ## 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. **Jan 25, 2026** [https://player.mediadelivery.net/embed/238508/4147abf7-d8ef-4c1d-95fb-b86b949b2a43?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true](https://player.mediadelivery.net/embed/238508/4147abf7-d8ef-4c1d-95fb-b86b949b2a43?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true) ## Improved webhook JSON editor The JSON editor to customize outgoing webhook payloads now highlights valid placeholders and loop names, warns on invalid tokens, and suggests available entities and properties as you type. Editing is smoother too: new lines are pre-filled, error handling is clearer, and the editor can expand for large schemas. It's like a small handcrafted IDE inside Phare 🌞 **Jan 25, 2026** ![New outgoing webhook JSON schema](https://mintcdn.com/phare/zLLzjjr1e4DRld1u/images/changelog/110-new-webhook-schema.avif?fit=max\&auto=format\&n=zLLzjjr1e4DRld1u\&q=85\&s=59d8fc2987f13c590253d5064043aa2a) ## 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). **Jan 13, 2026** ![Custom quota notification thresholds](https://mintcdn.com/phare/gMkTXk_uDeR48BoQ/images/changelog/109-notification-preferences.avif?fit=max\&auto=format\&n=gMkTXk_uDeR48BoQ\&q=85\&s=435570f767fbb778ba60aa91be0adf0e) ## 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. **Jan 13, 2026** ![Custom quota notification thresholds](https://mintcdn.com/phare/gMkTXk_uDeR48BoQ/images/changelog/108-custom-quota-thresholds.avif?fit=max\&auto=format\&n=gMkTXk_uDeR48BoQ\&q=85\&s=e111f1ebed7c0890e517e43d8ee8c1cb) ## 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. **Jan 13, 2026** ![Custom legal and billing emails](https://mintcdn.com/phare/gMkTXk_uDeR48BoQ/images/changelog/107-custom-organization-emails.avif?fit=max\&auto=format\&n=gMkTXk_uDeR48BoQ\&q=85\&s=0ff1c731bcca6e545aac188feeed89cb) ## 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. **Jan 11, 2026** ![ilert integration](https://mintcdn.com/phare/NFIZ2S5Md_Iexi6t/images/changelog/106-ilert-integration.webp?fit=max\&auto=format\&n=NFIZ2S5Md_Iexi6t\&q=85\&s=ed604cff2cce8b32714bc6fcd2ea81b2) ## 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. # Changelog of 2023 Source: https://docs.phare.io/changelog/2023 Follow the updates and improvements made to the Phare platform in 2023. **Dec 17, 2023** ## Alert policy duplication You can now duplicate an entire alert policy with all its rules to adapt Phare to how your company needs to be alerted. [https://iframe.mediadelivery.net/embed/238508/0bb0e17c-909b-4b22-9889-0216cab8ccbf?autoplay=true\&loop=true\&muted=true\&preload=true\&responsive=true](https://iframe.mediadelivery.net/embed/238508/0bb0e17c-909b-4b22-9889-0216cab8ccbf?autoplay=true\&loop=true\&muted=true\&preload=true\&responsive=true) **Nov 4, 2023** ## Status pages RSS and ATOM feed Status pages now offer an incident feed in RSS and ATOM format to let your users get updates on incidents. **Nov 2, 2023** ## Status pages brand logo and feed subscription You can now add your brand logo to your status page, which will be displayed in the top left corner of the page. Current and past incidents are now shown on the status page, and your users can subscribe to an RSS or Atom feed to get updates on incidents. ![Status Page branding](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/37-status-page-branding.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=560253171739f59e24f0f6d867779466) **Oct 29, 2023** ## Incident comments To help you resolve incidents faster, project members can now comment on the incident timeline. Comments can be written using a rich text editor, and are compatible with the Markdown syntax. ![Incident impact & comments](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/36-incident-impact-and-comments.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=b0da53e5bf33ef7869e20c3f48922924) **Oct 27, 2023** ## Incident impact The design of the incident management page has been improved, with all actions now part of the timeline. You can now select an impact level for your incidents. ![Incident management](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/35-incident-management.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=9ba2505eded738c7193f278350d5ec98) **Oct 23, 2023** ## Admin user role A new **Admin** role is now available. This role is similar to the former **Owner** role, with the exception that it can't delete the organization, making it easier to share the management of an organization with other team members. You can review the available permissions of each role in the [user management documentation](https://docs.phare.io/user-management). Role can be modified on existing users, as well as directly when inviting a new user. ![Invite user](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/34-user-roles.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=0f0622b04328fdadf4e83d3f262da85b) **Oct 21, 2023** ## Status pages Status pages are now available for all users, and they're **the most carbon-efficient status page on the market with an incredibly fast load time**. You can create unlimited status pages with a phare domain name, and personalize it with limited branding options. ![Status Page](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/33-status-pages.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=19d2a8f6f6a7b3437f56604302c71825) **Sep 17, 2023** ## European mail server The mail server used to send alert notifications has been moved to a new provider based in Europe, making Phare 100% European for non-subscribed users. This is part of Phare's commitment to privacy and data protection, using only services from companies that are headquartered in Europe and hosted in European datacenters. The only exception is Stripe, a US-based company used to process billing information and payments. **Aug 21, 2023** ## New branding Bye bye MinKit and hello Phare. The platform has been renamed to Phare and has a new logo. The new name is a reference to the lighthouse, a beacon of light that helps ships navigate safely. This symbol represents Phare's mission to give a signal when it is needed so you can run high-quality production websites. The new name and logo are designed to feel right at home. The old domain name `minkit.io` will continue to work for about a year, but you should update your bookmarks and password manager as soon as possible to avoid any inconvenience in the future. ![New branding](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/32-minkit-becomes-phare.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=e1c445d0d9b72462b5c9ae51e35f7e60) **Aug 18, 2023** ## Improved monitoring page Visualisation of incident periods in the performance chart has been improved, and you can now get your website's average response time, cumulated downtime and availability % for the selected time period (24 hours, 7 days, 30 days or 90 days). ![Monitoring statistics](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/31-monitoring-statistics.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=cd8eebe5136804fcd22b36c02ae2c77c) **Aug 17, 2023** ## Faster monitoring statistics A lot of work has been done to improve the monitoring statistics. With 15M records in the database, it was starting to be a bit slow to load monitoring results by Phare's standards, because speed is a priority. [ClickHouse](https://clickhouse.com/) came to the rescue, saving up to 500ms on every page load. If you visit your monitoring page twice a day, that's 6 minutes of your life saved every year. **Aug 15, 2023** ## Reviews A new review page has been added to the website with a list of all the places where you can leave a review of the platform. If you like Phare, please consider leaving an honest review on one of these platforms. The first 85 reviews created on Capterra will **receive a \$20 gift card**! ![Write a review](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/30-review.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=623bd70570b442484e216d81928c8150) **Jul 29, 2023** ## Deletion safeguard A new safeguard has been added to the platform to prevent accidental deletion of important data. When you try to delete your user account, a project, or your organization, you will be asked to confirm your action with a small typing challenge. This will prevent you from accidentally deleting your account or organization. ![Deletion safeguard](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/29-deletion-safeguard.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=d6ad8f3a564b0d05edc4158a34da65f3) **Jul 28, 2023** ## Alert rules duplication You can now duplicate an alert rule to rapidly create a new one with the same configuration. This is useful if you want to create a new alert rule with a similar configuration to an existing one. ![Alert rules duplication](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/28-alert-rule-duplication.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=2917a3e5bf862d86686f6db340a82d40) **Jun 4, 2023** ## Performance monitoring history It is now possible to navigate the performance history of your monitors, with three available time ranges of 24 hours, 7 days and 90 days. This is a first step towards giving you more flexibility on how you view and access your monitoring data. ![Performance monitoring history](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/27-performance-history.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=4144642669e8cedf6cd7ceb60ff100e5) **May 29, 2023** ## Improved uptime precision Uptime percentage is now calculated with four digits precision, allowing more accurate long-term SLA calculations. For example, 99.9999% uptime means that your service can be down for 31 seconds per year. Badges also got updated with four digits precision. ![Improved uptime precision](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/26-improved-uptime-precision.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=612f9924c3c8adaf66230cf0f7d93e08) **May 27, 2023** ## Incident events improvements Incident events now show more precise date and time information. With the exact time of the event, and the elapsed time since the creation of the incident. ![Incident event date time](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/24-incident-event-date-time.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=8353f948a950727e1d8eb52bcea61ba1) A tooltip with the exact date and time is also available on hover of all the already existing dates and times in the Phare dashboard. ![Datetime tooltip](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/25-datetime-tooltip.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=68fbe8aca3b1c75b13f71a3b0ada1bbb) **May 17, 2023** ## Multi-quota billing alerts A fairly technical feature, but important for the future of the platform. With the release of the SMS integration last week, Phare now offers two different billing quotas: SMS alerts and monitoring events. The billing alert system, which is responsible for sending emails when a quota is exhausted, was the last piece of the billing infrastructure that only supported monitoring events. In simpler terms, the platform now has the required foundation to bill anything, as part of a monthly plan or as additional usage. New features no longer require billing infrastructure changes, allowing faster releases. ![Multi-quota alerts](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/23-multi-quota-alerts.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=8caf3820aa20fd7d1673aec76e727956) **May 14, 2023** ## Integrations documentation The [documentation for the integrations](https://docs.phare.io/integrations/overview) has been created, mostly to include information on the new SMS integration. You can find a few tips on configuration, supported countries, the email address and phone numbers Phare uses to send alerts, and much more. ![Integration documentation](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/22-integrations-documentation.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=28876b7a42d78c018f9ae2d61a2d4146) **May 13, 2023** ## SMS integration Phare now offers SMS alerts! You can receive SMS alerts by configuring the new SMS integration. The SMS integration is only available on the Scale plan with 100 alerts included monthly. ![SMS integration](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/20-sms-integrations.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=b0afb153bcccc6985a8ada1c076b849b) You can add a phone number to their profile, which will be used to send SMS alerts. You will have to validate your phone number by entering a code sent by SMS. Team members that do not yet confirm a phone number can still be added to the SMS integration, but they will not receive the SMS alerts, a fallback solution will be added in the future. ![SMS integration](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/21-sms-integration-configuration.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=8a3863ced731283426efd1c306ba91d4) **May 10, 2023** ## Improved design The [home](https://phare.io) and [pricing](https://phare.io/pricing) pages got updated with a frostier design. A few other pages got updated as well to improve consistency across the website. ![Improved design](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/19-improved-design.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=5cfb8f1ab22f3356c5bd73cb59e95127) **May 5, 2023** ## Public launch The public launch on [ProductHunt](https://www.producthunt.com/posts/phare-uptime) went well, with the first unsolicited users signing up and using the platform. The platform has stayed stable and reliable, with only a few minor bugs reported and fixed since the launch. Thanks to everyone who voted on ProductHunt and participated in the launch. During the same period, the first paying customer joined, which is a great milestone for the project. ![Phare on ProductHunt](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/18-producthunt-launch.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=0074388d1fcb11307ee9801e4a7f416b) **May 4, 2023** ## Documentation Documentation has been published. It is still a work in progress, but it is already a great resource to learn about what the platform has to offer and how to use it. ![Documentation](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/17-documentation.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=5dda48c08936cc49a6f41dac2438affc) **Apr 14, 2023** ## New monitor alert rules Two new alert rules have been added to receive alerts when a monitor is created or deleted ![New monitor rules](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/1-new-monitor-rules.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=73ac3f047811b4dc1ccafe2219abfb2a) **Apr 10, 2023** ## Bunny CDN Phare migrated from [Cloudflare](https://www.cloudflare.com/) to [Bunny.net](https://bunny.net/). Bunny is a reliable content delivery platform with lightning-fast performance, making the platform even faster than before. ![Performance](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/16-performance.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=d62ed348754a804bd0d3ca7a80951696) Speed is not the only reason for the migration. Bunny is a European Union company, based in Slovenia. This migration is part of Phare's effort to rely as much as possible on European providers and ensure maximum privacy for users. **Apr 9, 2023** ## Billing overage management One feature was missing in the billing cycle released last week, managing overage, which occurs when your organization consumes more events than allowed in its subscription plan. You will now receive two emails, when 90% and 100% of your monthly allowed quota has been used. A free overage of 10 additional percent is offered before your account gets locked until the next billing period, or until you subscribe or upgrade your plan. ![Overage management](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/15-overage-management.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=ef79b0c3f644778c60cc8737dcb96b04) **Apr 8, 2023** ## End of beta With 3.5M checks successfully performed, 272 incidents reported, and 639 notifications sent, the platform is stable enough to end the beta program. The last 6 weeks have been productive, with lots of features and improvements on the platform, and a public launch is planned for early May. If you would like to support the launch on ProductHunt, you can [subscribe here to get notified](https://www.producthunt.com/products/phare). **Apr 6, 2023** ## Paid plan activation With the end of the beta program incoming, the payment integration has been activated, which means no more unlimited usage on the free plan. Most of this week went into making sure the billing system was working as expected, and that monitoring events are reported fairly every month. **Apr 2, 2023** ## Incidents on performance chart A small change, but a welcome one to the performance chart, as you can now see incidents directly, and how they impact your website performance. ![Incidents on performance chart](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/14-incidents-on-performance-chart.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=10ba0e2b0b46cfd14cdbb5387f6e6a65) **Apr 1, 2023** ## Frequently asked questions The pricing page now shows some frequently asked questions that should make everything clearer about how Phare works. This is a small first step toward fully fledged documentation. ![Frequently asked questions](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/13-faq.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=0a9fe0b3b2df3e93d261dadadf291734) **Mar 28, 2023** ## Stress test To make sure that the platform continues to work flawlessly under load, thousands of test monitors have been created for a few days to expose any performance weaknesses. A few culprits were identified in how uptime averages were calculated and monitoring results stored, and those issues are now fixed. On older monitors, the statistic page could take up to a second to show, which is not on par with the rest of the platform in terms of performance. It has been improved and should now be displayed in under 100ms. **Mar 26, 2023** ## Pagination Dealing with so many monitors was impossible without a pagination, which is now active on most pages like projects, environments, monitors, incidents, and alert policies. ![Pagination](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/12-pagination.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=3bc7a15cbc914fe1046700fd9e87bf30) **Mar 24, 2023** ## Authentication pages redesign A small redesign of the authentication pages was made to make the pages more coherent with the overall design of the new landing pages created last week. ![Authentication pages](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/11-authentication-pages.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=e9587e79138c02b643763a81a5636f5a) **Mar 22, 2023** ## Legal Phare published the [terms of services](https://phare.io/legal/terms-of-service) and [privacy policy](https://phare.io/legal/privacy-policy). This was not the funniest task, but a necessary one as the open beta approached. **Mar 19, 2023** ## Improved billing Billing is not yet active during the private beta, giving time to make sure everything is simple and works as expected. Wording around plans, billing, and quotas have been reviewed and changed to make things easier to understand. The offer is also simplified with a limited free (Hobby) plan, and a single paid (Scale) plan. The paid plan, as the name suggests, grows with your organization needs thanks to additional quotas that can be configured. A detailed pricing calculator is now available on a new [pricing page](https://phare.io/pricing). The billing page presents a fresh look with more detailed information on included and additional usage for all products: ![Phare billing management](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/10-billing-management.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=10f9f80cd63fa6552e8bf8d5cd16b3ee) **Mar 15, 2023** ## Members management It is now possible to invite your colleagues to your organization, all accounts have unlimited numbers, the more, the merrier. ![Phare members management](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/9-members-management.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=3cf2bb26fa4269f50ea8c827703d3301) You can assign members to projects and choose who has access to a project during creation. ![Phare project with members](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/8-project-with-members.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=2e267a3ddb2ae2ea9585b883ab55497e) For now, all members can perform every possible action in the scope of their respective project. More granular role management will come later. **Mar 9, 2023** ## New landing page The landing page received a small makeover. A new marketing-oriented page has been created to present the Phare Uptime product with more details. Go check out the new [Phare Uptime landing page](https://phare.io/products/uptime). **Mar 9, 2023** ## New alert rules Two new rules have been added with the introduction of incident management, one that triggers when a new incident is created and one when an incident has recovered. ![Incident alert rules](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/7-incident-alert-rules.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=4ddeeb79b4b49c5ef4c5d6a1d716a8ba) These two new rules replace the former `Monitor status changed` rule that no longer exists. All users' default alert policy rules have been updated to reflect this change. **Mar 8, 2023** ## Incident management Monitors now automatically create and resolve incidents, this behavior can be configured in each monitor's settings with two new parameters. * Incident confirmations: number of failing checks required before creating an incident. * Recovery confirmations: number of successful checks required before resolving an incident. ![Incident management configuration](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/6-incident-management-configuration.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=d26e029136b7fa069dadc68d7711228f) All incidents are shown in the incidents section of MinUptime, you can quickly see their status and act accordingly. ![Incidents](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/5-incidents.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=c81dfccc8fce3941c06d29b25f959b53) To help you fix the situation, a timeline of events linked to an incident is shown on the incident's page. ![Incidents timeline](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/4-incidents-timeline.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=4d3b653735fe3d9cc87ec8f235a63ca2) **Mar 6, 2023** ## Discord integration Discord is now an available integration, it can already be used for all types of alerts, and be configured to specific project and environments like the existing Slack and Email integration. ![Discord integration](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/3-discord-integration.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=ddccd412771baba5cc2623039ff51c55) **Mar 2, 2023** ## Timezone and time format Users can now select their Timezone and preferred time format (24 or 12-hour clock) ![Timezone and time format](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/2-timezone-and-time-format.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=70f6c53d8841e1ad172fb99834915120) # Changelog of 2024 Source: https://docs.phare.io/changelog/2024 Follow the updates and improvements made to the Phare platform in 2024. **Dec 23, 2024** ## Shield status badges Shield status badges are now available for your status pages. You can embed these badges in your documentation, README files, or any other web page to show the current status of your services. Two types of badges are currently available, a status badge showing the overall status of your status page, and an availability badge showing the uptime percentage of your services. ![Status badges](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/64-status-badges.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=3b2c4bc0817dc95e9acc5bf9df6fe072) **Dec 11, 2024** ## Send test alert rule notifications Phare now lets you send test notifications for your configured alert rules. Whether you’re fine-tuning an alert or setting up a new monitor, you can see exactly how it works before going live. This is particularly useful for more complex alert rules, like outgoing webhooks, where you can verify that the payload is correctly formatted and received by your system. This release also includes some quality of life improvements around alert policies and rules. ![Test notifications](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/63-test-notifications.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=9966a80b6ca82a55f7113d6704af7ae5) **Dec 6, 2024** ## Pushover integration Phare now supports Pushover, so you can get your alert notifications straight to your preferred device. Unlike other Pushover integrations you might have tried, Phare lets you set a custom priority for each type of notification, giving you fine-grained control over your alerts. Read the [Pushover integration documentation](/integrations/pushover) to get started. ![Pushover integration](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/62-pushover-integration.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=af6ed653529a0daeae2388dea727e23e) **Nov 22, 2024** ## Quickly pause and resume monitors Monitors can now be paused and resumed directly from the monitor list. This feature allows you to quickly disable monitoring for a specific monitor without having to navigate to the monitor page. ![Quick pause resume monitors](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/61-quick-pause-resume.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=9eced809abf1b831b207819ca612b73b) **Nov 22, 2024** ## Favicon support on status pages You can now customize the favicon displayed on your status pages. This feature allows you to add a personal touch to your status page and provide a more branded experience for your users. ![Status page favicon](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/60-status-page-favicon.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=560c6ec16790977acb483f331eefc163) **Nov 20, 2024** ## Simplified TCP monitoring TCP monitoring has been simplified to make it easier to set up and manage monitoring for your services. No need to specify a payload and an expected response. ![Simplified TCP monitoring](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/59-simplified-tcp-monitoring.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=17f8508012a75dbdbfb6b73d472400a3) **Nov 11, 2024** ## Refreshed status pages Status page design has been slightly refreshed to provide a better look and feel. This also includes a few bug fixes and improves how incidents and downtime are presented to your users in a more coherent way. ![Refreshed status pages](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/58-refreshed-status-pages.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=1a7f4819f8b7fb34836e393be05748fa) **Nov 8, 2024** ## Incident management enhancements Several improvements have been introduced to the incident management system to streamline incident creation and give you more control: ### Manual incident resolution You can now manually resolve incidents, providing greater control over the incident lifecycle and ensuring accurate status reporting. ![Manually resolve incidents](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/55-resolve-incidents.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=c66d3710e9e78fe2190dc2432f378a2f) ### Publish status update during incident creation When creating a new incident, you can now publish a status update immediately, keeping your users informed from the very beginning. ![Incident updates at creation](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/56-publish-incident-updates-at-creation.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=de780d6098cb8efee9688c3b5e3236b8) ### Control on incident downtime calculation You now have the ability to exclude an incident from the downtime calculation, allowing you to maintain accurate uptime metrics and avoid skewing your performance data. This feature is particularly useful for maintenance windows with downtime that are already part of your SLA, or for incidents that have minimal impact on your users. ![Control incident downtime](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/57-control-incident-downtime.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=d813ff3e336a707b840b8f5cdc31301b) **Oct 7, 2024** ## Incident creation Incidents can now be created manually. This feature allows you to easily track and manage incidents that are not automatically detected by uptime monitoring checks. It is now also possible to modify incidents created automatically by the platform, allowing you to customize incident titles shown on your status page and add more details to the incident report. Manually created incidents use alert policies under the hood and are not automatically resolved when associated monitors are successful. This feature makes it easier to communicate with users during incidents. ![Phare incident creation](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/54-create-incidents.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=cdb12350e2b25872e614ecb430561031) **Aug 30, 2024** ## Phare for good Phare is introducing the "Phare for Good" initiative, offering an extended free plan to open source projects and nonprofit organizations. This initiative supports projects making a positive impact by providing the full suite of monitoring and incident management tools, completely free. If you're driving change through technology or social causes, Phare is here to help keep your online presence strong and reliable. Join the program here: [https://phare.io/for-good](https://phare.io/for-good) ![Phare platform makeover](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/53-phare-for-good.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=c1497687e36ef4342a2a2251880e6694) **Aug 22, 2024** ## Blog An official blog is now live for Phare. New content is posted occasionally, but only when there is something valuable to share. You can already read a few articles: * [Downsampling time series data](https://phare.io/blog/downsampling-time-series-data/) * [Running Ghost on Docker with subdirectory routing](https://phare.io/blog/how-%77%65-run-ghost-on-docker-with-subdirectory-routing/) * [Best practices to configure an uptime monitoring service](https://phare.io/blog/best-practices-to-configure-an-uptime-monitoring-service/) **Aug 5, 2024** ## Phare platform makeover The Phare platform received a makeover focused on improving the navigation and user experience. The new design provides a cleaner and more intuitive interface, making it easier to access the features you need. Most pages have been updated with many small improvements to improve the overall user experience. Your monitoring pages have also been redesigned slightly and given a new filter to show performance data specific to a region. This allows you to quickly identify any regional performance issues and take appropriate action. ![Phare platform makeover](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/52-platform-makeover.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=c30ac42641085d5afa160ada3e376181) **Jul 29, 2024** ## Improved monitoring performance chart The algorithm used to generate the performance chart has been improved to provide a more accurate representation of your monitor's performance. This change allows for better anomaly removal and a more precise representation of the overall performance shown by your monitor. Incidents are now displayed on the chart with their respective impact colors, making it easier to understand any correlation at a glance. If you're interested in learning more about how Phare generates the performance chart, read the article on [downsampling time series data](https://phare.io/blog/downsampling-time-series-data/). ![Performance chart](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/51-performance-chart.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=0251a6113117838c467a7fca7c18ee73) **Jul 22, 2024** ## Custom domains for status pages You can now use your own domain for your status pages, providing a more seamless and branded experience for your users. This feature allows you to create a custom subdomain for your status pages, such as `status.example.com`, and link it to your Phare status page. The Phare-provided subdomain `*.status.phare.io` attached to your status page will stay active and will automatically redirect users to your custom domain if you configure one. Instructions on how to set up a custom domain for your status page can be found in the [documentation](/uptime/status-pages#custom-domain). ![Custom domain status pages](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/50-custom-domain-status-pages.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=6e8d2553b6528c3f90ae22e3da6c6ec1) **Jul 17, 2024** ## Outgoing webhooks integration Outgoing webhooks are now available on the Phare platform, allowing you to connect with third-party tools or build your own integration. The webhook payload can be customized for each alert rule event that you would like to use. You are free to use any valid JSON structure with access to many variables to help you build the perfect payload for your use case. ![Outgoing webhooks alert rules](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/48-outgoing-webhook-alert-rule.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=008e5377d89a008878e5c1f0ea12770d) Webhooks are secured with an HMAC SHA-256 signature to ensure the authenticity of the payload in a way that is resistant to replay and timing attacks. A retry policy is also in place to ensure that your webhook is safely delivered, even if your server is temporarily down. One more thing: you can also browse the history of the payloads sent to your webhook to easily debug and monitor the integration. ![Outgoing webhooks logs](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/49-outgoing-webhook-logs.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=8d1e4d1632ea2998df30d997ed650b90) You can learn more about the outgoing webhooks integration in the [documentation](/integrations/outgoing-webhook). **Jul 11, 2024** ## Billing quotas estimation Billing quota forecasting has been released on the Phare platform. This new feature provides greater visibility into your billing quota usage, helping you manage your resources more effectively. On your organization billing page, you can now see detailed forecasts of your quota usage. This includes predictions based on your current usage patterns, allowing you to plan ahead and avoid service interruptions. ![Billing quotas estimation](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/46-billing-quotas-estimation.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=00e2f5bc68f318a795644dc5e36d2b9f) You will also be alerted when creating or updating a monitor if the action exceeds your monthly quota. This real-time feedback helps you make informed decisions and ensures that your monitoring setup remains within your desired limits. ![Monitoring quotas forecast](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/47-monitoring-quotas-forecast.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=5309a1f79d14b0cf0abf5404f0b235b7) Billing transparency is a key part of the Phare platform, and the tooling helps you monitor and control usage effectively. **Jul 7, 2024** ## New API endpoints: alert rules, incidents and status pages New API endpoints are available to help you programmatically interact with the Phare platform: * [Alert rules](/api-reference/platform/alert-rules/list-alert-rules) * [Incidents](/api-reference/uptime/incidents/list-incidents) * [Status pages](/api-reference/uptime/status-pages/list-status-pages) These new API endpoints enhance your ability to automate and streamline your monitoring, alerting, and incident management workflows, offering a more integrated and efficient approach to maintaining service reliability. This release ends the current phase of API development with all major entities now available, allowing Phare to focus on stability and plan the end of the beta phase. ![New API endpoints](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/45-new-api-endpoints.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=c96ca458680d6790f8928778fd22cc5f) **Jul 4, 2024** ## Monitoring timeout customization You can now customize the timeout duration for your monitors, offering greater control over your monitoring strategy for more accurate and reliable results. This new feature allows you to set specific timeout values, taking into account DNS resolution, connection time, response time, and any redirections. By adjusting these settings, you can fine-tune the sensitivity of your checks to better meet your specific needs. While the default timeout value of 7 seconds is optimized for most scenarios, providing a good balance and minimizing false positives, you now have the flexibility to modify this setting to better suit your unique requirements. ![Monitoring timeout customization](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/44-monitoring-timeout.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=111c366c3a3490d7fb8aa0c59db913e5) **Jul 3, 2024** ## Smart monitoring suggestion Phare is introducing smart monitoring suggestions, designed to help you effortlessly optimize your monitors. This new feature provides tailored recommendations to enhance the accuracy and reliability of your monitoring. Smart Suggestions will alert you of unnecessary redirects, which can slow down your site's reported performance, and recommend using multiple regions for monitoring if you currently use only a single region. By following these suggestions, you can ensure more comprehensive coverage and faster detection of potential issues. ![Smart monitoring suggestion](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/43-monitoring-suggestions.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=b527a5350dad066fd4b6a5f52a261c74) **Jul 2, 2024** ## 30 second monitoring interval Phare enters the realm of sub-minute monitoring with the introduction of a new 30-second monitoring interval for your monitors. With this update, you can detect and respond to issues faster than ever, ensuring that your services remain reliable with minimal downtime. The 30-second checks are available to all users, offering a higher level of detail and control over your monitoring strategy. ![30 second monitoring](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/42-30-second-monitoring.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=6c7c44a3817fae0c46ed5a19ca456008) **Jul 1, 2024** ## New changelog Phare's changelog has moved to the documentation site to harmonize how new Phare features are documented. All previous entries were migrated to [this page](/changelog/2024). This new format should allow faster and more frequent updates. **May 28, 2024** ## New monitoring regions Following a recent monitoring infrastructure migration, three new regions are released for uptime monitoring: Say hello to Japan, the United Kingdom and Mexico. ![New monitoring regions](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/41-new-monitoring-regions.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=b0fbe05228d006aeec3c500f259c9a66) **May 26, 2024** ## New monitoring infrastructure Phare's monitoring infrastructure is the biggest operating cost and most important piece of the Phare Uptime product. As Phare performs millions of monitoring checks from many regions around the world, this infrastructure should be scalable, efficient, and most importantly reliable. As the platform grew over the past few months, the previous solution based on [AWS Lambda](https://aws.amazon.com/lambda/) started to show its limits in terms of performance and cost, forcing a search for an alternative solution. Phare has migrated all monitoring checks to a newly written infrastructure based on [Cloudflare workers](https://workers.cloudflare.com/). This solution helps maintain a generous free plan and competitive pricing for paid customers. **May 24, 2024** ## Alert policies API API endpoints to manage alert policies have been released and documented. ![Alert policies API](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/40-alert-policy-api.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=d418c596477f4e0499f5d70ba9de1ff5) **May 20, 2024** ## REST API The Phare REST API has been released with associated [documentation](/api-reference/introduction). All endpoints required to manage monitors are already available. Other endpoints will be added in the next few weeks until all the actions you can perform in your dashboard can also be done programmatically. You will need to generate an API key to authenticate your organization. You can choose an access scope (Read / Write) for each Phare product as well as access to the resources of the Phare platform. More information is available on the [API documentation](/api-reference/introduction) page. [https://iframe.mediadelivery.net/embed/238508/67722b0a-5db6-4eb3-88ba-a2f9f574f388?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true](https://iframe.mediadelivery.net/embed/238508/67722b0a-5db6-4eb3-88ba-a2f9f574f388?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true) **May 15, 2024** ## New Documentation Documentation has been moved to [docs.phare.io](/introduction) and offers an improved user experience. The documentation source code has also been published to [GitHub](https://github.com/phare/docs), allowing anyone to contribute. ![New documentation](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/39-new-documentation.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=e46a525815dbff36ee00468806bd6292) **May 7, 2024** ## Incident comment and update alert Two new alert rules have been created to let you know when your team is working on resolving an incident. The first one will alert you every time a new comment is published on an incident timeline, and the second when a team member publishes a status update for the incident. ![Incident comment and update alert](https://mintcdn.com/phare/hSNtktqv9Oo22zDC/images/changelog/38-new-alert-rules.webp?fit=max\&auto=format\&n=hSNtktqv9Oo22zDC\&q=85\&s=f99856388611301837f3c4c3a0840fb2) **May 2, 2024** ## Hosting provider migration Phare migrated to a new datacenter managed by [Hetzner](https://www.hetzner.com/) in Germany. The switch was made on May 2nd and resulted in \~6 minutes of downtime on uptime monitoring and \~10 minutes of downtime on dashboard access. This infrastructure migration was performed to improve speed and reliability of the service. A lot of work has also been put into disaster recovery, with four times more backup point every day and multi-region (all in Europe) replication. This ensures that the service can be put back up with the smallest possible downtime in case the current datacenter has a major outage. # Changelog of 2025 Source: https://docs.phare.io/changelog/2025 Follow the updates and improvements made to the Phare platform in 2025. **Nov 24, 2025** ![Open metrics](https://mintcdn.com/phare/Cg0jtM97ctG5RA9P/images/changelog/105-open-metrics.webp?fit=max\&auto=format\&n=Cg0jtM97ctG5RA9P\&q=85\&s=a07c60aff84596d55171212e7527d188) ## Public growth metrics Phare now shares growth metrics openly, so you can follow the journey with live user registration stats, monthly uptime monitoring checks, detailed revenue, and cost breakdown. Visit the [open metrics page](https://phare.io/open). **Nov 23, 2025** ![France region](https://mintcdn.com/phare/Cg0jtM97ctG5RA9P/images/changelog/104-france-region.webp?fit=max\&auto=format\&n=Cg0jtM97ctG5RA9P\&q=85\&s=591cd5ff82105178059614587cd899cd) ## New uptime monitoring region in France A brand-new monitoring region is now live in France, humming with that signature hon hon hon server noise. Expect uptime as fast as a TGV, incidents that dramatically shout “SACRE BLEU”, and a special Parisian luxury experience. **Nov 1, 2025** ![Status page subscription channels](https://mintcdn.com/phare/c9uA6xx59gvzX5TO/images/changelog/102-status-page-subscription-channels.webp?fit=max\&auto=format\&n=c9uA6xx59gvzX5TO\&q=85\&s=33089d93b86fbf060013c83cc40b1655) ## Customize status page subscription channels You can now customize which subscription channels are available for your users on your status page. The current selection of subscription channels is RSS and Atom. **Oct 26, 2025** ## Improved combobox selection A small convenience update for those of you with dozens of monitors or team members, Phare's combobox now comes with an easy way to select or deselect all options, allowing you to act faster without having to do 60 clicks. **Oct 4, 2025** ![Incident AI generations](https://mintcdn.com/phare/lx30wDf_-f9_VKzD/images/changelog/101-incident-ai-generations.webp?fit=max\&auto=format\&n=lx30wDf_-f9_VKzD\&q=85\&s=f2e5aa9d814fc604e622fc858a58e9df) ## AI-generated incident summaries and post-mortems Resolving incidents just got a whole lot easier. Programmatic incidents are now automatically enriched with AI-generated summaries and post-mortems, giving you a clear overview of what happened without the manual effort. This feature is powered by Mistral’s Magistral Small model, chosen for its efficiency and privacy-friendly design. Incident AI is configurable per project, and available on all plans with monthly quotas: * **Hobby**: 10 AI generations / month * **Scale**: 100 AI generations / month + optional pay-as-you-go You can also rate each AI summary directly from the incident page. Feedback helps improve accuracy and usefulness over time. Read more about [Incident AI](/uptime/incidents#incident-ai) in the documentation. **Sep 18, 2025** ![Smart Incident Merging](https://mintcdn.com/phare/qmQqNMU04844ct2O/images/changelog/100-smart-incident-merging.webp?fit=max\&auto=format\&n=qmQqNMU04844ct2O\&q=85\&s=51d92e76c135c2104e67c9ccb7c0112e) ## Smart incident merging Smart Incident merging is now available! This feature can be activated on a per-project basis, allowing you to choose a merge time window that fits your needs. Only similar incidents are merged together, and when paired with the thread support released a few weeks ago, this drastically reduces notification noise. Two new alert rule events are available: * **Incident Propagated**: A new monitor starts failing and is merged into an existing incident. * **Incident Partially Recovered**: One of the previously failing monitors recovers, but the incident remains open. Smart incident merging is not enabled by default for existing accounts, so you need to opt in from your project settings. Read the extended [Smart Incident merging documentation](/uptime/incidents#smart-incident-merging) for more information on this new feature. **Sep 9, 2025** ![Ntfy integration](https://mintcdn.com/phare/LIohR_9HePF0s2bi/images/changelog/99-ntfy-integration.webp?fit=max\&auto=format\&n=LIohR_9HePF0s2bi\&q=85\&s=f6f7f1d055bed4c3d29155fb5b4d4fbf) ## Ntfy.sh integration A new integration with [ntfy.sh](https://ntfy.sh) is now available to send alerts to your ntfy application. The integration supports sending messages to a topic through a custom server hostname and access token authentication. It can already be used with all existing alert events. You can find the documentation for the [ntfy integration here](/integrations/ntfy). **Sep 9, 2025** ![Slack threads support](https://mintcdn.com/phare/iG54y5gVuPTRWcRI/images/changelog/98-slack-threads.webp?fit=max\&auto=format\&n=iG54y5gVuPTRWcRI\&q=85\&s=dec96d4c4037d0674ab6bbf1d0de1cb1) ## Support for Slack threads The Phare integration for Slack now sends all notifications related to the same incident in a dedicated thread, making it easier to follow and manage incident notifications without cluttering your main channels. This update requires you to reinstall the integration to grant the permissions necessary for creating threads. You can do this from the integrations page of your dashboard, as explained in the [Slack integration documentation](/integrations/slack#reinstallation). **Sep 7, 2025** ![Discord threads support](https://mintcdn.com/phare/ITYyfSV_ujqGPRcE/images/changelog/97-discord-threads.webp?fit=max\&auto=format\&n=ITYyfSV_ujqGPRcE\&q=85\&s=04a3ef8366787dfcd4130496049dd73c) ## Support for Discord threads The Phare integration for Discord now sends all notifications related to the same incident in a dedicated thread, making it easier to follow and manage incident notifications without cluttering your main channels. This update requires you to reinstall the integration to grant the permissions necessary for creating threads. You can do this from the integrations page of your dashboard, as explained in the [Discord integration documentation](/integrations/discord#reinstallation). **Sep 2, 2025** ![Email threads support](https://mintcdn.com/phare/aFBpTSUGU7VRq6Un/images/changelog/96-email-threads.webp?fit=max\&auto=format\&n=aFBpTSUGU7VRq6Un\&q=85\&s=0f400a64ab0e2bd3409ed5d4dd32d6e2) ## Support for email threads Email alerts sent to your inbox now support email threads, making it easier to follow and manage incident notifications without cluttering. When you receive multiple notifications for the same incident, they will be grouped together in a single email thread, allowing you to see the entire conversation in one place. All emails also got a fresh new look that is more consistent with the Phare design system. **Sep 2, 2025** ![Incident notification filtering](https://mintcdn.com/phare/aFBpTSUGU7VRq6Un/images/changelog/95-incident-notification-filtering.webp?fit=max\&auto=format\&n=aFBpTSUGU7VRq6Un\&q=85\&s=ff39478ca31d3ae0c68e2c8858d838a7) ## Alert rule filtering for incident events Some alert rules can now be filtered to only send notifications for specific incident types. This is particularly useful to avoid being notified of manually created incidents, or to send notifications to different channels based on the incident type. The following alert events now support filtering by incident type: * Incident created * Incident recovered * Incident comment created * Incident update published **Aug 22, 2025** ![Monitor with POST, PUT, PATCH and a body](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/94-monitor-with-payload.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=2dce0f639ae236d9aaf803aff81fe181) ## Support for POST, PUT and PATCH methods with a body You can now create HTTP(S) monitors using the POST, PUT or PATCH methods, and include a request body with a content type of your choice. This allows you to monitor APIs and webhooks that require a specific method and payload. **Aug 15, 2025** ![Status page timeframe](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/93-status-page-timeframe.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=d10c3680a7a2132ab1236ab7d058701d) ## Custom status page history timeframe You can now customize the timeframe of the status page history, allowing you to choose between 30, 60 or 90 days. This gives you more flexibility in how much historical data you want to display on your status page. **Jul 30, 2025** ![Mute projects](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/92-mute-projects.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=63828a50363dcb160911644571dbac95) ## Mute projects It is now possible to mute an entire project that is being a little too noisy. Notifications are muted, but: * Incidents still show up in the dashboard * Notifications are logged with a "muted" status * You can still access the uptime percentage and other stats of your monitors Perfect for temporarily unstable infra, or that one API that breaks a few times a day. The feature can be activated from the Alert Rules page of your dashboard, and a special indicator will be shown for all muted projects. **Jul 30, 2025** ![Improved timeline](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/91-improved-timeline.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=429d53a1fb1939630026fa67f4c1cfb5) ## Improved incident timeline Many improvements landed on the incident timeline to improve the incident management experience: * Details of monitor modifications done during an incident active period are now shown in the timeline * Details of incident modifications done during an incident active period are now shown in the timeline * Relevant actions performed by API are now logged in the timeline, with the name of the API key used to perform the action * The timeline design has been refreshed and made more compact to show more data **Jul 17, 2025** ## Support for brotli and zstandard compression Phare's monitoring agent (A.K.A Beacon) now supports Brotli and Zstandard compression algorithms. The deflate implementation has also been updated to be compatible with the RFC 1950 standard on top of the existing RFC 1951 implementation. The monitoring agent `Content-Encoding` header has been updated to reflect this change: ```text theme={null} Content-Encoding: gzip, deflate, br, zstd ``` This should save a few bytes over the years ✌️ **Jul 8, 2025** ![Multi-monitor incidents](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/90-multi-monitor-incidents.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=e73ce810c7ceb613adbab1fbb3175857) ## Create incidents for multiple monitors It is now possible to create incidents for multiple monitors at once. This is a big structural change that will allow building features like incident merging. **Jul 1, 2025** ![Pay with credits](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/89-pay-with-credits.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=1ac4fbfdf13f7855e7355dd266db34a1) ## Credits payment for Scale plan The Scale plan now supports prepayment, allowing you to pay for a few months or a few years in advance. This allows you to receive a single invoice for the entire period and avoid monthly payments. This comes with a slight change for users already on the Scale plan, as the plan is now paid at the end of the month instead of the beginning. **Jun 26, 2025** ![Enhanced incident details](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/88-enhanced-incident-details.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=2a9b1024c1811944935063478e87b642) ## Enhanced incident details The information available in incident reports has been extended to include: * ✅ *Resolved address*: See the final hostname and port. * 🔢 *Status code*: Quickly verify the HTTP response status. * 🧪 *Assertion results*: View detailed outcomes for each assertion. * 📦 *Response size*: View the byte size of the response body. * 🧾 *Response headers*: Inspect the HTTP headers returned by the server. * 🔍 *Request trace*: Follow the full journey of the request through each step. The additional context should help you identify incident root causes more quickly and accurately. **Jun 13, 2025** ## Updated inactivity restriction for Hobby plan Organizations on the **Hobby** plan are now automatically deactivated after 4 months of inactivity, instead of 6 months. This means that if your organization has no active members for 4 months, it will be deactivated and all data will be deleted after receiving two reminder emails. This change is necessary to keep the platform sustainable, and requesting three sign-ins per year seems reasonable for a free plan. **Jun 12, 2025** ![Success assertions](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/87-success-assertions.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=9b3325d9ec03028fe07962a9e86a1fe8) ## Success assertions You can now define success assertions for your monitors, allowing you to specify custom checks for: * Status codes (with support for wildcards and multiple codes) * Response headers * Response body content **May 24, 2025** ![New monitoring options](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/86-new-monitoring-options.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=e5e14e9c1ff3fc90e9d815e075f5cf7a) ## TLS over TCP, and new monitoring options Monitoring secure TCP services with a TLS connection is now possible, allowing you to monitor a wider range of services. Certificates discovered during TCP monitoring are now tracked, and you can set up alert rules to be notified when they are about to expire. All types of monitors can now skip SSL/TLS certificate validation, which is useful for testing services with self-signed certificates. HTTP(S) monitors can now be configured to fail when facing a 3xx redirect response. **May 15, 2025** ![Phare design refresh](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/85-design-refresh.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=d25b7134e703f0b6490109437e686ecc) ## Refreshed design Phare has a fresh new look. The design has been refreshed to be more modern and user-friendly, and navigation should be more intuitive. **May 9, 2025** ![Removed integration project scope](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/84-removed-integration-project-scope.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=f2ee9c5145d06e56c45906f756f7a796) ## Integration project scope removed It was possible to scope integrations to a specific project, which was useful for advanced use cases of large organizations. However, this feature was not widely used and made integrations needlessly complex for most users, and Phare is all about the fine line between simplicity and sophistication, so bye-bye scoped integrations. **May 7, 2025** ![Custom headers](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/83-custom-headers.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=fe3647f2d1f8fed00104619dd39b9a54) ## Custom HTTP headers You can now add custom HTTP headers to your monitors. This is useful for passing authentication tokens, or any other headers required by your application. **May 7, 2025** ![User agent secret key](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/82-user-agent-secret.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=46993f3f990a9436c8966a148227bdc0) ## User agent secret key It is now possible to set a secret key of your choice to the user agent used for monitoring. This allows you to easily identify the requests made by Phare in your application logs, or filter them accurately in your firewall rules. The chosen secret key is passed as a user agent parameter with the following format: ```text theme={null} Mozilla/5.0 (compatible; Phare/1.0; +https://phare.io/products/uptime; Secret=your-secret-key) ``` The user agent is left unchanged if no secret key is set: ```text theme={null} Mozilla/5.0 (compatible; Phare/1.0; +https://phare.io/products/uptime) ``` **May 4, 2025** ![Monitor certificate expiring alert rule](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/80-monitor-certificate-expiring-alert-rule.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=4c0ca0d4cd9bb7f975a1aa62bbf4e173) ## New alert event: Monitor certificate expiring You can now create alert rules to be notified when your monitor certificates are about to expire. This new feature complements the SSL certificate tracking system introduced earlier this week, giving you proactive control over your certificate renewals. How it works: * Create a **Monitor Certificate Expiring** alert rule * Select how many days in advance you want to be notified (from 1 to 60 days) * Choose which integration to use for notifications (Email, SMS, Webhook, etc.) * Get timely notifications so you never miss a certificate renewal again Like other alert rules, you can scope it to a specific project or to the entire organization, and it works with all existing integrations. **May 4, 2025** ![Monitor certificate discovered notification](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/79-monitor-certificate-discovered.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=df03766ab677168f68f8f08e78ad5fe3) ## New alert event: Monitor certificate discovered You can now create alert rules to be notified when a new certificate is discovered on any monitor. It's a great way to make sure they're getting renewed on time, or to get alerted of any unexpected changes to your monitors' SSL certificates. **May 2, 2025** ![SSL certificate tracking](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/81-certificate-discovery.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=310540b574c786158fd926c31c9906a4) ## SSL certificate tracking Phare now tracks SSL certificates as first-class objects, giving you visibility on all the certificates used in your projects. How it works: * Certificates are discovered and stored automatically when performing monitor checks * Support for multiple certificates per domain and shared certificates across monitors This allows you to quickly view all certificates used by a monitor, and all monitors using a certificate. **Apr 29, 2025** ![New alerting system](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/78-alerting-system.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=8925b86886ea2ed37cbb9c5b6838aa0e) ## New scoped alert rules system Alert policies have been replaced with a more intuitive scoped alert rules system. You can now define alert rules that apply at the organization or project level, making alerting easier to manage and more transparent. How it works: * Alert policies do not exist anymore * Alert rules can be directly created * Choose a scope for each rule: project-specific or organization-wide. This greatly simplifies the alerting system, while keeping a good level of flexibility. The [API endpoints for managing alert rules](/api-reference/platform/alert-rules/list-alert-rules) have also been updated to reflect this change, which should make it easier to manage your alert rules programmatically. **Apr 19, 2025** ![Recipient delivery logs](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/77-recipient-delivery-logs.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=2827f515f319d689483600a643ef5eef) ## Enhanced messaging reliability and logging To improve the resilience of the email notifications, a failover SMTP (Brevo) has been introduced to ensure uninterrupted delivery in case the primary SMTP (Scaleway) fails. Real-time tracking of email delivery statuses has been implemented to allow for immediate detection of undelivered emails. The Email, Telegram, and SMS integration have also been updated to provide per-recipient logs, giving you more details in case of delivery issues. **Apr 14, 2025** ![New monitoring regions](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/76-new-monitoring-regions.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=4b9c9330d5dd1e91feea7f0416a85f90) ## New monitoring regions and infrastructure overhaul After two months of rollout and testing, Phare’s newest regions, Australia, Thailand, and Brazil, are now generally available. These regions bring faster, closer monitoring to key areas across APAC and South America. All regions, new and existing, now run on an upgraded infrastructure. Expect lower latency, improved efficiency, and even more reliable insights, no changes needed. A major step forward in global monitoring, now fully live! **Apr 7, 2025** ## New Scale plan price After nearly a year of intense optimization and some seriously messy spreadsheet formulas, it's finally done: the Phare Scale plan is now just 5€, down from 49€. That’s 90% off! And it’s not just about slashing prices, it’s about making powerful, high-quality tools accessible to everyone, without locking features behind expensive enterprise plans. The pricing page has been [updated to reflect this change and clarify things](https://phare.io/pricing). Now’s the perfect time to hop on board. Don’t miss out. **Apr 2, 2025** ![Phare on Discord](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/75-phare-discord.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=4bc19e385d3c9dff1d9b2892985acf12) ## Discord community Phare now has a Discord community, because sometimes you just want to drop a quick message, rant about a bug, or throw out a wild feature idea explained in a meme. Join to chat about Phare, share feedback, report issues, or just see what’s brewing. It's also the best place to talk to the guy who writes the code and tease him about adding a dark mode (please don’t). Jump in, say hi, and have fun: [https://phare.io/discord](https://phare.io/discord) **Feb 17, 2025** ![Preview regions](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/74-preview-regions.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=fda365ce492dc3ba6365d35d5ed04e4b) ## Preview regions Six new regions are available in preview to test Phare's brand-new monitoring infrastructure. They’re free to use for the next two months but come with no guarantees yet. Choose from US West / East 🇺🇸, Japan 🇯🇵, Germany 🇩🇪, or one of the new regions, Australia 🇦🇺 and Brazil 🇧🇷. Or try all of them to help test the new infrastructure at scale. **Jan 30, 2025** ![Telegram integration](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/73-telegram-integration.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=7b852e5113a7210df22115f47d0892d4) ## Telegram integration A new integration with Telegram is now available to send notifications to your Telegram application. The integration supports sending messages to a group or a private chat, and can be used with all existing alert events. Read the [Telegram integration documentation](/integrations/telegram) to get started. **Jan 26, 2025** ![Integration logs](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/70-integration-logs.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=cdf030df56e902a9c024026cf6afac0c) ## Improved integration reliability A lot of work has been done to improve the reliability of all integrations with third-party services, including a new delivery and error logs page, failure notifications, and automatic pause for failing integrations. ### Delivery and error logs All integrations now provide a detailed logs page to help you diagnose and fix issues. ![Integration logs](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/70-integration-logs.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=cdf030df56e902a9c024026cf6afac0c) ### Failure notifications All integrations now notify the organization owner when an issue occurs. For the SMS, Email, and Webhook integrations, a detailed list of failed numbers, addresses, or requests is provided to help you identify the issue. The failure notification for the Outgoing Webhook integration is only sent if all delivery attempts have failed, which means the organization owner will be notified [1 hour and 18 minutes](https://docs.phare.io/integrations/outgoing-webhook#retry-policy) after the event creation. ![Integration issue notification](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/71-integration-issue-notification.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=062f627ceba2355f949f8196c790fc15) ### Automatic pause Integrations that have been failing more than three consecutive times in a 7-day rolling window will be automatically paused. A notification will be sent to the organization owner when this happens. **Jan 26, 2025** ## Data retention change To improve the performance of the platform and reduce unnecessary data retention, a few rules are now enforced for organizations on the **Hobby** plan: Organizations must have at least one active member in the past 6 months to keep their account active. Two reminder emails will be sent to the organization owner before the account is deactivated. The first reminder is sent 14 days before the account deactivation, and the second reminder is sent 3 days before the account deactivation. Monitors that have been failing uninterrupted for more than 48h will be automatically paused. A notification will be sent to the organization owner when a monitor is paused. These rules are only enforced for organizations on the **Hobby** plan, and are necessary to keep this plan free and sustainable for everyone. **Jan 26, 2025** ![Custom status page error](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/72-custom-status-page-error.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=77804faead128d176dcf4f707416eafd) ## Custom error pages for status pages When visiting a status page with an error (404, 500, etc.), a custom error page is now displayed to provide a better user experience, instead of redirecting users to a phare.io error page. **Jan 8, 2025** ![Password confirmation](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/69-password-confirmation-flow.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=a0b636e6c1ea22cc505a9daecac0f910) ## Account security improvements The security of your user account has been improved with the addition of a password confirmation step when updating your email address or deactivating two-factor authentication. This step ensures that you are the owner of the account and that no one else can make changes without your consent. The two-factor authentication activation flow has also been improved with the possibility to manually set up your authenticator app without having to scan a QR code. **Jan 8, 2025** ![Embed status badges customization](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/68-embed-status-badges-customization.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=917d94007a3cb3f32d0e8965caeeacd8) ## Embed status badge customization Embed status badges can now be customized with a custom background color to match your website's design. A theme selector is available to choose between light and dark mode, and a color picker to select the background color for each theme. **Jan 3, 2025** ## Embed status badges Three embeddable status badges are now available to display your status page's current status on your website. The badges do not load any third-party scripts, are free from cookies, and adapt to your website dark and light modes. #### Pulse badge The pulse badge only displays the current status of your status page without any additional information, making it perfect to build your own components around it. ![Embed pulse badges](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/65-embed-pulse-badge.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=df79af75751e13d818ea2902a2830db4) #### Static badge The static badge displays the current status of your status page with a pulse and a static label. ![Embed static badges](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/66-embed-static-badge.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=6d21299faeb011ec1076427d87116d69) #### Live badge The live badge displays the current status of your status page with a pulse and a live label. ![Embed live badges](https://mintcdn.com/phare/PK6OfMSytvlvN_a7/images/changelog/67-embed-live-badge.webp?fit=max\&auto=format\&n=PK6OfMSytvlvN_a7\&q=85\&s=36fbdea21d41e054a9450da8d7d9f9cc) # Getting started with Phare Source: https://docs.phare.io/getting-started Get up and running with the Phare platform, learn how to create your account, select a plan, and set up your first project. Ready to level up your monitoring game? This guide walks through the quick onboarding process to get started with Phare. By the end, you'll have an organization account and know how to start using Phare products to run reliable websites and APIs. ## Account Creation First things first, you need a Phare account. Head over to the [registration page](https://app.phare.io/register) and sign up in just a few clicks. Once you've created your account, watch for a confirmation email in your inbox. Click the confirmation link to verify your account and log in to Phare. Easy! ![Email verification](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/getting-started/email-verification.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=80bcd45744054f561db7416f68bec5c4) ## Plan Selection Now it's time to [choose your plan](https://phare.io/pricing). There are only two options: Hobby (free) and Scale (paid). The Hobby plan comes with lower usage limits, and does not include SMS / voice alerts and single sign-on. No long-term commitment is required, and plan changes or upgrades are available anytime. ![Plan selection](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/getting-started/plan-selection.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=e9039d4f9450672ca7a62b52689c6451) If you go with the Scale plan, you'll be prompted for your payment method. This data is not stored or accessible by Phare and is managed by the payment provider Paddle. Paddle is a trusted merchant of record. They are [PCI & SOC 2 compliant](https://security.paddle.com/) and have a strong track record of security. ## Project Creation With your plan sorted, it's time to create your first project! Think of projects as containers for organizing your resources. In Phare, everything lives either directly in your organization or within a project inside your organization. > [!TIP] > > Pro tip: To keep things tidy, try mirroring your organization's actual > structure in how you set up your projects. And remember, projects also > control who can access what. So if something should only be visible to > certain team members, give it its own project. ![Project creation](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/getting-started/project-creation.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=c33531a96d71f3dacb6e0dead5963490) Congratulations! You've completed the Phare onboarding process. Now the fun part begins: start exploring the different products and features Phare has to offer. > [card] [Uptime](/uptime/overview) > > Monitor your websites, APIs and servers with HTTP, TCP and ICMP ping checks, > handle incidents, manage certificates and create status pages # Phare Ansible Collection (Community) Source: https://docs.phare.io/integrations/ansible Setup and manage Phare with infrastructure as code using the community-built Ansible collection. ## Overview The `tealk.phare_uptime` collection allows you to manage Phare resources using Ansible as infrastructure as code. With this collection, you can automate the creation and management of projects, monitors, status pages, alert rules, maintenance windows, and more. > [!NOTE] > > The Ansible collection is an open-source community project developed and maintained by [Daniel Buck](https://git.rollenspiel.monster/tealk) and is not officially maintained by Phare. ## Getting started To install the collection using the Ansible Galaxy CLI: ```bash theme={null} ansible-galaxy collection install tealk.phare_uptime ``` You can also include it in your `requirements.yml`: ```yaml theme={null} collections: - name: tealk.phare_uptime ``` Follow the instructions and documentation available on [Ansible Galaxy](https://galaxy.ansible.com/ui/repo/published/tealk/phare_uptime/). The source code and documentation for the collection are available on a [Forgejo](https://git.rollenspiel.monster/ansible-collections/phare_uptime) instance under the AGPL-3.0 licence. # Integrate Discord with Phare Source: https://docs.phare.io/integrations/discord Set up the Phare Discord integration to receive messages in your Discord server when your websites or APIs are down. Bring your monitoring alerts right where your team hangs out! The Discord integration sends alerts directly to your chosen Discord channel, so you won't miss a beat when something needs attention. Set it up in your [integrations dashboard](https://app.phare.io/organization/apps). ## Configuration Need alerts in different Discord channels? No problem! You can create multiple Discord integrations, each pointing to a specific channel. When you set up a Discord integration, you will be redirected to Discord to authorize the Phare app and select the right Discord server and channel for your alerts. > [!TIP] > > Pro tip: If you're a member of multiple Discord servers, double-check that > you're selecting the right one during the authorization step. A name will be automatically suggested for your integration, feel free to give it a more descriptive name that helps you identify it when setting up alert rules later, especially if you're connecting to multiple channels or servers. ## Reinstallation If the integration is experiencing errors or if an update is available, you will be able to reinstall your Phare integration for Discord with a single click. This will redirect you to Discord to reauthorize the Phare integration and select the right server, channel, and up-to-date permissions. Your alert rules will remain unchanged. ![Update the Phare integration for Discord](https://mintcdn.com/phare/PNHilPgFc-zJhmys/images/integrations/discord/update-integration.webp?fit=max\&auto=format\&n=PNHilPgFc-zJhmys\&q=85\&s=10f4f5927dabe9f3535523664b565377) ## Threads & permissions To keep your Discord channels organized, Phare creates a new thread for each incident. This way, all messages related to a specific incident are grouped together, making it easy to track the status and updates without cluttering the main channel. ![Phare incident threads on Discord](https://mintcdn.com/phare/PNHilPgFc-zJhmys/images/integrations/discord/discord-threads.webp?fit=max\&auto=format\&n=PNHilPgFc-zJhmys\&q=85\&s=819ed1d432859dcd3f42f3869f67f609) This feature can only work if you allow the following permissions during the integration setup: * **View Channels**: Allows the Phare bot to join the channel you choose for the incoming-webhook * **Send Messages**: Allows the Phare bot to send messages to the channel * **Send Messages in Threads**: Allows the Phare bot to send messages in public threads * **Create Public Threads**: Allows the Phare bot to create public threads in the channel If you choose not to grant any of these permissions, the integration will send alert notifications directly to the channel instead of creating threads. ## Private Channels If you wish to receive alerts in a private channel, the Phare bot must be invited to that channel. You can do this by mentioning the bot in the channel or by using the "Invite to Channel" option in Discord. # Integrate Emails with Phare Source: https://docs.phare.io/integrations/email Set up the Phare email integration to receive alerts when your website or server is down. Good old email, still the backbone of professional communications. Phare's Email integration makes sure critical alerts land in the right inboxes. Set it up in the [integration section](https://app.phare.io/organization/apps) of your dashboard. ## Email validation To keep things secure and spam-free, only email addresses belonging to registered team members can receive alerts. Don't worry, support for generic addresses and distribution lists is on the roadmap, and you can [contact support](https://phare.io/contact) if you need a workaround in the meantime. ## Configuration You can include up to 100 organization members in each Email integration. Need to notify different groups for different alerts? Just create multiple Email integrations with the right people in each. ## Receiving Emails All alerts come from the following address: * **[alerts@phare.io](mailto:alerts@phare.io)** Email delivery is no joke! That's why Phare uses not one, but two reliable SMTP providers for failover and redundancy: * [Scaleway](https://www.scaleway.com/) * [Brevo](https://www.brevo.com/) This dual-provider approach means your critical alerts have a better chance of reaching you, even in the rare event one provider is experiencing issues. # Integrate ilert with Phare Source: https://docs.phare.io/integrations/ilert Set up the Phare integration with ilert to route monitoring alerts to your on-call team with AI-first incident management. Need proper on-call management for your monitoring alerts? The [ilert](https://www.ilert.com/?utm_campaign=316508387-Phare%20Uptime\&utm_source=integration\&utm_medium=organic) integration makes sure the right people get notified when things go wrong, with automatic escalation and resolution when your services bounce back. Set it up in your [integrations dashboard](https://app.phare.io/organization/apps). ## Pre-requisites Before you can start routing alerts to ilert, you'll need an active ilert account with permissions to create alert sources. That's it! ## ilert Setup First stop: your ilert dashboard. You'll need to create an alert source to catch those Phare alerts. 1. Head to **Alert sources** in ilert 2. Click **Create new alert source** 3. Search for "Phare.io", click the Phare.io tile and hit **Next** ![Find the Phare integration in ilert](https://mintcdn.com/phare/r17KXbJG44ZUY2Rw/images/integrations/ilert/find-ilert-phare-integration.webp?fit=max\&auto=format\&n=r17KXbJG44ZUY2Rw\&q=85\&s=8df1088fa7b60d8d553013ff5f6bec6a) 4. Give a name to your alert source and configure it as you wish ![Create and configure the Phare integration in ilert](https://mintcdn.com/phare/r17KXbJG44ZUY2Rw/images/integrations/ilert/create-phare-integration.webp?fit=max\&auto=format\&n=r17KXbJG44ZUY2Rw\&q=85\&s=c2d692d0c137dc98c5402bd61d9c8fca) 5. Once configured, you will receive an integration key for the alert source ![Phare integration key in ilert](https://mintcdn.com/phare/r17KXbJG44ZUY2Rw/images/integrations/ilert/phare-integration-key.webp?fit=max\&auto=format\&n=r17KXbJG44ZUY2Rw\&q=85\&s=78228e9a5fc9db008a728c461d14afe6) That's it for the ilert side of things. Copy the integration key somewhere safe, then follow the next steps to forward Phare alerts to the newly created ilert alert source. ## Phare Setup 1. Navigate to your [integrations dashboard](https://app.phare.io/organization/apps) 2. Find **ilert** and click **New installation** 3. Configure the **ilert** integration with a name and your **integration key** from the previous step ![Create and configure the ilert integration in Phare](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/integrations/ilert/create-ilert-integration.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=a5994428814de941a6ff95e35d9d957a) 4. Click **Create** to save your integration, the integration key is encrypted and never shown again Your ilert integration is ready to be used. You can now create alert rules to send data to ilert. ## Alert Rules 1. Head over to the [alert rules](https://app.phare.io/uptime/alert-rules) page, and ensure the project on the top left of your screen is the right one. 2. Create Alert Rules (or edit existing ones) with the following event configuration: * Incident created * Incident propagated * Incident recovered * Monitor certificate discovered * Monitor certificate expiring 3. Save your changes ![Phare alert rules for ilert](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/integrations/ilert/ilert-phare-alert-rules.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=f252b257baecbd01e3c7bdf0a6052201) ## Automatic Resolution When your service comes back online, Phare will now automatically tell ilert to resolve the alert. No manual cleanup needed! Your on-call team gets the complete story from problem to resolution, all without lifting a finger. # Phare MCP Server Source: https://docs.phare.io/integrations/mcp Connect AI assistants like Claude, ChatGPT and Cursor to Phare, and manage your monitors, incidents and status pages from a conversation. The Phare MCP server connects AI assistants like Mistral, Claude, and ChatGPT to your organization with the [Model Context Protocol](https://modelcontextprotocol.io). Check which monitors are down, open an incident during an outage, or schedule a maintenance window, directly from your conversation. Applications connected to the MCP server act as you: they have the permissions of your [role](/user-management#roles) and only access your projects. No API key is needed, you log in to Phare and approve the application the first time you connect it. Use this URL to connect an application: ``` https://mcp.phare.io/mcp ``` ## Requirements * A Phare account with a verified email address. * Access to at least one project. Admins and the owner access every project, other members access the [projects they are part of](/user-management#accessing-projects). * An application supporting remote MCP servers with OAuth, like the ones below. ## Connecting an application Select your application below for step-by-step instructions, with a link to its own MCP documentation. > [accordion] Mistral Vibe > > **1. Add the MCP server** > > In Mistral Vibe (formerly Le Chat), open **Connectors**, click **+ Add Connector** and switch to the **Custom MCP Connector** tab. Enter `phare` as the connector name and `https://mcp.phare.io/mcp` as the server URL, then click **Connect**. > > **2. Log in to Phare** > > Log in to Phare when Mistral Vibe asks you to, and [approve the connection](#approving-the-connection). > > Custom connectors are an administrator feature. On Free, Pro and Student plans, the account owner is the administrator. > > Check out the [Mistral Vibe documentation](https://docs.mistral.ai/vibe/work/connectors/mcp-connectors) for more details. > [accordion] Vibe CLI > > **1. Add the MCP server** > > Run this command in your terminal: > > ```bash theme={null} > vibe mcp add phare --url https://mcp.phare.io/mcp > ``` > > **2. Log in to Phare** > > Vibe opens your browser after adding the MCP server. Log in to Phare and [approve the connection](#approving-the-connection). > > Check out the [Vibe CLI documentation](https://docs.mistral.ai/vibe/code/cli/mcp-servers) for more details. > [accordion] Claude > > **1. Add the connector** > > Open [Phare in the Claude directory](https://claude.ai/directory/phare) and click **Connect**. > > **2. Log in to Phare** > > Log in to Phare when Claude asks you to, and [approve the connection](#approving-the-connection). > > On Team and Enterprise plans, an owner first adds Phare in **Organization settings** > **Connectors**: click **Browse connectors**, select Phare and click **Add to your team**. Members then connect it from the directory. > > Check out the [Claude documentation](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities) for more details. > [accordion] Claude Code > > **1. Add the MCP server** > > Run this command in your terminal: > > ```bash theme={null} > claude mcp add --transport http phare https://mcp.phare.io/mcp > ``` > > **2. Log in to Phare** > > In Claude Code, run `/mcp`, select **phare** and follow the steps in your browser to log in to Phare and [approve the connection](#approving-the-connection). > > Already connected Phare in Claude? Claude Code uses the same connection when you log in with your Claude account, listed as **claude.ai Phare** in `/mcp`. > > Check out the [Claude Code documentation](https://code.claude.com/docs/en/mcp) for more details. > [accordion] ChatGPT > > **1. Add the MCP server** > > Open the [ChatGPT plugins](https://chatgpt.com/plugins), click **+** and choose **Add custom MCP server**. Enter `Phare` as the name, a description, and `https://mcp.phare.io/mcp` as the URL. Choose OAuth as the authentication, accept the warning and click **Create as a plugin**. > > **2. Log in to Phare** > > ChatGPT asks you to log in to Phare the first time it uses a tool. Log in and [approve the connection](#approving-the-connection). > > On business plans, your workspace policies can restrict custom MCP servers. > > Check out the [ChatGPT documentation](https://developers.openai.com/plugins/deploy/connect-chatgpt) for more details. > [accordion] Codex > > **1. Add the MCP server** > > Run this command in your terminal: > > ```bash theme={null} > codex mcp add phare --url https://mcp.phare.io/mcp > ``` > > The Codex IDE extension uses the same configuration. > > **2. Log in to Phare** > > Run this command, then log in to Phare in your browser and [approve the connection](#approving-the-connection): > > ```bash theme={null} > codex mcp login phare > ``` > > Check out the [Codex documentation](https://learn.chatgpt.com/docs/extend/mcp) for more details. > [accordion] Cursor > > **1. Add the MCP server** > > Add the MCP server to `~/.cursor/mcp.json`, or to `.cursor/mcp.json` in your project: > > ```json theme={null} > { > "mcpServers": { > "phare": { > "url": "https://mcp.phare.io/mcp" > } > } > } > ``` > > **2. Log in to Phare** > > Restart Cursor, then open **Customize** > **MCPs** in the sidebar to log in to Phare and [approve the connection](#approving-the-connection). > > Check out the [Cursor documentation](https://cursor.com/docs/mcp) for more details. > [accordion] VS Code > > **1. Add the MCP server** > > Run **MCP: Add Server** from the Command Palette and choose **HTTP (HTTP or Server-Sent Events)**. Enter `https://mcp.phare.io/mcp` as the URL and `phare` as the server ID, then choose where to save it. > > **2. Log in to Phare** > > VS Code opens your browser when it starts the MCP server. Log in to Phare and [approve the connection](#approving-the-connection). > > Check out the [VS Code documentation](https://code.visualstudio.com/docs/agent-customization/mcp-servers) for more details. > [accordion] Zed > > **1. Add the MCP server** > > Open **Settings** > **AI** > **MCP Servers**, click **Add Server** and choose **Add Remote Server**. You can also add the MCP server to your settings file: > > ```json theme={null} > { > "context_servers": { > "phare": { > "url": "https://mcp.phare.io/mcp" > } > } > } > ``` > > **2. Log in to Phare** > > Zed asks you to authenticate with the MCP server. Log in to Phare and [approve the connection](#approving-the-connection). > > Check out the [Zed documentation](https://zed.dev/docs/ai/mcp) for more details. > [accordion] Gemini CLI > > **1. Add the MCP server** > > Add the MCP server to `~/.gemini/settings.json`: > > ```json theme={null} > { > "mcpServers": { > "phare": { > "httpUrl": "https://mcp.phare.io/mcp" > } > } > } > ``` > > **2. Log in to Phare** > > In Gemini CLI, run `/mcp auth phare`, then log in to Phare in your browser and [approve the connection](#approving-the-connection). > > Check out the [Gemini CLI documentation](https://geminicli.com/docs/tools/mcp-server/) for more details. > [accordion] OpenCode > > **1. Add the MCP server** > > Run this command in your terminal: > > ```bash theme={null} > opencode mcp add phare --url https://mcp.phare.io/mcp > ``` > > **2. Log in to Phare** > > Run this command, then log in to Phare in your browser and [approve the connection](#approving-the-connection): > > ```bash theme={null} > opencode mcp auth phare > ``` > > Check out the [OpenCode documentation](https://opencode.ai/docs/mcp-servers) for more details. > [accordion] Other applications > > Enter `https://mcp.phare.io/mcp` as the URL of a remote MCP server (Streamable HTTP) in your application. The application registers itself with Phare and opens the Phare login page. > > Applications running on your computer, like command-line tools and desktop applications, work with Phare. Web applications must be allowed by Phare first: if yours isn't, [contact support](mailto:support@phare.io). ### Approving the connection After you log in, Phare shows the name of the application, the site you will be sent to after approving, and your email address, organization and role. Click **Approve** to connect the application. > [!WARNING] > > Only approve a connection you just started yourself. Phare shows a warning when the connection was started by an application on your computer, as any application on your computer can start one. ## Using the MCP server Once connected, ask your questions in plain words. For example: * "Which monitors are down in my Production project?" * "What was the uptime of the API monitor last month?" * "Open an incident on the status page for the slow checkout, and post an update saying we are investigating." * "Schedule a maintenance window on Sunday from 2:00 to 4:00 for the database monitors." * "Create an HTTP monitor for [https://example.com](https://example.com) checking every minute." The application calls [`whoami`](#account) first to find your role and projects, then the [tools](#tools) it needs to answer. > [!TIP] > > If you have several projects, name the project in your request so the application uses the right one. ## Permissions The MCP server follows your [role](/user-management#roles) and your projects, so an application can never do more than you can in the dashboard: * **Tools**: The application only sees the tools your role can use. Viewers only see the tools reading data, responders also see the tools managing incidents and maintenance windows. Phare checks your permissions on every tool call, so a change to your role applies right away. * **Projects**: The application only accesses the projects you can access. Most tools act on one of them through their `project_id` argument. * **Credentials**: The MCP server can't manage API keys, invitations, members, roles, single sign-on, the organization settings or billing. Use the dashboard for these. Each tool tells the application whether it reads, creates, or changes and deletes data. Most applications ask for your confirmation before changing or deleting anything. ## Tools The tools run the endpoints of the [Phare API](/api-reference/introduction), with the same arguments, validation and responses. Click a tool to see all its arguments in the API reference. The alert rules, monitors, reports, incidents, maintenance windows and status pages tools act inside a project and require a `project_id` argument: the ID of one of your projects, found with `whoami` or `list_projects`. List tools return 20 results per page by default, up to 100 with the `per_page` argument. The application gets the next results with the `page` argument. ### Account | Tool | Description | Permission | | :- | :- | :- | | `whoami` | Get your account, role, organization, permissions and the projects you can access. Called first. | Any role | ### Projects | Tool | Description | Permission | | :- | :- | :- | | [`list_projects`](/api-reference/platform/projects/list-projects) | List the projects you can access. | `projects:read` | | [`get_project`](/api-reference/platform/projects/get-a-project) | Get a project by ID. | `projects:read` | | [`create_project`](/api-reference/platform/projects/create-a-project) | Create a project. | `projects:write` | | [`update_project`](/api-reference/platform/projects/update-a-project) | Update a project. | `projects:write` | | [`delete_project`](/api-reference/platform/projects/delete-a-project) | Delete a project with all its monitors, incidents, status pages and alert rules. | `projects:write` | ### Members | Tool | Description | Permission | | :- | :- | :- | | [`list_users`](/api-reference/platform/users/list-users) | List the members of your organization. | `members:read` | | [`get_user`](/api-reference/platform/users/get-a-user) | Get a member of your organization by ID. | `members:read` | ### Integrations | Tool | Description | Permission | | :- | :- | :- | | [`list_integrations`](/api-reference/platform/integrations/list-integrations) | List the integrations of an app, like Slack or Discord. | `integrations:read` | | [`get_integration`](/api-reference/platform/integrations/get-an-integration) | Get an integration by ID. | `integrations:read` | | [`create_integration`](/api-reference/platform/integrations/create-an-integration) | Create an integration. | `integrations:write` | | [`update_integration`](/api-reference/platform/integrations/update-an-integration) | Update an integration. | `integrations:write` | | [`delete_integration`](/api-reference/platform/integrations/delete-an-integration) | Delete an integration not used by an alert rule. | `integrations:write` | ### Alert rules | Tool | Description | Permission | | :- | :- | :- | | [`list_alert_rules`](/api-reference/platform/alert-rules/list-alert-rules) | List the alert rules of the project and the organization-wide alert rules. | `alert_rules:read` | | [`get_alert_rule`](/api-reference/platform/alert-rules/get-an-alert-rule) | Get an alert rule by ID. | `alert_rules:read` | | [`create_alert_rule`](/api-reference/platform/alert-rules/create-an-alert-rule) | Create an alert rule. | `alert_rules:write` | | [`update_alert_rule`](/api-reference/platform/alert-rules/update-an-alert-rule) | Update an alert rule. | `alert_rules:write` | | [`delete_alert_rule`](/api-reference/platform/alert-rules/delete-an-alert-rule) | Delete an alert rule. | `alert_rules:write` | ### Monitors | Tool | Description | Permission | | :- | :- | :- | | [`list_monitors`](/api-reference/uptime/monitors/list-monitors) | List the monitors of the project. | `monitors:read` | | [`get_monitor`](/api-reference/uptime/monitors/get-a-monitor) | Get a monitor by ID. | `monitors:read` | | [`get_monitor_report`](/api-reference/uptime/monitors/get-a-monitor-report) | Get the uptime statistics of a monitor, over up to one year. | `monitors:read` | | [`create_monitor`](/api-reference/uptime/monitors/create-a-monitor) | Create a monitor. | `monitors:write` | | [`update_monitor`](/api-reference/uptime/monitors/update-a-monitor) | Update a monitor. | `monitors:write` | | [`pause_monitor`](/api-reference/uptime/monitors/pause-a-monitor) | Pause a monitor. | `monitors:write` | | [`resume_monitor`](/api-reference/uptime/monitors/resume-a-monitor) | Resume a paused monitor. | `monitors:write` | | [`delete_monitor`](/api-reference/uptime/monitors/delete-a-monitor) | Delete a monitor. | `monitors:write` | ### Reports | Tool | Description | Permission | | :- | :- | :- | | [`get_report`](/api-reference/uptime/reports/get-a-report) | Get the uptime statistics of all the monitors of the project, over up to one year. | `reports:read` | ### Incidents | Tool | Description | Permission | | :- | :- | :- | | [`list_incidents`](/api-reference/uptime/incidents/list-incidents) | List the incidents of the project. | `incidents:read` | | [`get_incident`](/api-reference/uptime/incidents/get-an-incident) | Get an incident by ID. | `incidents:read` | | [`create_incident`](/api-reference/uptime/incidents/create-an-incident) | Create an incident. | `incidents:write` | | [`update_incident`](/api-reference/uptime/incidents/update-an-incident) | Update an incident. | `incidents:write` | | [`recover_incident`](/api-reference/uptime/incidents/recover-an-incident) | Recover an incident now. | `incidents:write` | | [`delete_incident`](/api-reference/uptime/incidents/delete-an-incident) | Delete an incident. | `incidents:write` | ### Incident updates | Tool | Description | Permission | | :- | :- | :- | | [`list_incident_updates`](/api-reference/uptime/incidents/updates/list-incident-updates) | List the updates of an incident. | `incidents:read` | | [`get_incident_update`](/api-reference/uptime/incidents/updates/get-an-incident-update) | Get an incident update by ID. | `incidents:read` | | [`create_incident_update`](/api-reference/uptime/incidents/updates/create-an-incident-update) | Post an incident update, an update with the `resolved` state recovers the incident. | `incidents:write` | | [`update_incident_update`](/api-reference/uptime/incidents/updates/update-an-incident-update) | Update an incident update. | `incidents:write` | | [`delete_incident_update`](/api-reference/uptime/incidents/updates/delete-an-incident-update) | Delete an incident update. | `incidents:write` | ### Maintenance windows | Tool | Description | Permission | | :- | :- | :- | | [`list_maintenance_windows`](/api-reference/uptime/maintenance-windows/list-maintenance-windows) | List the maintenance windows of the project. | `maintenance_windows:read` | | [`get_maintenance_window`](/api-reference/uptime/maintenance-windows/get-a-maintenance-window) | Get a maintenance window by ID. | `maintenance_windows:read` | | [`create_maintenance_window`](/api-reference/uptime/maintenance-windows/create-a-maintenance-window) | Schedule a maintenance window. | `maintenance_windows:write` | | [`update_maintenance_window`](/api-reference/uptime/maintenance-windows/update-a-maintenance-window) | Update a maintenance window. | `maintenance_windows:write` | | [`complete_maintenance_window`](/api-reference/uptime/maintenance-windows/complete-a-maintenance-window) | Complete a maintenance window in progress. | `maintenance_windows:write` | | [`cancel_maintenance_window`](/api-reference/uptime/maintenance-windows/cancel-a-maintenance-window) | Cancel a scheduled or in progress maintenance window. | `maintenance_windows:write` | | [`delete_maintenance_window`](/api-reference/uptime/maintenance-windows/delete-a-maintenance-window) | Delete a maintenance window. | `maintenance_windows:write` | ### Status pages | Tool | Description | Permission | | :- | :- | :- | | [`list_status_pages`](/api-reference/uptime/status-pages/list-status-pages) | List the status pages of the project. | `status_pages:read` | | [`get_status_page`](/api-reference/uptime/status-pages/get-a-status-page) | Get a status page by ID. | `status_pages:read` | | [`get_status_page_current_status`](/api-reference/uptime/status-pages/get-a-status-page-current-status) | Get the current status of a status page. | `status_pages:read` | | [`create_status_page`](/api-reference/uptime/status-pages/create-a-status-page) | Create a status page. | `status_pages:write` | | [`update_status_page`](/api-reference/uptime/status-pages/update-a-status-page) | Update a status page. | `status_pages:write` | | [`delete_status_page`](/api-reference/uptime/status-pages/delete-a-status-page) | Delete a status page. | `status_pages:write` | ## Disconnecting an application Your applications are listed in the connected applications section of your [user settings](https://app.phare.io/user/settings#connected-applications), with the site they send you to and when they were last active. Click the trash icon next to an application to disconnect it, it loses access to your account until you connect it again. Phare also disconnects all your applications when: * You change your password or your email address, or reset your password. * You enable or disable two-factor authentication. * Single sign-on is enabled or removed for your organization. > [!NOTE] > > An application unused for 30 days must be connected again. ## Security You receive an email when an application is connected to your account, with the date, IP address and browser of the connection. If the connection is unexpected, [disconnect the application](#disconnecting-an-application), reset your password and contact [support@phare.io](mailto:support@phare.io) right away. Phare uses the OAuth authorization code flow with PKCE. Access tokens expire after one hour, and only the known web applications and the applications running on your computer can connect. ## Rate limiting The MCP server is rate limited to **100 requests per minute** across the organization. All members share the same limit, separate from the [API rate limit](/api-reference/introduction#rate-limiting). *** If a tool is missing or a custom rate limit is needed, [contact support](mailto:support@phare.io). Phare can help find a solution that fits the use case. # Phare NixOS Module (Community) Source: https://docs.phare.io/integrations/nixos Declare and manage Phare resources with infrastructure as code using the community-built NixOS module. ## Overview The `phare-nix` module allows you to manage Phare resources using NixOS as infrastructure as code. With this module, you can automate the creation, update, and management of monitors and maintenance windows declaratively in your NixOS configuration. > [!NOTE] > > The NixOS module is an open-source community project developed and maintained by [Pascal Wittmann](https://codeberg.org/pSub) and is not officially maintained by Phare. ## Getting started The module is distributed as a [Nix Flake](https://wiki.nixos.org/wiki/Flakes). To include it, add `phare-nix` to your flake inputs and import the module into your system configuration: ```nix theme={null} { inputs = { nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable"; phare-nix.url = "git+https://codeberg.org/pSub/phare-nix"; }; outputs = { self, nixpkgs, phare-nix }: { nixosConfigurations.some-server = nixpkgs.lib.nixosSystem { modules = [ ./configuration.nix phare-nix.nixosModules.phare ]; }; }; } ``` Follow the configuration instructions and documentation available in the [phare-nix repository on Codeberg](https://codeberg.org/pSub/phare-nix). The source code for the module is open source under the MIT license. # Integrate Ntfy.sh with Phare Source: https://docs.phare.io/integrations/ntfy Set up the Phare integration with Ntfy.sh to receive alerts on your preferred device. Ntfy is a simple and open-source notification service that allows you to receive push notifications on your devices. With the Phare integration for Ntfy, you can get real-time alerts about your monitored services directly to your preferred platform. Configure it in your [integrations dashboard](https://app.phare.io/organization/apps). ## Pre-requisites Before you can start receiving Ntfy notifications from Phare, install the app on your device or create an account in the [web client](https://ntfy.sh/). Once you're set up, create a topic for the notifications. > [!WARNING] > > Keep in mind that all Ntfy topics are public, so choose a unique name to avoid unwanted noise, or create your own server protected with an access token. ## Configuration To configure the integration in Phare, head over to your [integrations dashboard](https://app.phare.io/organization/apps), find Ntfy in the list, and click the **New installation** button. Fill in the topic you created earlier and custom server hostname if required. If your topic is protected, turn on the access token and paste a token of your ntfy account. The token is encrypted and never shown again once saved. ![Ntfy configuration with an access token](https://mintcdn.com/phare/_UXS79HzXpRX3QU3/images/integrations/ntfy/ntfy-configuration.avif?fit=max\&auto=format\&n=_UXS79HzXpRX3QU3\&q=85\&s=c425afa3dfb912868dc68e83a05d6006) ## Usage With everything connected, you can choose Ntfy as a notification channel when creating or editing alert rules. The best part? You can set different priority levels for different types of alerts, making that 3AM wake-up notification reserved for truly critical issues. You can learn more about Ntfy priority levels in the [Ntfy documentation](https://docs.ntfy.sh/publish/#message-priority). # Integrate Outgoing Webhooks with Phare Source: https://docs.phare.io/integrations/outgoing-webhook Receive alerts by webhooks on third-party tools or build your own integration. Want to build your own custom integration or connect Phare to a tool that isn’t officially supported? Outgoing webhooks are your best friend! They send HTTP callbacks with your alert data to any endpoint you specify, perfect for DIY integrations, logging or connecting to specialized systems. ## Configuration Setting up an outgoing webhook is straightforward, you just need two pieces of information: * **Callback URL**: Where should the data be sent? This could be an endpoint in your own application or a third-party service that accepts webhooks. * **Signing secret**: A secret key that proves the data came from Phare and wasn't tampered with along the way. A secure signing secret is automatically generated for you, but you're welcome to use your own if you prefer. Copy it to your application before saving: the secret is encrypted and never shown again. ![Outgoing webhooks installation](https://mintcdn.com/phare/_UXS79HzXpRX3QU3/images/integrations/outgoing-webhook/outgoing-webhook-installation.avif?fit=max\&auto=format\&n=_UXS79HzXpRX3QU3\&q=85\&s=401d7b341196394a753b154af606ec48) ## Using the integration Once your webhook is set up, you can connect it to alert rules in your projects. A default JSON payload based on the alert event you've chosen will be generated, customize it as needed to fit your specific use case. ![Outgoing webhooks alert rule](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/integrations/outgoing-webhook/outgoing-webhook-alert-rule.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=b1ec91b82606e551d1bfb7ff4ea08349) ## Delivery details Outgoing webhooks are sent as `POST` requests with a 30-second timeout. Each request includes: * `Content-Type: application/json` * `User-Agent: Phare 1.0 (+https://phare.io)` * `X-Phare-Request-Id`: Unique delivery ID * `X-Phare-Request-Event`: Alert event key * `X-Phare-Request-Timestamp`: Unix timestamp * `X-Phare-Request-Signature`: HMAC-SHA256 signature The request body is the rendered JSON schema from the Payload customization section below. ## Payload customization [Outgoing webhook editor](https://player.mediadelivery.net/embed/238508/4147abf7-d8ef-4c1d-95fb-b86b949b2a43?autoplay=false\&loop=false\&muted=false\&preload=true\&responsive=true) You can customize the payload that will be sent to your webhook endpoint by defining a valid JSON schema with placeholders like `{{ incident.slug }}`. When the webhook is sent, Phare swaps the placeholders with real values. > [!NOTE] > > JSON keys do not support placeholders. ### Example template ```json theme={null} { "event": "uptime.monitor.created", "monitor": { "id": "{{ monitor.id }}", "name": "{{ monitor.name }}", "status": "{{ monitor.status }}", "protocol": "{{ monitor.protocol }}", "request": "{{ monitor.request }}", "regions": "{{ monitor.regions }}", "interval": "{{ monitor.interval }}", "incident_confirmations": "{{ monitor.incident_confirmations }}", "recovery_confirmations": "{{ monitor.recovery_confirmations }}" }, "project": { "id": "{{ project.id }}", "name": "{{ project.name }}", "slug": "{{ project.slug }}" } } ``` ### Placeholder formats When a placeholder is the only thing in a string, the value keeps its original type: `"{{ monitor.tags }}"` becomes a real JSON array, `"{{ monitor.interval }}"` a number, and empty values `null`. Mixed with other text, the value is inserted as text instead, so `"Tags: {{ monitor.tags }}"` becomes `"Tags: [\"api\",\"production\"]"`. ### Looping over list of entities To define a schema for an entity that is part of a list, use `$each` and `$item`. The loop name should match the entity list name you want to iterate, such as `affected_monitors`. In the entity schema, use the `item` variable to access the current item properties. ```json theme={null} { "affected_monitors": { "$each": "affected_monitors", "$item": { "id": "{{ item.id }}", "name": "{{ item.name }}" } } } ``` Nested loops are not currently supported. ### Available entities by event > [accordion] Monitor Created > > * `monitor` > * `project` > [accordion] Monitor Deleted > > * `monitor` > * `project` > [accordion] Monitor Certificate Discovered > > * `certificate` > * `monitor` > * `project` > [accordion] Monitor Certificate Expiring > > * `certificate` > * `monitor` > * `project` > [accordion] Incident Created > > * `incident` > * `project` > * `affected_monitors` (list) > [accordion] Incident Recovered > > * `incident` > * `project` > * `affected_monitors` (list) > [accordion] Incident Propagated > > * `incident` > * `project` > * `propagated_monitor` (the newly affected monitor) > * `affected_monitors` (list) > [accordion] Incident Partially Recovered > > * `incident` > * `project` > * `recovered_monitor` (the recovered monitor) > * `affected_monitors` (list) > [accordion] Incident Comment Created > > * `comment` > * `creator` > * `incident` > * `project` > * `affected_monitors` (list) > [accordion] Incident Update Published > > * `update` > * `creator` > * `incident` > * `project` > * `affected_monitors` (list) ### Available fields by object Dates are ISO 8601 strings in UTC, such as `2026-10-17T15:32:48Z`. > [accordion] incident > > | Field | Type | What it means | > | :- | :- | :- | > | `id` | Integer | Unique incident ID | > | `slug` | String | Short incident code | > | `title` | String | Incident title | > | `description` | String or null | Incident description | > | `state` | String | Current state: `unknown`, `investigating`, `identified`, `monitoring`, or `resolved` | > | `status` | String | Current status: `ongoing`, `recovering`, or `recovered` | > | `impact` | String | Impact level: `unknown`, `operational`, `maintenance`, `degraded_performance`, `partial_outage`, or `major_outage` | > | `tags` | Array of strings | Names of associated tags, `[]` when there are none | > [accordion] monitor > > | Field | Type | What it means | > | :- | :- | :- | > | `id` | Integer | Unique monitor ID | > | `name` | String | Monitor name | > | `status` | String | Current status: `fetching`, `online`, `offline`, `partial`, or `paused` | > | `protocol` | String | Protocol type: `http`, `tcp`, or `icmp` | > | `request` | Object | Request configuration, which depends on the protocol (for example `method` and `url` for HTTP monitors) | > | `regions` | Array of strings | Regions used for checks, such as `["eu-deu-fra"]` | > | `interval` | Integer | Check interval (seconds) | > | `incident_confirmations` | Integer | Confirmations required to open an incident | > | `recovery_confirmations` | Integer | Confirmations required to resolve an incident | > | `region_threshold` | Integer | Number of regions that must fail before an incident is confirmed | > | `tags` | Array of strings | Names of associated tags, `[]` when there are none | > [accordion] project > > | Field | Type | What it means | > | :- | :- | :- | > | `id` | Integer | Project ID | > | `name` | String | Project name | > | `slug` | String | Project slug | > [accordion] certificate > > | Field | Type | What it means | > | :- | :- | :- | > | `serial_number` | String | Certificate serial number, in colon-separated hexadecimal | > | `subject_common_name` | String or null | Common name | > | `subject_alternative_names` | Array of strings | Alternative names | > | `issuer_common_name` | String or null | Issuer name | > | `issuer_organization` | String or null | Issuer organization | > | `not_before` | Date string | Valid from | > | `not_after` | Date string | Valid until | > [accordion] comment > > | Field | Type | What it means | > | :- | :- | :- | > | `id` | Integer | Comment ID | > | `content` | String | Comment content | > [accordion] update > > | Field | Type | What it means | > | :- | :- | :- | > | `id` | Integer | Update ID | > | `state` | String | Update state: `unknown`, `investigating`, `identified`, `monitoring`, or `resolved` | > | `content` | String | Update content | > [accordion] creator > > | Field | Type | What it means | > | :- | :- | :- | > | `type` | String | Creator type | > | `label` | String | Display label | ## Webhook security Trust but verify! Phare outgoing webhooks come with built-in security through HMAC-SHA256 signatures. This ensures the payloads you receive: 1. Actually came from Phare 2. Haven't been tampered with in transit 3. Aren't being replayed from previous requests To verify a webhook's authenticity, compute the HMAC-SHA256 of this concatenated string: ```text theme={null} {version}:{timestamp}:{payload} ``` The version is always `v0` (this will be bumped if the algorithm ever changes). You'll find the timestamp in the `X-Phare-Request-Timestamp` header and the signature in the `X-Phare-Request-Signature` header. You can also use `X-Phare-Request-Id` and `X-Phare-Request-Event` to correlate deliveries. Make sure to use the raw request body, re-serializing parsed JSON can change escaping (like `\/` in URLs) and break the signature. Here are some code examples to help you implement verification: ```javascript Node.js theme={null} const crypto = require('crypto'); const express = require('express'); app.post('/webhook', express.raw({ type: 'application/json' }), (req, res) => { const secret = 'your-signing-secret'; const version = 'v0'; const timestamp = req.headers['x-phare-request-timestamp']; const signature = req.headers['x-phare-request-signature']; const payload = version + ':' + timestamp + ':' + req.body.toString('utf8'); const hash = crypto.createHmac('sha256', secret) .update(payload) .digest('hex'); if (hash === signature) { console.log('Signature verified'); } else { console.log('Signature verification failed'); } }) ``` ```php PHP theme={null} [!TIP] > > Pro security tip: Always check that the timestamp isn't too old, it is recommended > to reject a webhook older than 5 minutes to prevent replay attacks. ## Retry policy Network hiccups happen, which is why Phare outgoing webhooks don't give up easily. If your endpoint doesn't respond with a 2xx status code within 30 seconds, it will be retried up to four times (five attempts total) using an exponential backoff strategy: 1. First attempt: Immediate delivery 2. First retry: After 1 minute 3. Second retry: After 5 minutes 4. Third retry: After 10 minutes 5. Final retry: After 1 hour This means that from first attempt to last retry, your webhook could arrive anytime within a 1 hour and 18 minute window (including timeouts). ## Debugging Webhooks not working as expected? Logs are available with the request and response details making troubleshooting a breeze, you only need to click the row you would like to inspect. ![Outgoing webhooks logs](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/integrations/outgoing-webhook/outgoing-webhook-logs.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=9899416efb25d257e729276d80e1b94e) # Overview Source: https://docs.phare.io/integrations/overview Seamlessly connect your favorite apps and services with Phare Phare plays nicely with other tools, making it easy to integrate with your preferred apps and services. Whether you want to receive alerts in your favorite chat app, or send JSON data to a third-party service, you should be covered. Setting up integrations is a breeze, visit your [integrations dashboard](https://app.phare.io/organization/apps) to get started. Create as many connections as you need to ensure the right people have access to the right information. Integrations can also be created with the [create an integration](/api-reference/platform/integrations/create-an-integration) endpoint. ![Phare integrations](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/integrations/overview/phare-integrations.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=52840aa67c496b8397d5aef1eebcbe87) The credentials of your integrations, such as access tokens, keys and signing secrets, are encrypted and never shown again once saved, not in the dashboard or the API. ## Alert integrations Alert integrations are notification channels that can be used when configuring [alert rules](/uptime/alerting). By choosing the right integration for each alert rule, you can make sure the right people get notified on their preferred platforms. Here's the list of available alert integrations: > [card] [Discord](/integrations/discord) > [card] [Email](/integrations/email) > [card] [ilert](/integrations/ilert) > [card] [Ntfy](/integrations/ntfy) > [card] [Outgoing webhooks](/integrations/outgoing-webhook) > [card] [Pushover](/integrations/pushover) > [card] [SMS](/integrations/sms) > [card] [Slack](/integrations/slack) > [card] [Telegram](/integrations/telegram) ### Resilience All alert integrations are designed to be resilient and deliver notifications during critical moments. An aggressive retry strategy ensures that if any notification fails to send, it will be retried until it goes through. This means you can rest easy knowing that alert recipients are notified, even if there are temporary hiccups in the connection or with third-party services. In case a notification still fails after multiple attempts, Phare will log the error and notify the organization owner by email, so action can be taken if needed. Emails are sent through two different SMTP providers, [Scaleway](https://www.scaleway.com/) and [Brevo](https://www.brevo.com/), ensuring redundancy and reliability. If one provider experiences issues, the other will step in to deliver your alerts. ### Detailed logs ![Phare alert integrations logs](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/integrations/overview/alert-integration-logs.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=ec3dd4f15b15b02c73e2b39b3f6ff263) Detailed logs of all sent notifications are available in the Phare dashboard, so you can easily track the status of your alerts and troubleshoot any issues. *** Is a favorite tool missing from this list? [Contact support](https://phare.io/contact) to have it added to the roadmap. # Integrate Pushover with Phare Source: https://docs.phare.io/integrations/pushover Set up the Phare integration with Pushover to receive alerts on your preferred device. Want your monitoring alerts delivered straight to your pocket? The Pushover integration lets you receive instant notifications on your phone, tablet, or desktop. Configure it in your [integrations dashboard](https://app.phare.io/organization/apps). ## Pre-requisites Before you can start receiving Pushover notifications from Phare, you'll need two things: 1. A Pushover account (they have a one-time purchase model, no subscriptions!) 2. A Pushover application set up to connect with Phare You can find your user key in the [Pushover dashboard](https://pushover.net/), and create a new application via the link at the bottom of that page. Feel free to customize your app however you like, or use these ready-made settings: * Name: Phare * Description: Receive notifications from Phare.io * URL: [https://phare.io](https://phare.io) * Icon: [Phare logo](https://phare.io/img/logo-pushover.png) ![Pushover app creation](https://mintcdn.com/phare/Jh1uiqHFo-IwwO2b/images/integrations/pushover/pushover-app-creation.webp?fit=max\&auto=format\&n=Jh1uiqHFo-IwwO2b\&q=85\&s=1e0b67cd9a6368f65f2c68602d9e4046) ## Configuration Setting up the integration is simple, just connect the dots between Phare and Pushover by adding your user key and the API key from your newly created Pushover application. Both keys are encrypted and never shown again once saved. ![Pushover configuration](https://mintcdn.com/phare/_UXS79HzXpRX3QU3/images/integrations/pushover/pushover-configuration.avif?fit=max\&auto=format\&n=_UXS79HzXpRX3QU3\&q=85\&s=bc223a991111bb212062293916398c4e) ## Usage With everything connected, you can choose Pushover as a notification channel when creating or editing alert rules. One of the coolest features? You can set different priority levels for different types of alerts, making that 3AM wake-up call reserved for truly critical issues. If you choose the `Emergency` priority level, you'll need to specify two additional parameters: * `retry`: How often (in seconds) the alert should repeat * `expire`: How long (in seconds) the alert should continue trying before giving up These parameters help ensure critical alerts don't go unnoticed, and you can learn more about them in the [Pushover API documentation](https://pushover.net/api#priority). ![Pushover alert rule configuration](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/integrations/pushover/pushover-alert-rule.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=e035d3e8204a90be3003624a51c5cfcb) # Integrate Slack with Phare Source: https://docs.phare.io/integrations/slack Set up the Phare integration for Slack to receive a message in your Slack workspace when your website or server is down. Keep your team in the loop with the Phare integration for Slack! Get alerts delivered directly to your team's go-to communication hub, where the conversations already happen. ## Installation Getting started is easy. Head over to your [integrations dashboard](https://app.phare.io/organization/apps), find Slack in the list, and click the **New installation** button. ![Slack installation](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/integrations/slack/slack-installation.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=14296e1be15a448d234d0e0c96f35a9e) You'll be redirected to Slack's authorization page where you can give Phare permission to send those important notifications to your workspace. ## Configuration Each Slack installation connects to one channel, but don't worry, you can create multiple integrations if you want alerts in different channels. Maybe critical issues go to #incidents while minor hiccups go to #monitoring? The choice is yours! > [!TIP] > > Pro tip: If you belong to several Slack workspaces, double-check you're connecting to the right one during setup. A default name will be suggested for your integration. Feel free to change it to something more descriptive, especially helpful when setting up multiple Phare integrations for Slack. ![Slack configuration](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/integrations/slack/slack-configuration.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=90467950ca212b1541bdc25b2b4ef05a) ## Receiving Slack messages When an alert rule triggers, Phare will send an informative message to your selected Slack channel with all the details your team needs. To learn more about configuring when and how these alerts trigger, check out the [alerting documentation](/uptime/alerting). ![Slack notification](https://mintcdn.com/phare/Jh1uiqHFo-IwwO2b/images/integrations/slack/slack-notification.webp?fit=max\&auto=format\&n=Jh1uiqHFo-IwwO2b\&q=85\&s=68c7783a76d69415852388fe4a141fed) ## Privacy Phare only shares the minimum information needed with Slack to deliver your notifications. Phare stores your workspace name, identifier, and an access token for sending messages. For the full details on how your data is handled, take a look at the [privacy policy](https://phare.io/legal/privacy-policy). ## Reinstallation If the integration is experiencing errors or if an update is available, you will be able to reinstall your Phare integration for Slack with a single click. This will redirect you to Slack to reauthorize the Phare integration and select the right server, channel, and up-to-date permissions. Your alert rules will remain unchanged. ![Update the Phare integration for Slack](https://mintcdn.com/phare/et-MvizKiM5UTEx8/images/integrations/slack/update-integration.webp?fit=max\&auto=format\&n=et-MvizKiM5UTEx8\&q=85\&s=51a55f9faad40b55d039d22d7afa2f70) ## Threads & private channels To keep your Slack channels organized, Phare creates a new thread for each incident. This way, all messages related to a specific incident are grouped together, making it easy to track the status and updates without cluttering the main channel. ![Phare incident threads on Slack](https://mintcdn.com/phare/et-MvizKiM5UTEx8/images/integrations/slack/slack-threads.webp?fit=max\&auto=format\&n=et-MvizKiM5UTEx8\&q=85\&s=0547b6b8756de951033556e5ebab9ef2) If you wish to receive alerts as threads in a private channel, the Phare bot must be invited to that channel. You can do this by inviting the Phare bot to your private channel with the following command: ``` /invite @phare ``` # Integrate SMS with Phare Source: https://docs.phare.io/integrations/sms Set up the Phare SMS integration to receive a message on your phone when your website or server is down. > [!WARNING] > > This integration is only available with a Scale plan subscription and in selected countries When email just won't cut it, and you need alerts that grab attention immediately, the SMS integration delivers critical notifications straight to your phone. Configure it in the [integration section](https://app.phare.io/organization/apps) of your dashboard. ## Phone number validation For security and to prevent misuse, each organization member needs to verify their phone number before receiving alerts. It's simple, just visit the [user settings](https://app.phare.io/user/settings) page and follow the verification steps. ![Add phone number](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/integrations/sms/add-phone-number.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=2ad66cbddb2d830ab0fb2ccc059206a3) ## Configuration You can include up to 100 organization members in each SMS integration. When searching for members, you'll see instantly who has a verified phone number ready to go. If someone hasn't verified a number yet, it is still possible to add them. They will receive alerts after completing verification. ![SMS configuration](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/integrations/sms/sms-configuration.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=42c010f43330ed979b73d955f27085a3) ## Receiving SMS Team members will receive a text message from the **Phare** originator, which is a special sender ID that identifies the message as coming from Phare. The countries below do not support sender IDs, the SMS will come from a phone number instead. Phone numbers used until April 20th 2026: | Country | Number | | - | - | | Canada | +1 902-912-5871 | | United States of America | +1 262-398-3007 | Phone numbers used starting April 20th: | Country | Number | | - | - | | Canada | +1 581-901-2094 | | United States of America | +1 646-558-4954 | ## Supported countries Currently, the SMS integration works in the following countries: > [accordion] Asia > > * India > [accordion] Europe > > * Austria > * Belgium > * Croatia > * Denmark > * Estonia > * Finland > * France > * Germany > * Netherlands > * Norway > * Poland > * Portugal > * Slovenia > * Spain > * Sweden > * Switzerland > * United Kingdom > [accordion] North America > > * Canada > * United States of America ## Request a new country Need SMS alerts in a country that isn’t listed? It typically takes three business days to add a new country, but it depends on the local regulations. Each country requires specific compliance checks to ensure 24/7 deliverability. [Contact Phare support](https://phare.io/contact) to request adding a new country. # Integrate Telegram with Phare Source: https://docs.phare.io/integrations/telegram Set up the Phare Telegram integration to receive alerts when your website or server is down. Love the privacy and simplicity of Telegram? This integration brings Phare alerts directly to your Telegram chats, perfect for groups that prefer its secure, lightweight messaging experience. Set it up in your [integrations dashboard](https://app.phare.io/organization/apps). ## Configuration After creating your Telegram integration in Phare, you'll get two convenient options: * **Individual notifications**: A link/QR code that connects the Phare bot to your personal Telegram account. Share this with anyone in your organization who wants alerts on individual accounts. * **Group notifications**: A link/QR code for adding the bot to an existing Telegram group, ideal for team-wide monitoring alerts. ![Telegram configuration](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/integrations/telegram/telegram-configuration.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=aa547ee94da264c78d2cd97349961125) Simply open the link or scan the QR code, then follow the prompts on your device. Once connected, you'll receive a confirmation message from the Phare bot. ![Telegram start](https://mintcdn.com/phare/Jh1uiqHFo-IwwO2b/images/integrations/telegram/telegram-start.webp?fit=max\&auto=format\&n=Jh1uiqHFo-IwwO2b\&q=85\&s=b266a143e8444b4058c95c8317bb3e10) > [!WARNING] > > Security note: You can't add the Phare bot by searching for it directly from the Telegram app, you must use the provided links or QR codes. This prevents unauthorized access to your monitoring alerts. ## Usage That's it! Your Telegram account is now ready to receive Phare alerts. If you ever need to stop receiving notifications, just send the `/stop` command to the Phare bot and delete the conversation. # Phare Terraform Provider Source: https://docs.phare.io/integrations/terraform Setup Phare with infrastructure as code using the official Terraform provider. ## Overview Phare maintains a first-party Terraform provider allowing you to manage your resources using infrastructure as code. With this provider, you can automate the creation and management of projects, monitors, status pages, alert rules, and more. ![Terraform provider Phare in beta](https://mintcdn.com/phare/h2hj49DncSB3RBiE/images/integrations/terraform/terraform-provider-phare-beta.avif?fit=max\&auto=format\&n=h2hj49DncSB3RBiE\&q=85\&s=1f169a2c372ae77b03e88c2d7748459f) ## Getting started To get started with the Phare Terraform provider, follow the instructions and documentation available on the [Terraform registry](https://registry.terraform.io/providers/phare/phare/latest/docs). The source code for the provider is open source under the MIT licence and available on [GitHub](https://github.com/phare/terraform-provider-phare). # Introduction to the Phare Documentation Source: https://docs.phare.io/introduction Discover how Phare can help with HTTP, TCP and ICMP ping monitoring for websites and servers, incident management, and much more. In this documentation, you'll find everything you need to know about setting up, configuring, and using Phare to its fullest potential. Whether you're an internet veteran or just getting started with websites, this guide walks you through every step of the process. > [card] [Getting started](/getting-started) > > Set up your account in a couple of minutes > [card] [API Reference](/api-reference/introduction) > > Create programmatic interactions with the Phare API > [card] [Uptime](/uptime/overview) > > Monitor your websites and servers, manage incidents and create status pages > [card] [Integrations](/integrations/overview) > > Seamlessly connect your favorite apps and services with Phare # Alerting and Alert Rules Source: https://docs.phare.io/uptime/alerting Learn how to configure alert rules with Phare Uptime. Stay in the loop with Phare's [real-time notification system](https://phare.io/products/uptime/alerting). Whether it's a sudden outage, an expiring SSL certificate, or an incident update, the flexible alert rules system ensures the right people get the right information at the right time. [Create an alert rule](https://iframe.mediadelivery.net/embed/238508/ca22ec6a-67ce-4309-9b8f-16fb12e3b12d?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true) ## Alert Rules Think of alert rules as your notification command center. Each rule defines four key elements: * **Event**: What triggers the alert (like a monitor failing or a certificate nearing expiration) * **Scope**: Where the rule applies (organization-wide or just in specific projects) * **Rate limit**: How often the notification can be sent (preventing notification fatigue) * **Integration**: Where to send the alert (email, Slack, Discord, etc.) Additional settings can be configured depending on the event type and integration you choose. Alert rules can also be created with the [create an alert rule](/api-reference/platform/alert-rules/create-an-alert-rule) endpoint. ![Event, scope, rate limit and integration of an alert rule](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/alerting/alert-rule-create.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=28cf0d44ab72fd75b6c8ec9cc7e6aedd) ## Events Phare can alert you of various events, each with its own configuration options and use cases. You choose which events matter most to your organization and can set up multiple alert rules for a single event type. ### Monitor Events | Event | API format | Description | | :- | :- | :- | | Monitor created | `uptime.monitor.created` | Sent when a new monitor is created, great for logging or auditing purposes. | | Monitor deleted | `uptime.monitor.deleted` | Sent when a monitor is deleted, great for logging or auditing purposes. | ### Certificate Events | Event | API format | Description | | :- | :- | :- | | Monitor certificate discovered | `uptime.monitor_certificate.discovered` | Sent when a new SSL certificate is discovered on a monitor, useful for tracking changes and certificate renewal confirmation. | | Monitor certificate expiring | `uptime.monitor_certificate.expiring` | Sent when a monitor's SSL certificate is nearing expiration, based on a configurable threshold. | ### Incident Events | Event | API format | Description | | :- | :- | :- | | Incident created | `uptime.incident.created` | Sent when a new incident is created, this is the main alert for incident management. | | Incident propagated | `uptime.incident.propagated` | Sent when an incident propagates to an additional monitor. Requires smart incident merging to be enabled. | | Incident partially recovered | `uptime.incident.partially_recovered` | Sent when a monitor recovers but the incident is still ongoing due to other affected monitors. Requires smart incident merging to be enabled. | | Incident recovered | `uptime.incident.recovered` | Sent when an incident has fully recovered, indicating that all affected monitors are back to normal. | | Incident comment created | `uptime.incident_comment.created` | Sent when a new comment is added to an incident, useful for keeping team members informed of updates and discussions. | | Incident update published | `uptime.incident_update.published` | Sent when a new public incident update is published on a status page, useful for notifying stakeholders and users about the incident status. | ### Maintenance Window Events | Event | API format | Description | | :- | :- | :- | | Maintenance window in progress | `uptime.maintenance_window.in_progress` | Sent when a maintenance window starts, notifying teams that planned downtime has begun. | | Maintenance window completed | `uptime.maintenance_window.completed` | Sent when a maintenance window is finished, confirming normal operations have resumed. | | Maintenance window cancelled | `uptime.maintenance_window.cancelled` | Sent when a scheduled or in-progress maintenance window is cancelled. | ## Scope Keep your alerts relevant by setting the right scope: * **Organization**: Catch all matching events across your entire organization * **Project**: Focus only on events within specific projects This targeted approach ensures nobody gets alerts they don't need to act on. ## Rate limiting Too many notifications can lead to alert fatigue. That's why Phare lets you set limits on how frequently a notification can be sent. Even if an event triggers multiple times, you'll only be notified based on your preferred cadence, like at most once every 10 minutes. ## Notification channels Connect any [integration](/integrations/overview) to your alert rules to receive notifications through your preferred channels. Create as many alert rules as you need, customizing each one to get the right balance of information without overwhelming recipients. ![Alert rules data-table with their integration, scope and rate limit](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/alerting/alert-rules-list.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=30cb21e4332175c63b221e2e24e58e7a) ## Duplicating alert rules To send the same alerts to another channel, duplicate an alert rule from its actions menu in the alert rules list. The new rule starts with the same event, scope, filters and rate limit: choose another integration and create it. [Duplicate an alert rule](https://iframe.mediadelivery.net/embed/238508/0bb0e17c-909b-4b22-9889-0216cab8ccbf?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true) # Certificate management Source: https://docs.phare.io/uptime/certificates Discover how Phare helps you discover, manage, and monitor SSL/TLS certificates. SSL/TLS certificates are essential for securing endpoints. Phare makes monitoring and management straightforward by automatically detecting and tracking certificates across websites, APIs, and services. ## How certificate discovery works Phare integrates certificate discovery directly into the monitoring system for any HTTPS endpoint or TCP endpoint with TLS enabled. * Certificates are automatically detected when Phare monitors your endpoints * Multiple certificates per monitor are properly tracked and managed * Certificates are linked to all relevant monitors * New certificates are identified and added to your inventory as they appear ![Certificates data-table with their expiration and status](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/certificates/certificates-list.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=b8bb4772e947aa41f57158aeea9bccd5) ## Certificate monitoring Keep track of your SSL/TLS certificates with these helpful features: * **Notifications** when new certificates are discovered on your monitors, with an alert rule on the **Monitor certificate discovered** event * **Customizable expiration alerts** that can be set anywhere from 1 to 60 days before expiry * **Complete certificate inventory** showing both active and historical certificates * **Detailed certificate information** including issuer, validity period, and domain coverage Each certificate has a status: * **In use**: The certificate was seen by a monitor in the last 2 hours * **Expiring**: The certificate is in use and expires in less than 30 days * **Expired**: The certificate is in use and has expired * **Retired**: No monitor has seen the certificate in the last 2 hours, for example after a renewal ![Issuer, subject and validity period of a certificate](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/certificates/certificate-details.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=c9deb71b9642164108d5a20d2cfe61cd) ## Preventing certificate expiration issues With Phare's certificate monitoring, you can avoid the security warnings and outages that occur when certificates expire unexpectedly. Set a preferred notification schedule to get reminders when it's time to renew, or when certbot fails to renew certificates. Each alert rule on the **Monitor certificate expiring** event sends one reminder, the chosen number of days before the expiration. Create several alert rules, for example 30 and 7 days before, to get several reminders. ![Alert rule sent 14 days before a certificate expires](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/certificates/certificate-expiring-alert-rule.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=81a03454b92794fecf038c640fa7fc61) # Incident Management Source: https://docs.phare.io/uptime/incidents Learn how to manage the lifecycle of an incident with Phare Uptime incident management. When things go wrong, having a clear process makes all the difference. Phare's [incident management](https://phare.io/products/uptime/incident-management) system takes care of the entire incident lifecycle automatically, from the moment a problem is detected to when everything's back to normal. ## Programmatic incidents When a monitor detects trouble (respecting your confirmation settings and any keyword/SSL checks), Phare springs into action by creating an incident. Each incident is automatically linked to the affected monitor and includes detailed information about what went wrong. Right away, alert recipients are notified through your configured alert rules, no manual intervention required. Programmatic incidents track the entire lifecycle from detection through resolution, giving you a complete picture of what happened during the outage. ![Details of the failed request of an incident](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/incidents/incident-details.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=b89e35d6e4c8b988b9e6fae78b3ec960) ## Manual incidents Sometimes you need to create an incident even when your monitors haven't detected a problem. Issues from services you're not actively monitoring, or that can't be monitored by an uptime agent. [Create an incident](https://iframe.mediadelivery.net/embed/238508/a7158887-bf82-445f-8a3e-570b44a58faf?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true) Phare makes it easy to create incidents manually: 1. Select the affected monitor(s) 2. Set the impact level 3. Add a descriptive title 4. Include details about the situation ![Impact and affected monitors of a manual incident](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/incidents/manual-incident-create.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=4bbd7d5e26f8856b9b51cefdacb26ec8) Manual incidents follow the same lifecycle as programmatic ones, but you'll need to resolve them manually when the issue is fixed. This gives you full control over the incident's duration and communication timeline. ## Incident recovery When your service recovers (again, respecting your recovery confirmation settings), Phare automatically resolves the incident and notifies recipients through your alert rules. ## Impact Not all incidents are created equal. That's why Phare lets you classify incidents by their impact level: * **Unknown**: Still investigating, not sure how bad it is * **Maintenance**: The service is unavailable because of planned work * **Degraded performance**: Things are slower / working less well than usual * **Partial outage**: Some users are affected or certain features are down * **Major outage**: Everything is on fire, users can't access the service or are severely impacted ![Edit the impact of an incident](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/incidents/incident-impact.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=5336479b997139dc983f91a2fa3495ff) Impact levels help prioritize responses internally and keep users informed through status pages. If left as "unknown," status pages will simply show the monitor as "down" without additional details. An incident can also be excluded from downtime calculations, for example when the downtime is already part of your SLA. Excluded incidents are not counted in the downtime shown in your dashboard and on status pages. ## Tags Incidents can be organized with [tags](/uptime/monitors#tags), such as `environment:production` or `priority-1`, shared across your whole organization. Use the **Tags** filter on the incidents data-table to quickly find related incidents, or the `tag` parameter of the [list incidents](/api-reference/uptime/incidents/list-incidents) API endpoint. ## Event timeline ![Incident event timeline](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/incidents/incident-timeline.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=926482bbe9e5033b9936d2164f17d23d) The event timeline gives you the full picture of what happened during an incident. You can see every region's status, which alert rules fired, and follow the incident's progression from start to finish. This chronological view helps with post-incident analysis and improves response procedures over time. ## Incident comments Team members can add private comments to share insights or document solutions, helping everyone resolve issues faster. These internal notes are perfect for: * Documenting troubleshooting steps * Sharing relevant links to logs or dashboards * Coordinating response efforts between team members * Recording root cause analysis findings The rich text editor supports Markdown, making it easy to include formatted text, code snippets, or links to relevant resources. Comments are only visible to organization members and never appear on public status pages. Each comment is timestamped and attributed to its author, creating a clear record of who did what during incident response. ![Add a comment to an incident](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/incidents/incident-comment.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=a64da80dc0a83192beb40f6f2e939683) ## Incident updates ![Publish an incident update](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/incidents/incident-publish-update.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=d1d840b9ca0d6bdd90d20d7d0163dc91) While comments help private collaboration, incident updates are designed for external communication. These updates allow you to keep users informed about: * What's happening with the incident * What you're doing to fix it * When they can expect resolution * Workarounds they can use in the meantime Each update allows you to communicate progress as you mitigate the issue and is automatically published to connected status pages, helping maintain transparency with users during outages. Each update has a state (investigating, identified, monitoring or resolved) and a publication time. Updates can also be published with the [create an incident update](/api-reference/uptime/incidents/updates/create-an-incident-update) endpoint. Consistent, clear communication during incidents builds trust. Users appreciate knowing the situation is under control even when things aren't working perfectly. ## Smart incident merging Smart incident merging reduces noise by grouping multiple, similar failures into a single incident that evolves over time. Instead of opening a new incident for every affected monitor, Phare can merge them together, keep one timeline, and notify recipients more intelligently. ### Configuration Smart incident merging can be configured per-project, allowing you to tailor the behavior to different services or groups. You can also set a preferred time window for merging, balancing responsiveness with noise reduction. ![Smart Incident merging project settings](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/incidents/incident-merging-configuration.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=cb12b408501cc91ccf8de482e51f8d72) > [!NOTE] > > Start with a moderate window of 10 to 30 minutes. If you often experience bursty or cascading failures, a longer window will reduce duplicate incidents further. ### How it works Only incidents belonging to the same project can be merged together. When a new incident is created, even before confirmation, Phare checks for any existing open incidents in the project that share the same reported issue. If it finds one within the configured time window, it merges the new incident into the existing one. This approach, even though simple, provides fast and reliable results for most incident scenarios. ![Timeline of an incident merged across two monitors](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/incidents/incident-merged-timeline.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=9a5ab14705a406bcdeccf7432c456f55) ### Dedicated alert rule events Two alert rule events are available to help you react precisely to incident propagation and partial recoveries: * [Incident Propagated](/uptime/alerting#>-incident-propagated) * [Incident Partially Recovered](/uptime/alerting#>-incident-partially-recovered) Paired with notification threads on the [Email](/integrations/email), [Discord](/integrations/discord), or [Slack](/integrations/slack) integrations, notifications stay focused: one creation, threaded follow‑ups for expansions and partial recoveries, and a final recovery when everything is back to normal. ## Incident AI Incident AI leverages the [Mistral AI](https://mistral.ai/) platform to analyze incident data and generate useful summaries and post-mortem reports. By understanding the context and details of each incident, Incident AI helps resolve issues faster and improve future response strategies. This feature is powered by [Mistral Small 4](https://mistral.ai/news/mistral-small-4), a lightweight model that provide fast reasoning with lower costs and energy use. ### Configuration Incident AI can be activated per-project, allowing compliance with different data policies across your organization. ![Incident AI project settings](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/incidents/incident-ai-configuration.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=13eceb770bc609dc4a80f8f81c831039) ### How it works When activated, Phare will automatically generate an AI incident summary when an automated incident is created, and a post-mortem report when it is resolved. Incident AI is not active on manually created incidents. Each AI generation consumes one credit from your plan's monthly allowance. When the [quota](/billing-quotas) is exhausted, no further AI generation is performed until the next billing cycle. Additional quota can be configured if your organization is subscribed to the Scale plan. ![AI post-mortem report of an incident](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/incidents/incident-ai-generations.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=d14da045b67d957e93eb28db94a9f8b7) > [!NOTE] > > Incident AI is in its early stages and may not always produce perfect results. Carefully review AI-generated content before sharing it with users. ### Privacy To protect your data, Incident AI only processes strictly necessary information related to the incident, such as: * Incident data * Impacted monitors * Failed request responses * Incident event timeline * Incident comments * Incident updates Sensitive data like monitor name, API keys, HTTP header values, or user emails are redacted with anonymization tokens in the payload sent to Mistral AI. Phare uses Mistral's paid plan which [does not train artificial intelligence models on your data](https://help.mistral.ai/en/articles/347617-do-you-use-my-user-data-to-train-your-artificial-intelligence-models#scale-plan-pay-per-use-subscription). ### Improving Incident AI You can rate each AI generation by using the thumbs up/down buttons next to the AI content to provide your feedback. Phare will use this feedback in the future to fine-tune a custom model specifically for incident management. Only rated AI generations will be used for this purpose. # Maintenance Windows Source: https://docs.phare.io/uptime/maintenance-windows Plan scheduled downtime, control monitoring behavior, and keep users informed during maintenance. Whether you're upgrading databases, shipping breaking API changes, or rebooting a server, it's best to let your users know in advance. Phare's [maintenance windows](https://phare.io/products/uptime/maintenance-windows) let you plan ahead, choose exactly how monitoring should behave, and keep your status page subscribers in the loop throughout the process. [Create a maintenance window](https://iframe.mediadelivery.net/embed/238508/f507dec8-3113-43bc-a3e5-ca4ce917dfe4?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true) ## Scheduling a maintenance window Every maintenance window requires a start and end date. Once created, it's immediately shown on linked status pages and communicated to your users. You can modify the start date right up until the window begins. Once it's in progress, you can extend its end date, cancel it or mark it as completed early. If you don't make any manual changes, Phare will automatically mark it as completed when the end date arrives. ![Title, description, start and end time of a maintenance window](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/maintenance-windows/maintenance-window-schedule.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=0346960b20b73d2b530b21a0807a379a) > [!TIP] > > Dates and times automatically use your account's local timezone, so there's no need to do mental UTC math when scheduling. ## Monitoring modes Depending on your SLA and the type of maintenance being performed, you might want monitoring completely turned off, or just watch requests flow in without blowing up your notification channels. Phare gives you three modes to handle checks and alerts: ![Affected monitors and monitoring mode of a maintenance window](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/maintenance-windows/maintenance-window-monitoring-mode.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=07611c944200efa44f03445b4be762bf) ### Pause monitoring When a maintenance window starts in **Pause** monitoring mode, Phare stops all attached monitors, effectively pausing checks for the duration of the window. * **Zero false alarms**: No checks are performed, so no incidents are triggered and your uptime and SLA percentages remain untouched. * **Smart resume**: If a monitor was *already* paused before the maintenance window started (for instance, a staging server you took down earlier), Phare remembers that state. When the maintenance window finishes, only monitors that were active beforehand are resumed. Overlapping pause windows are also handled automatically. > [!TIP] > > Use Pause monitoring for heavy-duty infrastructure work, database migrations, or server reboots where services will be completely unavailable. ### Mute alerts In **Mute** mode, Phare keeps checking your endpoints as usual in the background, but silences all alert notifications. * **Live telemetry**: Response times, status codes, and latency charts keep updating in real time. * **Quiet incidents**: If an endpoint fails or throws errors during maintenance, an incident is tracked internally, but its alerts are not sent (no Slack pings, Discord alerts, SMS, or emails) when all the monitors of the incident are in the maintenance window. Other alerts, like certificate expiration, are still sent. * **Instant verification**: You can see immediately when services come back up and start returning 200 OK (or whatever HTTP code you configured on your monitor). > [!TIP] > > Mute mode is perfect for rolling deployments, configuration tweaks, or verifying that a hotfix worked in production before wrapping up. ### Normal In **Normal** mode, checks run and alerts fire exactly as usual. Use this mode for non-disruptive maintenance, like warming up background worker queues or upgrading secondary systems, where you still want full alerting if something unexpected goes wrong, but want the maintenance window officially announced on your status pages. ## Lifecycle & Status Maintenance windows manage themselves so you don't have to keep an eye on the clock: * **Scheduled**: Planned for the future. Upcoming notices appear on connected status pages. * **In progress**: The window has started. Monitors are paused or muted depending on the monitoring mode, status pages show an active maintenance banner, and your team gets notified if configured. * **Completed**: Everything's back to normal. Paused monitors resume automatically and status pages return to operational. * **Cancelled**: Called off before or during maintenance. Any paused monitors are immediately restored. Phare automatically transitions windows to **In progress** when the start time arrives, and marks them **Completed** when the end time passes. ![Maintenance windows data-table with their state](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/maintenance-windows/maintenance-windows-list.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=0d254f12ffceae8d0ed12a828651d378) ### Early completion & Cancellation Finished early? While the window is in progress, you can hit **Complete** from the dashboard to wrap up the window, resume your monitors, and update your status pages immediately. If the maintenance isn't needed anymore, **Cancel** will stop the process and let your users know. The same actions are available with the [complete a maintenance window](/api-reference/uptime/maintenance-windows/complete-a-maintenance-window) and [cancel a maintenance window](/api-reference/uptime/maintenance-windows/cancel-a-maintenance-window) endpoints. ![Maintenance window in progress with the Complete and Cancel buttons](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/maintenance-windows/maintenance-window-details.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=081fb789b8f3013dae973dab97733d3b) ## Status page communication When you link a maintenance window to a status page, Phare handles external communication automatically: * **Upcoming announcements**: Visitors can see scheduled maintenance in advance, giving them time to prepare. * **Active maintenance status**: While maintenance is underway, the status page displays a prominent banner and sets the overall component status to **Maintenance** (unless a real outage takes precedence). * **Timeline markers**: Maintenance periods are highlighted on component uptime bars so visitors know downtime was planned. * **Subscriber feeds**: Maintenance announcements are automatically broadcast across RSS, ATOM, and Slack feeds. ![Status page with a maintenance in progress and two scheduled maintenance windows](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/maintenance-windows/status-page-maintenance.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=bd777d3fa4e4d2da21e514b3dbcd9aa6) ## Tags Maintenance windows can be organized with [tags](/uptime/monitors#tags), such as `environment:production` or `server:main`, shared across your whole organization. Use the **Tags** filter on the maintenance windows data-table, or the `tag` parameter of the [list maintenance windows](/api-reference/uptime/maintenance-windows/list-maintenance-windows) API endpoint, to find related maintenance windows. ## Alert rules You can hook maintenance windows into Phare's [alert rules](/uptime/alerting) to keep internal teams aligned when work begins and ends: | Event | API format | Description | | :- | :- | :- | | Maintenance window in progress | `uptime.maintenance_window.in_progress` | Sent when planned maintenance starts. | | Maintenance window completed | `uptime.maintenance_window.completed` | Sent when maintenance finishes and normal checks resume. | | Maintenance window cancelled | `uptime.maintenance_window.cancelled` | Sent when a scheduled or active window is cancelled. | # Monitors Source: https://docs.phare.io/uptime/monitors Monitor the availability of your websites, APIs and servers with HTTP, TCP and ICMP ping monitoring. Monitors are the backbone of [Phare Uptime](https://phare.io/products/uptime/website-monitoring). They are tireless digital assistants checking if your website or server is alive and kicking. Set them up once, and they'll dutifully perform HTTP(S), TCP, and ICMP ping checks according to your schedule. [Create a new monitor](https://iframe.mediadelivery.net/embed/238508/af095257-c47c-4dec-8a72-92e95cb349aa?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true) ## HTTP(s) When monitoring websites, Phare sends HTTP(s) requests and checks both the status code and (optionally) looks for specific text in the response. If HTTPS is used, Phare automatically keeps an eye on your SSL certificates too, making sure they're valid and well-configured. ![HTTP(s) monitor request settings](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/monitors/http-request.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=3f82a2c6e31a40495b1160f3d4a0b30e) You can find more details about the [HTTP(s) monitoring settings](#configuration-options-for-https) below. ### Method When creating HTTP monitors, you can choose which method to use for your requests. Phare currently supports: * **HEAD**: Ideal for quick availability checks. Retrieves only headers, saving bandwidth and processing time, perfect for frequent checks on large websites. * **GET**: The standard choice for most monitoring. Gets the full page content, allowing you to verify text content and properly test API content or websites that do not support HEAD requests. * **POST**, **PUT**, **PATCH**: For testing form submissions or API endpoints that require data input. You can customize the request body to simulate real user interactions or API calls. * **OPTIONS**: For checking API configuration and CORS policies without triggering data changes. Great for testing API availability without actually using it. Switching to the POST, PUT or PATCH methods adds a `Content-Type: text/plain` header to the [headers](#headers) of the request, unless there is one already. Change its value to match your request body, such as `application/json`. ![POST request with a JSON body](https://mintcdn.com/phare/bix3XWvYLxj7FRq8/images/uptime/monitors/http-request-body.avif?fit=max\&auto=format\&n=bix3XWvYLxj7FRq8\&q=85\&s=1034691db366ad704fb52b0c2d5c911f) ### Skip SSL verification By default, Phare performs strict SSL certificate validation to ensure secure connections on all `https://` endpoints. However, if you're monitoring a staging environment or a server with a self-signed certificate, you can choose to skip SSL verification. When this option is enabled, Phare will ignore SSL issues such as certificate expiration, intermediate certificate chain problems, or OCSP revocation status. ### Follow redirects Phare can automatically follow HTTP redirects (3xx status codes) when this option is enabled. This is particularly useful to test scenarios where redirects are expected, or when monitoring URLs that may change over time. If disabled, Phare will report the initial redirect response, allowing you to monitor the redirection behavior itself. When enabled, the Phare monitoring agent will follow up to 5 redirects before failing the check. Each redirect counts toward the chosen timeout limit, so ensure the timeout is sufficient to accommodate all potential redirects. ### User agent Every HTTP request from Phare carries the following user-agent signature: > `Mozilla/5.0 (compatible; Phare/1.0; +https://phare.io/products/uptime)` Turn on the user agent secret to add a `secret-value` to the user agent header for firewall filtering, it will look like this: > `Mozilla/5.0 (compatible; Phare/1.0; +https://phare.io/products/uptime; Secret=secret-value)` The secret value is encrypted and never shown again once saved. ### Headers Need to get past authentication or test an API with specific requirements? Phare lets you add custom headers to your HTTP monitors. This feature opens up possibilities for: * Testing APIs with authorization tokens * Bypassing basic authentication on staging environments * Setting content negotiation preferences * Adding custom tracking identifiers ![Follow redirects, user agent secret and headers settings](https://mintcdn.com/phare/bix3XWvYLxj7FRq8/images/uptime/monitors/http-advanced-options.avif?fit=max\&auto=format\&n=bix3XWvYLxj7FRq8\&q=85\&s=98d80d4ac2a3f1199fedc5406c00ea39) > [!NOTE] > > To prevent abuse, it is not possible to set a custom `User-Agent` header, with the exception of adding a secret value for firewall filtering. ### Encrypted headers Click the lock in the value of a header to encrypt it, such as an `Authorization` token or an API key. An encrypted header value is never shown again once saved, not in the dashboard, API, MCP, or the alert payloads. ![Encrypted Authorization header value being replaced](https://mintcdn.com/phare/bix3XWvYLxj7FRq8/images/uptime/monitors/http-encrypted-header.avif?fit=max\&auto=format\&n=bix3XWvYLxj7FRq8\&q=85\&s=ad3bbd0781b0d0f444653ef1ff1cd2fa) Duplicating a monitor leaves out its user agent secret and encrypted header values, type them again in the new monitor. ### Success assertions ![Phare Uptime success assertions](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/monitors/success-assertions.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=966a9d8cc44145100553efce92333a9a) Phare allows you to define specific success assertions to ensure your service is not only up but also functioning correctly. You can choose to validate: * **Status code**: Specify exact status codes (`200`) or use wildcards (`2xx`), you can also combine multiple codes (`200,3xx`). * **Response header**: Check for the presence of a specific header with a value of your choice. * **Response body**: Look for specific text or patterns in the response body to confirm the service is delivering the expected content. Not available with `HEAD` and `OPTIONS` methods. > [!NOTE] > > Response body and response header assertions are performed case-insensitively. ## TCP For services beyond websites, TCP monitoring establishes a direct connection to your server port to make sure everything responds correctly. Phare currently supports plain and TLS connections. ### Connection Phare supports plain and TLS connections for TCP monitoring. You can choose the appropriate option based on your service requirements. With a TLS connection, you can skip TLS verification to accept any certificate, even if misconfigured, expired or self-signed. ![TCP monitor request settings](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/monitors/tcp-request.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=0085910aa0d5950576118f8c3a1af8e0) ## ICMP For servers, network appliances, and infrastructure, ICMP ping monitoring sends standard Internet Control Message Protocol (ICMP) echo requests (ping) to verify host reachability and measure network latency. Unlike HTTP(S) or TCP monitors, ICMP monitoring does not require any open ports or running web servers. This makes it ideal for monitoring routers, switches, firewalls, and bare-metal hosts where you only need to verify host availability and network responsiveness. ### Host When setting up an ICMP monitor, specify the target hostname or IP address to ping. ## Interval You decide how often Phare checks your endpoints. The default is every minute, but you can adjust the frequency to suit your needs, anywhere between 30 seconds and 1 hour. ## Timeout A check fails when your service does not respond within the request timeout. The default is 20 seconds, but you can set it anywhere between 1 and 30 seconds. For HTTP monitors, the timeout includes any redirections. ## Confirmations & recovery Nobody likes false alarms. That's why Phare allows extra checks before creating an incident. A service is only marked as down (or recovered) after a configurable number of consecutive failures (or successes). The default is three confirmations, but you can set this anywhere from one (immediate alerts) to five checks. When a monitor uses several regions, the region threshold sets how many regions must fail at the same time before an incident is confirmed. It can be set from one up to the number of selected regions. ![Incident confirmations, recovery confirmations and region threshold settings](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/monitors/confirmations.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=b8e67154a0b28a19a228bc91b006b5a4) ## Regions With 12 monitoring regions worldwide, Phare lets you check your services from different parts of the globe. **It is strongly recommended to use at least two regions**, this helps avoid false positives and keeps monitoring resilient even if one region experiences issues. ![Monitoring interval and regions settings](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/monitors/scheduling.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=77a5bf26b83ddf18648a0b490af4228c) ### Region list Region API codes follow the format `--`. #### Asia | Country | City | API code | | :- | :- | :- | | 🇯🇵 Japan | Tokyo | `as-jpn-hnd` | | 🇸🇬 Singapore | Singapore | `as-sgp-sin` | | 🇹🇭 Thailand | Bangkok | `as-tha-bkk` | #### Europe | Country | City | API code | | :- | :- | :- | | 🇩🇪 Germany | Frankfurt | `eu-deu-fra` | | 🇫🇷 France | Paris | `eu-fra-cdg` | | 🇬🇧 United Kingdom | London | `eu-gbr-lhr` | | 🇸🇪 Sweden | Stockholm | `eu-swe-arn` | #### North America | Country | City | API code | | :- | :- | :- | | 🇲🇽 Mexico | Mexico City | `na-mex-mex` | | 🇺🇸 US East | Ashburn | `na-usa-iad` | | 🇺🇸 US West | Seattle | `na-usa-sea` | #### Oceania | Country | City | API code | | :- | :- | :- | | 🇦🇺 Australia | Sydney | `oc-aus-syd` | #### South America | Country | City | API code | | :- | :- | :- | | 🇧🇷 Brazil | Sao Paulo | `sa-bra-gru` | ## Tags Monitors can be organized with tags, such as `environment:production` or `server:main`, shared across your whole organization. Use the **Tags** filter on the monitors data-table, or the `tag` parameter of the [list monitors](/api-reference/uptime/monitors/list-monitors) API endpoint, to find related monitors. ![Tags filter on the monitors data-table](https://mintcdn.com/phare/0gTUtPvKPs13-CY9/images/uptime/monitors/monitor-tags-filter.avif?fit=max\&auto=format\&n=0gTUtPvKPs13-CY9\&q=85\&s=9de92119e3041133f0571b7ff33e836a) ## Alert rules Phare's alert rules system allows you to decide which events trigger notifications. There are a few alert events that can be raised by monitors. The full list is in the [alerting documentation](/uptime/alerting). ## Suggestions ![Phare Uptime monitoring suggestions](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/monitors/uptime-monitor-suggestions.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=415faf127bf741448cd0556b20ad63f5) As you set up your monitors, Phare's suggestion system analyzes your configuration and offers improvements to boost reliability and reduce false positives: * Adding more monitoring regions for better global coverage * Increasing incident and recovery confirmations to prevent false positives * Alerting you to redirections that might impact performance reporting ## Statistics ![Phare Uptime monitoring statistics](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/monitors/uptime-monitoring-statistics.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=ebfcf6d740a52ada5e07a601ee1e2be3) Each monitor will show detailed statistics to help you understand your service performance at a glance: * **Performance charts** appear shortly after creating a monitor, displaying quantile-based response time trends (**P75**, **P90**, and **P99**) * View the performance data by region to spot geographical performance variations * Zoom in on specific timeframes by clicking and dragging to select portions of the chart * Track key metrics including response time quantiles, total downtime, and SLA percentages * Historical data from 24 hours up to 90 days lets you spot both immediate issues and long-term trends Be aware that charts are rendered leveraging [downsampling techniques](https://phare.io/blog/downsampling-time-series-data/) to present meaningful visualizations without overwhelming your browser. This is why you won't see every single data point on the chart. ## Firewall & Bot protection Because Phare monitoring agents run on global edge networks, IP addresses are dynamic. Rather than maintaining brittle IP allowlists, Phare supports modern cryptographic bot authentication and header-based filtering. ### Web Bot Auth (Verified Bot) Phare monitoring agents implement the IETF standard **Web Bot Auth** ([RFC 9421](https://datatracker.ietf.org/doc/html/rfc9421) HTTP Message Signatures). Every HTTP check executed by Phare includes cryptographic Ed25519 signatures in the request headers (`Signature`, `Signature-Input`, and `Signature-Agent`). Phare's signature directory is available at: ``` https://phare.io/.well-known/http-message-signatures-directory ``` Phare is also listed as a [verified bot on Cloudflare](https://radar.cloudflare.com/bots/directory/phare-uptime). If your website is behind Cloudflare, Phare's monitoring requests are recognized as verified bot traffic, and Cloudflare's default bot settings exclude verified bots. If you changed these settings, make sure **Verified bots** is set to **Allow** in Super Bot Fight Mode, and that your WAF custom rules don't block verified bots. ### User-Agent & Secret token If your web server or firewall does not support web-auth-bot yet, the next best thing is to filter Phare's traffic with an [User-Agent secret](/uptime/monitors#user-agent). ## Private monitoring agent Need specialized monitoring for complex requirements, large-scale operations, or access through private VPNs? A private monitoring agent can be set up in a preferred region. [Contact Phare](https://phare.io/contact) to discuss specific needs. ## Good practices If you're unsure about the best settings for your monitoring needs, you can find the [Best practices to configure an uptime monitoring service](https://phare.io/blog/best-practices-to-configure-an-uptime-monitoring-service/) on the Phare blog. ## Limits Phare's monitoring infrastructure is built for scale and resilience, but there is one important constraint: * **No IP allowlisting**: Monitoring traffic comes from [Bunny.net's shared IP ranges](https://api.bunny.net/mc/nodes/plain), so fixed IPs can't be provided. If this is a blocker, a private monitoring agent can provide dedicated IPs, or [reach out](https://phare.io/contact) to discuss alternatives. # Overview of Phare Uptime Source: https://docs.phare.io/uptime/overview Monitor websites, APIs and servers with HTTP, TCP and ICMP ping monitoring, manage incidents and create status pages Phare Uptime is your digital babysitter that keeps an eye on your websites, APIs and servers 24/7, alerting you before users start complaining. ## Uptime Monitoring Think of uptime monitoring as your website's health checkup. Phare regularly visits your website or API, checks its vital signs, and lets you know if something looks off. Alongside HTTP and TCP checks, [ICMP ping monitoring](/uptime/monitors#icmp) keeps an eye on your servers' availability and latency. [Learn more about uptime monitoring](/uptime/monitors). [Phare uptime monitoring demo](https://iframe.mediadelivery.net/embed/238508/9f92680b-95ac-4e87-80b4-bb7eb65f8fec?autoplay=false\&loop=false\&muted=false\&preload=true\&responsive=true) ## Incident Management When things go sideways, you need a system to track what happened, who is fixing it, and when it's resolved. Phare's incident management gives you the tools to handle the entire lifecycle, from "oh no!" to "all good!" [Learn more about incident management](/uptime/incidents). ![Incident with the failed request, the AI post-mortem and the event timeline](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/overview/incident-management-page.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=26764471fb17ccfb614338d97e58f158) ## Maintenance Windows Schedule maintenance windows in advance, pause or mute monitoring checks, and keep your customers informed. [Learn more about maintenance windows](/uptime/maintenance-windows). ![Maintenance window in progress with its monitors and status pages](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/overview/maintenance-windows-page.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=2f86062bac38922cbcb8b3950c844593) ## Status pages Status pages let your users know what's going on when your service isn't performing as expected. A little transparency goes a long way in building trust. [Learn more about status pages](/uptime/status-pages). ![Status page with the history of each component](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/overview/status-pages-page.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=9d878c89bbe0a322d98992ea331e719d) ## Alerting When problems arise, you need to know immediately. Phare's alerting system lets you customize exactly who gets notified, when, and how on the channel of your choice. [Learn more about alerting](/uptime/alerting). ![Alert rule creation form](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/overview/alert-rules-page.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=52be4540326e215cc5e6693042592027) # Status pages Source: https://docs.phare.io/uptime/status-pages Keep your customers in the loop with a sleek status page. Build trust with transparent communication on incidents and maintenance periods. Status pages are your public-facing communication hub during both good times and bad. They show your users the real-time status of your services, any ongoing incidents, and planned maintenance. [Status pages by Phare](https://phare.io/products/uptime/status-pages) are lightning-fast and [among the most eco-friendly](https://www.websitecarbon.com/website/status-phare-io/) you can find. [Create a status page](https://iframe.mediadelivery.net/embed/238508/958b161f-21ab-43a8-af7f-7062e30de0d9?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true) ## Creating a status page Create as many status pages as your projects need, there's no limit. Pick which monitors to display, customize the look to match your brand, and give Phare a few seconds to generate an SSL certificate, your status page will be ready in no time. Status pages can also be created with the [create a status page](/api-reference/uptime/status-pages/create-a-status-page) endpoint. ![Status page creation](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/status-pages-creation.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=8fe58eefaf12bf40b8ae01a869341751) ## Phare domain Every status page gets its own `*.status.phare.io` domain name, complete with SSL protection out of the box. ## Custom domain Want your status page on your own domain? Simply create a CNAME record in your DNS settings pointing to `cname.status.phare.io`: | Type | Name | Target | | :- | :- | :- | | CNAME | status.example.com | cname.status.phare.io | Make sure your DNS is configured correctly so Phare can generate a valid SSL certificate. This usually takes a few minutes. Once verified, your Phare domain will automatically redirect to your custom domain. ![Phare subdomain and custom domain settings](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/status-page-domain.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=fad6d9b65beca0c1f786e46c173e2f6c) ### Custom domain with Cloudflare DNS Using Cloudflare? Make sure to create your CNAME with proxy status in `DNS-only` mode (keep the cloud icon gray, not orange) as shown below: ![Custom domain on Cloudflare](https://mintcdn.com/phare/Jh1uiqHFo-IwwO2b/images/uptime/status-pages/custom-domain-cloudflare.webp?fit=max\&auto=format\&n=Jh1uiqHFo-IwwO2b\&q=85\&s=bb103c005cf0be364c68d5c407e37faa) ### Custom domain with Bunny.net Hello fellow Bunny enthusiast! Since Phare also uses Bunny.net as a DNS and certificate provider, there's an extra security step, called **multi-domain**, required to make your domain work with Phare. Don't worry, it's quick and straightforward: **1. Create a TXT record** Add this TXT record to your root domain (`@`) in your DNS settings to help Bunny.net verify your request: | Type | Name | Target | | :- | :- | :- | | TXT | @ (or example.com) | Bunny Support - Phare | **2. Open a support ticket** Head over to your [Bunny.net support hub](https://dash.bunny.net/support/tickets) and create a new ticket. **3. Write a message** Select the **DNS** department and send something like this (with your actual domain): ```text theme={null} Hello Bunny.net team, I created a CNAME entry for my subdomain status.example.com that points to cname.status.phare.io. Phare.io is also using Bunny, and they need your authorization to add my subdomain on their PullZone and generate an SSL certificate for my subdomain. Could you please whitelist my domain for multi-use across the bunny platform? I've created a TXT record on my root domain called `Bunny Support - Phare` as proof of ownership. Thank you for being awesome! ``` **4. Wait for the ticket to be processed** Bunny's support team is usually quick, sit tight for a few minutes. **5. Verify your custom domain** Once resolved, go back to your [status page dashboard](https://app.phare.io/uptime/status-pages) and hit the `Verify again` button to activate your custom domain. ![Verify failed status page domain](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/verify-failed-status-page-domain.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=8a867682f3af6a5247975049073cb1df) #### Known Issues If you remove your domain name from **your own** Bunny DNS account, and later try to add it back, you will encounter the following error: > [!CAUTION] > > It appears that the domain, or a subdomain of it, is already registered in > another account. This is due to the way Bunny handles domain ownership verification. When you remove the domain from your account, it will still be registered on Phare's account to handle your status page, preventing you from re-adding it. **How to fix:** 1. [Disable your status page](https://app.phare.io/uptime/status-pages) in Phare 2. [Add your domain](https://dash.bunny.net/dns/zones) back to your Bunny account The multi‑domain setting that was previously enabled by Bunny's support agents will stay active, allowing you to recreate your status page right away. Having trouble? [Contact support](https://phare.io/contact). ## Availability history ![Status page availability history](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/status-page-timeline-days.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=51f0e5be5d9a0c618585bc6bdc9bc6cc) Each monitor on a status page displays an availability history with one bar per day, along with its overall availability percentage. The history window can be set to 30, 60, or 90 days in the status page settings. Days with incidents are highlighted by a marker colored according to the incident [impact level](/uptime/incidents#impact), so a short degraded performance episode is not mistaken for a full day of outage. Visitors can browse previous periods using the navigation arrows. ## Timezone Each status page has a timezone, `UTC` by default, that can be changed in the status page settings. The timezone is used to split the availability history into days and to display all dates on the status page, including incidents, maintenance windows, and the RSS, Atom and Slack [feeds](#subscription). Choosing the timezone of your main audience ensures an incident happening late in the evening is shown on the day your users experienced it. ![Status page timeframe and timezone settings](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/status-page-timeframe-timezone.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=688d3bd1a311d2228f56768b3fb2cc44) ## Monitor groups ![Status page component groups](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/status-page-groups.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=0c368e743f1039d44c3344eda24a85ac) To keep status pages organized and readable, you can group multiple monitors into collapsible **groups** (for example, grouping by service, region, or infrastructure layer). Each group displays an aggregated operational status, overall availability, and combined incident history across all nested monitors, with an option to display the group expanded or collapsed by default. ## Monitor display name You can assign a custom display name to any monitor to show a user-friendly label on your public status page without having to rename the underlying monitor in your dashboard. ![Monitor name and display name settings](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/monitor-display-name.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=655b0eb593610cda2c22bf803de73400) ## Tags Status pages can be organized with [tags](/uptime/monitors#tags), such as `environment:production` or `customer:acme`, shared across your whole organization. Use the **Tags** filter on the status pages data-table, or the `tag` parameter of the [list status pages](/api-reference/uptime/status-pages/list-status-pages) API endpoint, to find the status pages you need. ## Subscription Your users can stay informed about your service's status with automatic update subscriptions. Phare status pages come with built-in RSS and ATOM feeds, allowing for easy integration with various platforms. ![Status page subscription menu](https://mintcdn.com/phare/R-q9jFaU3EYRQo0C/images/uptime/status-pages/status-page-subscribe.avif?fit=max\&auto=format\&n=R-q9jFaU3EYRQo0C\&q=85\&s=bdf47fba21aea3f72fff34e9862310c9) ### RSS and ATOM feeds Every status page automatically includes feed endpoints that users can subscribe to: * **RSS feed**: Available at `https://status.example.com/history.rss` or `https://example.status.phare.io/history.rss` * **ATOM feed**: Available at `https://status.example.com/history.atom` or `https://example.status.phare.io/history.atom` ### Slack feed Phare provides a dedicated Slack-compatible RSS feed for easy integration with Slack workspaces: * **Slack RSS feed**: Available at `https://status.example.com/history.slack.rss` or `https://example.status.phare.io/history.slack.rss` To subscribe in Slack, use the command: ``` /feed subscribe https://status.phare.io/history.slack.rss ``` ### Subscribing to feeds Your users can subscribe to the standard RSS/ATOM feeds using: 1. **Feed readers**: Apps like Feedly, Inoreader, or NewsBlur 2. **Email notifications**: Services that convert feeds to email alerts 3. **Other integrations**: Many platforms like Microsoft teams or Discord can connect to standard RSS/ATOM feeds for notifications The number of subscribers is currently unlimited on any Phare plan at no extra cost. ## Access control > [!WARNING] > > Access control are only available with a Scale plan subscription By default, status pages are publicly accessible. You can restrict access using three complementary control mechanisms. Multiple access controls can be activated to fit your needs, they are evaluated in order: 1. If the visitor's IP is in the allowlist → access is granted 2. If the URL includes a valid token query parameter → access is granted 3. If a password is configured → the visitor is redirected to a login page ### IP allowlist ![Access control ips](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/access-control-ip.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=85917fb14a4bd4b6e59828834f0546c1) > [!TIP] > > IP restrictions are the most seamless option when everyone accesses the page from a shared network or VPN. Define individual IPv4 addresses or CIDR ranges that are granted access automatically, with no token or password required. Requests from listed addresses bypass all other checks. Common use cases: * Office or campus networks * VPN exit nodes * CI/CD infrastructure polling badges or feeds ### Access token ![Access control token](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/access-control-token.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=75c2a11b53470c440ff2d8f811ff48be) > [!TIP] > > Tokens are ideal for programmatic access like RSS/Atom feeds, or showing embedded badges on internal resources. Append a secret `token` query parameter to any status page URL to grant access. The token works on the main page, feeds, and badge endpoints: ``` https://example.status.phare.io?token= https://status.example.com/history.rss?token= https://status.example.com/embed-badges/static-status?token= ``` When a browser visits a URL with a valid token, a session cookie is set automatically, subsequent visits from that browser won't need the token for 1h. ### Access password ![Access control password](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/access-control-password.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=51bb10ae8a644f9fc0315c8b3388d3a4) > [!TIP] > > Passwords are the simplest option for human visitors who access the page through a regular browser. When a password is configured, visitors are prompted with a login screen before they can view the status page. This works well for internal pages shared with team members or customers. ![Status page login screen](https://mintcdn.com/phare/R-q9jFaU3EYRQo0C/images/uptime/status-pages/status-page-login.avif?fit=max\&auto=format\&n=R-q9jFaU3EYRQo0C\&q=85\&s=ac17053b24a89610a8a6a49418367041) ## Status badges Once your status page is live, you get access to status badges you can proudly display on your website or repository. They're a great way to show transparency and confidence in your service reliability. Access them through your status page's action menu. ![Status badges menu](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/status-badges-menu.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=6d16bdf47221deecbb53ebf2d4b47eb6) ### Embed badges These badges are designed for your website and can be customized to fit right in with your design. They adapt to light/dark themes or can be forced to either style. You can adjust: * `align`: For the live status badge positioning. Options: `start`, `center`, or `end`. * `background-light`: Background color in light mode. * `background-dark`: Background color in dark mode. * `text-light`: Text color in light mode. * `text-dark`: Text color in dark mode. Colors accept standard hex formats (RGB, RGBA, RRGGBB, or RRGGBBAA). Not feeling creative? There's already some stylish presets ready to go. ![Embed status badges](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/embed-status-badge.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=dd2c4058a27777e1efebb39502bd8afc) ### Shield badges These are the classic badges you see in GitHub repositories. Perfect for your README file, they come in all the popular shield styles. Based on the [Shields.io](https://shields.io) service, they're [fully customizable](https://shields.io/badges/endpoint-badge) to match your project's look. ![Shield status badges](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/uptime/status-pages/shield-status-badge.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=b4946723bb9abc92faca54948656dffc) # User management Source: https://docs.phare.io/user-management Learn how to manage members and roles in Phare, from read-only viewers to admins, invite team members, control project access, and set up single sign-on with your identity provider. Phare makes collaboration easy by letting you invite as many team members as you need to your organization. Keep things organized by managing access with roles and project scopes, so everyone gets exactly what they need, no more and no less. [Phare user management](https://iframe.mediadelivery.net/embed/238508/ae26b18b-6c96-42f0-8334-b61fe0eea0c5?autoplay=false\&loop=true\&muted=true\&preload=true\&responsive=true) ## Roles Roles are predefined sets of permissions. Phare has four of them, from read-only access to full control of the organization, and each role includes every permission of the previous one: * **Viewer**: Read-only access to every resource of their projects. Perfect for stakeholders, managers or support teams who follow the status of your services. * **Responder**: Viewer, and manage incidents, their updates and comments, and maintenance windows. Ideal for on-call engineers who communicate during an outage without touching the monitoring configuration. * **Member**: Responder, and manage monitors, status pages, projects and the alert rules of their projects. * **Admin**: Every permission. Admins access every project, and manage members, API keys, integrations, organization-wide alert rules, the organization settings and billing. The **Owner** is the admin who created the organization. Only the owner can delete the organization, and their role can't be changed. To transfer the ownership of your organization, contact [support@phare.io](mailto:support@phare.io). | Permission | Responder | Member | Admin | | :- | :-: | :-: | :-: | | View monitors, incidents, status pages and other resources | ✓ | ✓ | ✓ | | Manage incidents, their updates and comments | ✓ | ✓ | ✓ | | Manage maintenance windows | ✓ | ✓ | ✓ | | Manage monitors and status pages | | ✓ | ✓ | | Create and manage projects | | ✓ | ✓ | | Manage the alert rules of a project | | ✓ | ✓ | | Access every project | | | ✓ | | Edit and delete the incident updates and comments of others | | | ✓ | | Manage integrations and organization-wide alert rules | | | ✓ | | Invite and manage members | | | ✓ | | Manage API keys | | | ✓ | | Manage the organization settings, single sign-on and billing | | | ✓ | Viewers, responders and members only access the resources of [their projects](#accessing-projects), and responders and members can always edit and delete their own incident updates and comments. API keys have their own [permissions](/api-reference/introduction#permissions), set resource by resource. ## Inviting members Admins can invite as many members as needed from the [members page](https://app.phare.io/organization/members), choosing the role of each person and the projects they can access. Invited persons receive an email with a link to join your organization. ![Invitation form with the email, role and projects of each member](https://mintcdn.com/phare/CjNf7FpIIDKNfKF5/images/user-management/invite-user.avif?fit=max\&auto=format\&n=CjNf7FpIIDKNfKF5\&q=85\&s=f77b9bc6ebd94085aa18d35cef45b92c) ## Editing members To change the role or the projects of a member, click the member in the [members page](https://app.phare.io/organization/members). Admins can change the role of every member, except the owner's and their own, which another admin can change. ![Member edit page with the role and the projects of the member](https://mintcdn.com/phare/CjNf7FpIIDKNfKF5/images/user-management/member-edit.avif?fit=max\&auto=format\&n=CjNf7FpIIDKNfKF5\&q=85\&s=311dddc5fa0058f56f259aac85821a54) ## Accessing projects Viewers, responders and members only access the projects they are part of, chosen when inviting them. Need to adjust their access later? No problem, you can update their projects anytime from their member page as your team's needs evolve. **Admins** and the **Owner** can join any project they want, but the project selector only shows the ones they've actively joined. This keeps the workspace clean and focused. Other projects can still be modified or deleted from the organization's project page without cluttering the daily view. ![Project selector](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/user-management/project-selector.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=28527d2e2652091b40dab5cb6746c36a) ## Single sign-on Single sign-on (SSO) lets your members log in to Phare with the identity provider of your organization. You manage access to Phare in one place, and your security rules, like multi-factor authentication, apply to Phare too. Phare works with any identity provider supporting [OpenID Connect](https://openid.net/developers/how-connect-works/), like Okta, Microsoft Entra ID, Google Workspace, Auth0, JumpCloud, OneLogin, Keycloak, authentik and ZITADEL. > [!NOTE] > > Single sign-on is available on the [Scale plan](https://phare.io/pricing). Owners and admins can set it up in the single sign-on section of the [organization settings](https://app.phare.io/organization/settings#single-sign-on). ### How it works Once enabled, single sign-on is required for your whole organization: * **Admins and members** log in with your identity provider, which now manages their email, password and two-factor authentication. * **The owner** keeps their password and two-factor authentication, so they can always log in, even if your identity provider is down. * **New members still need an invitation**, Phare never creates accounts automatically. Existing members are linked to their identity provider account by email on their first login. If their email later changes in your identity provider, Phare updates it on their next login. Linked members show an **SSO** badge in the members list. ![Members list with a member linked to the identity provider](https://mintcdn.com/phare/CjNf7FpIIDKNfKF5/images/user-management/members-sso.avif?fit=max\&auto=format\&n=CjNf7FpIIDKNfKF5\&q=85\&s=8e2b5bfe775189efeaac8ae4f491a6df) ### Configure your identity provider Create an OpenID Connect **web application** in your identity provider (a confidential client using the authorization code flow) with the following settings: | Setting | Value | | :- | :- | | Redirect URI | Provided in the form when configuring SSO for your organization, for example `https://app.phare.io/sso/callback/a1B2c3D4` | | Scopes | `openid email profile` | | Client authentication | Client secret basic (`client_secret_basic`) | Your identity provider then gives you the **issuer URL**, **client ID** and **client secret** needed by Phare. Select your identity provider below for step-by-step instructions. > [accordion] Okta > > 1. In the Okta Admin Console, go to **Applications** > **Applications** (**Applications and Resources** > **Applications** on recent Okta organizations) and click **Create App Integration**. If Okta asks you to choose an experience, choose **Classic experience**. > 2. Choose the **OIDC - OpenID Connect** sign-in method and the **Web Application** type, then click **Next**. > 3. Enter a name, keep **Authorization Code** as the only grant type, and paste the redirect URI in **Sign-in redirect URIs**. > 4. Under **Assignments**, choose **Limit access to selected groups**, select the groups allowed to use Phare, then click **Save**. > 5. In the **General** tab, keep **Client secret** as client authentication, then copy the **Client ID** and **Client secret**. > > Then enter in Phare: > > * **Issuer URL**: your Okta domain, for example `https://your-organization.okta.com`. If you use a custom authorization server, enter its issuer instead, for example `https://your-organization.okta.com/oauth2/default`. > * **Client ID** and **Client secret**: the ones copied in step 5. > > Make sure to use your Okta domain, not the `-admin` domain of the Admin Console. Users not assigned to the application can't log in, you can assign more in its **Assignments** tab. > > Learn more in the [Okta documentation](https://help.okta.com/oie/en-us/content/topics/apps/apps_app_integration_wizard_oidc.htm). > [accordion] Microsoft Entra ID > > 1. In the Microsoft Entra admin center, go to **Entra ID** > **App registrations** and click **New registration**. > 2. Enter a name and choose the single tenant account type (**Accounts in this organizational directory only** or **Single tenant only**, depending on your tenant). Under **Redirect URI**, choose the **Web** platform, paste the redirect URI and click **Register**. > 3. In the **Overview** page, copy the **Application (client) ID** and the **Directory (tenant) ID**. > 4. In **Certificates & secrets**, click **New client secret**, choose an expiration and click **Add**. Copy the secret **Value**, it is only shown once. The **Secret ID** doesn't work with Phare. > 5. In **API permissions**, click **Grant admin consent for** your tenant, so members don't see a consent screen on their first login. > 6. To restrict access, open the application in **Enterprise apps**, set **Assignment required?** to **Yes** in **Properties**, then assign the users or groups allowed to use Phare in **Users and groups**. > > Then enter in Phare: > > * **Issuer URL**: `https://login.microsoftonline.com//v2.0`, with the **Directory (tenant) ID** copied in step 3. > * **Client ID**: the **Application (client) ID** copied in step 3. > * **Client secret**: the secret **Value** copied in step 4. > > Make sure to use your tenant ID in the issuer URL, not your domain name. Multi-tenant endpoints (`common`, `organizations` and `consumers`) don't work with Phare. > > Phare uses the **Email** property of your users, not their user principal name. Users without a mailbox may not have one, you can add it in the contact information of their profile. > > Client secrets expire after 24 months at most, create a new one and update it in Phare before it expires. > > Learn more in the [Microsoft documentation](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app). > [accordion] Google Workspace > > 1. In the Google Cloud console, select or create a project in your Google Workspace organization, and open **Google Auth Platform**. > 2. If Google Auth Platform is not configured yet, click **Get started**. Enter an app name and a support email, choose the **Internal** audience so only accounts of your Google Workspace can log in, and complete the setup. > 3. In **Clients**, click **Create client** and choose the **Web application** type. Paste the redirect URI in **Authorized redirect URIs**, then click **Create**. > 4. Copy the **Client ID** and **Client secret**, the client secret is only shown once. > > Then enter in Phare: > > * **Issuer URL**: `https://accounts.google.com` > * **Client ID** and **Client secret**: the ones copied in step 4. > > Google can take up to a few hours to apply a new redirect URI, and deletes clients unused for six months. > > Learn more in the [Google documentation](https://support.google.com/cloud/answer/15549257). > [accordion] Auth0 > > 1. In the Auth0 Dashboard, go to **Applications** > **Applications** and click **Create Application**. Choose **Regular Web Applications** and click **Create**. > 2. In the **Settings** tab, paste the redirect URI in **Allowed Callback URLs** and click **Save Changes**. Copy the **Domain**, **Client ID** and **Client Secret**. > 3. In the **Credentials** tab, choose the **Client Secret (Basic)** authentication method and click **Save**. New applications use **Client Secret (Post)** by default, which doesn't work with Phare. > 4. In the **Settings** tab, open **Advanced Settings** > **OAuth** and make sure the **JSON Web Token (JWT) Signature Algorithm** is **RS256**. > 5. To restrict access, only enable the connections used by your members in the **Connections** tab. > > Then enter in Phare: > > * **Issuer URL**: the **Domain** copied in step 2, for example `https://your-tenant.us.auth0.com/`, or your custom domain, for example `https://login.example.com/`. > * **Client ID** and **Client secret**: the ones copied in step 2. > > Phare refuses unverified emails, make sure your Auth0 database users clicked their verification link. You can send it again from **User Management** > **Users**. > > If you use the Auth0 Management API or Terraform, set the `regular_web` application type, the `RS256` signature algorithm and the `client_secret_basic` authentication method, as the default values don't work with Phare. > > Learn more in the [Auth0 documentation](https://auth0.com/docs/get-started/auth0-overview/create-applications/regular-web-apps). > [accordion] JumpCloud > > 1. In the JumpCloud Admin Portal, go to **Access** > **SSO Applications** and click **Add New Application**. > 2. Choose **Custom Application**, then select **Manage Single Sign-On (SSO)** and **Configure SSO with OIDC**. Enter a display label and click **Configure Application**. > 3. In the **SSO** tab: > * Paste the redirect URI in **Redirect URIs**. > * Choose **Client Secret Basic** as **Client Authentication Type**. > * Enter `https://app.phare.io/login#sso` as **Login URL**. > * In **Attribute Mapping**, check the **Email** and **Profile** standard scopes. > 4. Click **Activate**, then copy the **Client ID** and **Client Secret**, the client secret is only shown once. > 5. In the **User Groups** tab, select the groups allowed to use Phare and click **Save**. > > Then enter in Phare: > > * **Issuer URL**: `https://oauth.id.jumpcloud.com/`. If your JumpCloud organization is hosted in the EU, use `https://oauth.id.eu.jumpcloud.com/`, and in India `https://oauth.id.in.jumpcloud.com/`. > * **Client ID** and **Client secret**: the ones copied in step 4. > > Learn more in the [JumpCloud documentation](https://jumpcloud.com/support/sso-with-oidc). > [accordion] OneLogin > > 1. In the OneLogin admin portal, go to **Applications** > **Applications** and click **Add App**. > 2. Search for **OpenId Connect (OIDC)**, select it, enter a display name and click **Save**. > 3. In the **Configuration** tab, paste the redirect URI in **Redirect URI's**, optionally enter `https://app.phare.io/login#sso` as **Login Url**, and click **Save**. > 4. In the **SSO** tab, choose the **Web** application type and the **Basic** token endpoint authentication method, then click **Save**. Copy the **Client ID** and the client secret, using **Show client secret**. > 5. In the **Access** tab, select the roles allowed to use Phare and click **Save**. > > Then enter in Phare: > > * **Issuer URL**: the issuer URL shown in the **SSO** tab, for example `https://your-organization.onelogin.com/oidc/2`. > * **Client ID** and **Client secret**: the ones copied in step 4. > > Make sure the issuer URL ends with `/oidc/2`, not `/oidc`. OneLogin can take up to 10 minutes to apply a new redirect URI. > > Learn more in the [OneLogin documentation](https://developers.onelogin.com/docs/openid-connect/connect-to-onelogin/). > [accordion] Keycloak > > 1. In the Keycloak admin console, select your realm and go to **Clients** > **Create client**. > 2. In **General settings**, keep the **OpenID Connect** client type, enter a client ID such as `phare`, and click **Next**. > 3. In **Capability config**, turn **Client authentication** on, keep **Standard flow** checked, and click **Next**. > 4. In **Login settings**, paste the redirect URI in **Valid redirect URIs** and click **Save**. > 5. In the **Credentials** tab, keep the **Client Id and Secret** client authenticator and copy the **Client Secret**. > > Then enter in Phare: > > * **Issuer URL**: `https://keycloak.example.com/realms/`, or `https://keycloak.example.com/auth/realms/` for Keycloak versions older than 17. > * **Client ID** and **Client secret**: the ones from steps 2 and 5. > > Phare refuses unverified emails, and users created in the Keycloak admin console are unverified by default. Turn **Email verified** on in their profile, or enable **Verify email** in the **Login** tab of the realm settings. > > Keycloak must be publicly reachable over https on port 443, with its `hostname` option set to its public URL, and proxy headers enabled behind a reverse proxy. > > Keycloak can't restrict access to a client, use a dedicated realm to restrict who can log in to Phare. > > Learn more in the [Keycloak documentation](https://www.keycloak.org/docs/latest/server_admin/index.html#proc-creating-oidc-client_server_administration_guide). > [accordion] authentik > > 1. In the authentik admin interface, go to **Applications** > **Applications** and create an application with a new provider: **Create with Provider**, or **New Application** > **with New Provider** since authentik 2026.5. > 2. Enter a name, copy the **Slug** of the application, then choose the **OAuth2/OpenID Connect** provider type. > 3. In the provider settings: > * Keep the **Confidential** client type, then copy the **Client ID** and **Client Secret**. > * Paste the redirect URI in **Redirect URIs/Origins**, with the **Strict** matching mode. > * Select an RSA **Signing Key**, such as **authentik Self-signed Certificate**. Without a signing key, authentik signs ID tokens with HS256, which doesn't work with Phare. > 4. To restrict access, bind the users or groups allowed to use Phare. Then create the application. > > Then enter in Phare: > > * **Issuer URL**: `https://authentik.example.com/application/o//`, with the slug copied in step 2. > * **Client ID** and **Client secret**: the ones copied in step 3. > > Phare refuses unverified emails, and since authentik 2025.10 the default email mapping reports every email as unverified. If the emails of your users are verified, create a **Scope Mapping** in **Customization** > **Property Mappings**, with `email` as scope name and the following expression: > > ```python theme={null} > return { > "email": request.user.email, > "email_verified": True, > } > ``` > > Then, in the **Advanced protocol settings** of the provider, replace the default email mapping with your new mapping in **Scopes**. > > authentik must be publicly reachable over https on port 443, with the default issuer mode. Behind a reverse proxy, forward the `Host` and `X-Forwarded-Proto` headers. > > Learn more in the [authentik documentation](https://docs.goauthentik.io/add-secure-apps/providers/oauth2/create-oauth2-provider/). > [accordion] ZITADEL > > 1. In the ZITADEL console, go to **Projects** and create a project for Phare, or select an existing project. > 2. In the **Applications** of the project, click **New**. Enter a name, choose the **Web** type and click **Continue**. > 3. Choose the **Code** authentication method and click **Continue**. > 4. Paste the redirect URI in **Redirect URIs**, keep **Development Mode** off, then click **Continue** and **Create**. > 5. Copy the **Client ID** and **Client Secret**, the client secret is only shown once. > 6. In the **Token settings** of the application, enable **Include user's profile info in the ID Token** (**User Info inside ID Token** on older versions) and click **Save**. Without it, ZITADEL doesn't share the email of your users with Phare. > > Then enter in Phare: > > * **Issuer URL**: the domain of your instance, for example `https://your-instance.zitadel.cloud`, or your custom domain. > * **Client ID** and **Client secret**: the ones copied in step 5. > > To restrict access, enable **Check authorization on Authentication** (**Only authorized users can authenticate** on recent versions) in the project settings, and grant a project role to the users allowed to use Phare. > > If you host ZITADEL yourself, it must be publicly reachable over https on port 443, with its external domain, port and secure settings matching its public URL. > > Learn more in the [ZITADEL documentation](https://zitadel.com/docs/guides/manage/console/applications). > [accordion] Other providers > > Any OpenID Connect identity provider publishing its configuration at `/.well-known/openid-configuration` works with Phare. Your identity provider must: > > * Be publicly reachable over https on port 443, without redirects. Identity providers only available on a private network or behind a VPN don't work with Phare. > * Accept the `client_secret_basic` client authentication method. > * Sign ID tokens with RS256, RS384, RS512, ES256 or ES384. > * Include the `email` claim in the ID token. Phare only reads the ID token, not the userinfo endpoint. > * Not report the email as unverified. Phare refuses emails with an `email_verified` claim set to `false`. ### Enable single sign-on **1. Enter the configuration** In the single sign-on section of the [organization settings](https://app.phare.io/organization/settings#single-sign-on), click **Set up**. Then enter the issuer URL, client ID and client secret of your application. **2. Save & test** Click **Save & test**, then log in to your identity provider with the account matching your Phare email. **3. Done** Single sign-on is enabled once the test login succeeds. A wrong configuration is never saved, so it can't lock out your members. ![Redirect URI, issuer URL, client ID and client secret of the single sign-on configuration](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/user-management/sso-configuration.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=b029f26a00c5edb45dc64443276e3985) > [!WARNING] > > Enabling single sign-on logs out every member except the owner and yourself. ### Logging in Members click **Log in with single sign-on** on the login page, or open the [single sign-on login page](https://app.phare.io/login#sso) directly, then enter their work email to continue with your identity provider. ![Single sign-on login page asking for the work email](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/user-management/sso-login.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=c3c37b91d459bcd5453e5c9a666bc598) Members trying to log in with a password or to reset it are asked to use single sign-on instead. > [!TIP] > > Once their account is linked, the owner can log in with both single sign-on and their Phare password. Phare skips its two-factor authentication on single sign-on logins, as your identity provider handles it. ### Joining with an invitation New members accept their invitation with **Continue with single sign-on**, using the identity provider account matching their invitation email. ![Invitation to join an organization using single sign-on](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/user-management/sso-accept-invite.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=e68e6182b8924bf503765c275bdd1f4d) ### Changing the configuration ![Single sign-on section of the organization settings with the Edit button](https://mintcdn.com/phare/BSnSxwdZGWf6m6AC/images/user-management/sso-settings.avif?fit=max\&auto=format\&n=BSnSxwdZGWf6m6AC\&q=85\&s=94d15cfb52b9157fb5c84d138ef61863) To update the configuration, click **Edit** in the single sign-on section, then **Save & test**. Leave the client secret empty to keep the current one, it is stored encrypted and never shown again. Changing the issuer URL or the client ID, for example to move to another identity provider, logs out every member except the owner and yourself. Members are then linked again by email on their next login. Updating only the client secret doesn't log out anyone. ### Removing single sign-on To remove single sign-on, click **Edit** then **Remove** in the single sign-on section. Members are logged out and log in with their password again. Members who joined with single sign-on have no password yet, they can create one with the [forgot password](https://app.phare.io/forgot-password) page. > [!NOTE] > > Single sign-on keeps working if your organization leaves the Scale plan. The configuration can't be updated anymore, but it can still be removed. ### Security The organization owner receives an email when single sign-on is enabled, removed, or connected to another identity provider, with the admin who made the change, their IP address and browser. If the change is unexpected, review your single sign-on settings and contact [support@phare.io](mailto:support@phare.io). Phare uses the authorization code flow with PKCE, verifies the signature, issuer, audience, nonce and expiration of every ID token, and refuses unverified emails. ### Troubleshooting > [accordion] Single sign-on is not configured for this email > > This email doesn't belong to a member of an organization using single sign-on. If you are the owner, log in with your password, or link your account by running **Save & test** yourself. > [accordion] No Phare account matches this email > > Ask an admin of your organization for an invitation. If you are already a member, make sure your identity provider email matches your Phare email. > [accordion] Your identity provider signed you in as another account > > Log out of your identity provider, or use a private window, then log in with the account matching your Phare email. > [accordion] Your identity provider did not share your email address > > Make sure the `email` scope is allowed for the application, and that the account has an email in your identity provider. On Microsoft Entra ID, set the **Email** property of the user. On ZITADEL, enable **Include user's profile info in the ID Token** in the token settings of the application. > [accordion] Your identity provider reports this email as unverified > > Verify the email in your identity provider and try again. On Keycloak, turn **Email verified** on in the profile of the user. On Auth0, the user must click the verification link sent by Auth0. On authentik 2025.10 and later, replace the default email mapping as explained in the [authentik instructions](#configure-your-identity-provider). > [accordion] Your identity provider refused to complete the sign-in > > Make sure the client ID and client secret are correct, and that the application uses the `client_secret_basic` authentication method: **Client Secret (Basic)** on Auth0, **Client Secret Basic** on JumpCloud, **Basic** on OneLogin and **Code** on ZITADEL. On Microsoft Entra ID, make sure you use the **Value** of the client secret, not its secret ID, and that it hasn't expired. > [accordion] The ID token returned by your identity provider could not be verified > > Phare only accepts ID tokens signed with RS256, RS384, RS512, ES256 or ES384. On authentik, select an RSA **Signing Key** in the provider settings. On Auth0, make sure the signature algorithm of the application is **RS256**. > [accordion] Your identity provider shows a redirect URI error > > Make sure the redirect URI in your identity provider exactly matches the one shown in the single sign-on section of Phare. Some identity providers, such as Google and OneLogin, can take a few minutes to apply a new redirect URI. > [accordion] The issuer returned by your provider is different > > Use the issuer URL shown in the error message, it must exactly match the issuer published by your identity provider. > [accordion] Your identity provider must be publicly reachable > > Phare must reach your identity provider over https on port 443, from the internet. Identity providers on a private network or behind a VPN don't work with Phare. > [accordion] Your Phare account is linked to another account of your identity provider > > This usually happens when your identity provider account was deleted and created again. Contact [support@phare.io](mailto:support@phare.io) to reset your single sign-on link. > [accordion] Your single sign-on attempt expired > > Logins must be completed within 10 minutes. Start again from the login page.