# 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 page. This page covers preferences, contact details, password updates, and two-factor authentication.
## 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:
* **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.
## Create an API key
Only team members with the **Owner** or **Admin** role 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.
## Choosing the right scope
### 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
* 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
### Product scopes
Product scopes lets you restrict which parts of the Phare platform an API key can access. This helps apply the principle of least privilege and limits what a key can do if it is misused.
Each API key can be configured per product with one of the following access levels:
* **No access**
* **Read-only**
* **Read-write**
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.
## 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
# 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
# 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
# List alert rules
Source: https://docs.phare.io/api-reference/platform/alert-rules/list-alert-rules
get /alert-rules
Get a paginated list of alert rules.
# 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
# Get API info
Source: https://docs.phare.io/api-reference/platform/get-api-info
get /
Get basic API information
# Get an integration
Source: https://docs.phare.io/api-reference/platform/integrations/get-an-integration
get /apps/{app}/integrations/{integrationId}
Get an integration by ID
# List integrations
Source: https://docs.phare.io/api-reference/platform/integrations/list-integrations
get /apps/{app}/integrations
Get a paginated list of integrations for a specific app.
# Create a project
Source: https://docs.phare.io/api-reference/platform/projects/create-a-project
post /projects
Create a project
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
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
# List projects
Source: https://docs.phare.io/api-reference/platform/projects/list-projects
get /projects
Get a paginated list of projects.
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
# Get a user
Source: https://docs.phare.io/api-reference/platform/users/get-a-user
get /users/{userId}
Get a user by ID
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 users.
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 an incident
# Delete an incident
Source: https://docs.phare.io/api-reference/uptime/incidents/delete-an-incident
delete /uptime/incidents/{incidentId}
Delete an incident by ID
# Get an incident
Source: https://docs.phare.io/api-reference/uptime/incidents/get-an-incident
get /uptime/incidents/{incidentId}
Get an incident by ID
# List incidents
Source: https://docs.phare.io/api-reference/uptime/incidents/list-incidents
get /uptime/incidents
Get a paginated list of incidents
# Recover a incident
Source: https://docs.phare.io/api-reference/uptime/incidents/recover-an-incident
post /uptime/incidents/{incidentId}/recover
Recover a incident by ID
# Update an incident
Source: https://docs.phare.io/api-reference/uptime/incidents/update-an-incident
post /uptime/incidents/{incidentId}
Update an incident by ID
# Create an incident update
Source: https://docs.phare.io/api-reference/uptime/incidents/updates/create-an-incident-update
post /uptime/incidents/{incidentId}/updates
Create an incident update
# 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
# 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
# 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 incident updates
# 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 an incident update by ID
# Create a monitor
Source: https://docs.phare.io/api-reference/uptime/monitors/create-a-monitor
post /uptime/monitors
Create a monitor
# Delete a monitor
Source: https://docs.phare.io/api-reference/uptime/monitors/delete-a-monitor
delete /uptime/monitors/{monitorId}
Delete a monitor by ID
# Get a monitor
Source: https://docs.phare.io/api-reference/uptime/monitors/get-a-monitor
get /uptime/monitors/{monitorId}
Get a monitor by ID
# Get a monitor report
Source: https://docs.phare.io/api-reference/uptime/monitors/get-a-monitor-report
get /uptime/monitors/{monitorId}/report
Get uptime statistics for a single monitor by ID in the selected time window
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 monitors
# 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
# Resume a monitor
Source: https://docs.phare.io/api-reference/uptime/monitors/resume-a-monitor
post /uptime/monitors/{monitorId}/resume
Resume a monitor by ID
# Update a monitor
Source: https://docs.phare.io/api-reference/uptime/monitors/update-a-monitor
post /uptime/monitors/{monitorId}
Update a monitor by ID
# Get report
Source: https://docs.phare.io/api-reference/uptime/reports/get-a-report
get /uptime/reports
Get aggregated uptime statistics for the selected time window
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 status page
# 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
# Get a status page
Source: https://docs.phare.io/api-reference/uptime/status-pages/get-a-status-page
get /uptime/status-pages/{statusPageId}
Get a status page by ID
# 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 a status page current status by ID
# 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 status pages
# 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
# 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 monitoring events 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]()
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 of 2023
Source: https://docs.phare.io/changelog/platform/2023
Follow the updates and improvements made to the Phare platform in 2023.
## Alert policy duplication
*December 17th, 2023*
You can now duplicate an entire alert policy with all its rules to adapt Phare to how your company needs to be alerted.
***
## Status pages RSS and ATOM feed
*November 4th, 2023*
Status pages now offer an incident feed in RSS and ATOM format to let your users get updates on incidents.
***
## Status pages brand logo and feed subscription
*November 2nd, 2023*
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]()
***
## Incident comments
*October 29th, 2023*
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]()
***
## Incident impact
*October 27th, 2023*
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]()
***
## Admin user role
*October 23rd, 2023*
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]()
***
## Status pages
*October 21st, 2023*
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]()
***
## European mail server
*September 17th, 2023*
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.
***
## New branding
*August 21st, 2023*
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]()
***
## Improved monitoring page
*August 18th, 2023*
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]()
***
## Faster monitoring statistics
*August 17th, 2023*
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.
***
## Reviews
*August 15th, 2023*
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]()
***
## Deletion safeguard
*July 29th, 2023*
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]()
***
## Alert rules duplication
*July 28th, 2023*
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]()
***
## Performance monitoring history
*June 4th, 2023*
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]()
***
## Improved uptime precision
*May 29th, 2023*
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]()
***
## Incident events improvements
*May 27th, 2023*
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]()
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]()
***
## Multi-quota billing alerts
*May 17th, 2023*
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]()
***
## Integrations documentation
*May 14th, 2023*
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]()
***
## SMS integration
*May 13th, 2023*
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]()
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]()
***
## Improved design
*May 10th, 2023*
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]()
***
## Public launch
*May 5th, 2023*
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]()
***
## Documentation
*May 4th, 2023*
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]()
***
## Bunny CDN
*April 10th, 2023*
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]()
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.
***
## Billing overage management
*April 09th, 2023*
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]()
***
## End of beta
*April 8th, 2023*
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).
***
## Paid plan activation
*April 6th, 2023*
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.
***
## Incidents on performance chart
*April 2nd, 2023*
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]()
***
## Frequently asked questions
*April 1st, 2023*
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]()
***
## Stress test
*March 28th, 2023*
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.
***
## Pagination
*March 26th, 2023*
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]()
***
## Authentication pages redesign
*March 24th, 2023*
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]()
***
## Legal
*March 22nd, 2023*
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.
***
## Improved billing
*March 19th, 2023*
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]()
***
## Members management
*March 15th, 2023*
It is now possible to invite your colleagues to your organization, all accounts have unlimited numbers, the more, the merrier.
![Phare members management]()
You can assign members to projects and choose who has access to a project during creation.
![Phare project with members]()
For now, all members can perform every possible action in the scope of their respective project. More granular role management will come later.
***
## New landing page
*March 9th, 2023*
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).
***
## New alert rules
*March 9th, 2023*
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]()
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.
***
## Incident management
*March 8th, 2023*
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]()
All incidents are shown in the incidents section of MinUptime, you can quickly see their status and act accordingly.
![Incidents]()
To help you fix the situation, a timeline of events linked to an incident is shown on the incident's page.
![Incidents timeline]()
***
## Discord integration
*March 6th, 2023*
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]()
***
## Timezone and time format
*March 2nd, 2023*
Users can now select their Timezone and preferred time format (24 or 12-hour clock)
![Timezone and time format]()
***
## New monitor alert rules
*April 14th, 2023*
Two new alert rules have been added to receive alerts when a monitor is created or deleted
![New monitor rules]()
# Changelog of 2024
Source: https://docs.phare.io/changelog/platform/2024
Follow the updates and improvements made to the Phare platform in 2024.
## Shield status badges
**December 23rd, 2024**
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]()
***
## Send test alert rule notifications
*December 11th, 2024*
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]()
***
## Pushover integration
*December 6th, 2024*
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]()
***
## Quickly pause and resume monitors
*November 22th, 2024*
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]()
***
## Favicon support on status pages
*November 22th, 2024*
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]()
***
## Simplified TCP monitoring
*November 20th, 2024*
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]()
***
## Refreshed status pages
*November 11th, 2024*
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]()
***
## Incident management enhancements
*November 8th, 2024*
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]()
### 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]()
### 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]()
***
## Incident creation
*October 7th, 2024*
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]()
***
## Phare for good
*August 30th, 2024*
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]()
***
## Blog
*August 22th, 2024*
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/)
***
## Phare platform makeover
*August 5th, 2024*
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]()
***
## Improved monitoring performance chart
*July 29th, 2024*
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](/articles/downsampling-time-series-data).
![Performance chart]()
***
## Custom domains for status pages
*July 22th, 2024*
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]()
***
## Outgoing webhooks integration
*July 17th, 2024*
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]()
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]()
You can learn more about the outgoing webhooks integration in the [documentation](/integrations/outgoing-webhook).
***
## Billing quotas estimation
*July 11th, 2024*
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]()
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]()
Billing transparency is a key part of the Phare platform, and the tooling helps you monitor and control usage effectively.
***
## New API endpoints: alert rules, incidents and status pages
*July 7th, 2024*
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]()
***
## Monitoring timeout customization
*July 4th, 2024*
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]()
***
## Smart monitoring suggestion
*July 3rd, 2024*
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]()
***
## 30 second monitoring interval
*July 2nd, 2024*
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]()
***
## New changelog
*July 1st, 2024*
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/platform/2024). This new format should allow faster and more frequent updates.
***
## New monitoring regions
*May 28th, 2024*
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]()
***
## New monitoring infrastructure
*May 26th, 2024*
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.
***
## Alert policies API
*May 24th, 2024*
API endpoints to manage alert policies have been released and documented.
![Alert policies API]()
***
## REST API
*May 20th, 2024*
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.
***
## New Documentation
*May 15th, 2024*
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]()
***
## Incident comment and update alert
*May 7th, 2024*
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]()
***
## Hosting provider migration
*May 2nd, 2024*
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
Source: https://docs.phare.io/changelog/platform/2025
Follow the updates and improvements made to the Phare platform in 2025.
![Open metrics]()
## 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).
![France region]()
## 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.
![Status page subscription channels]()
## 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.
## 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.
![Incident AI generations]()
## 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.
![Smart Incident Merging]()
## 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.
![Ntfy integration]()
## 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).
![Slack threads support]()
## 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).
![Discord threads support]()
## 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).
![Email threads support]()
## 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.
![Incident notification filtering]()
## 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
![Monitor with POST, PUT, PATCH and a body]()
## 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.
![Status page timeframe]()
## 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.
![Mute projects]()
## 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.
![Improved timeline]()
## 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
## 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 ✌️
![Multi-monitor incidents]()
## 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.
![Pay with credits]()
## 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.
![Enhanced incident details]()
## 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.
## 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.
![Success assertions]()
## 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
![New monitoring options]()
## 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.
![Phare design refresh]()
## 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.
![Removed integration project scope]()
## 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.
![Custom headers]()
## 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.
![User agent secret key]()
## 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)
```
![Monitor certificate expiring alert rule]()
## 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.
![Monitor certificate discovered notification]()
## 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.
![SSL certificate tracking]()
## 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.
![New alerting system]()
## 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.
![Recipient delivery logs]()
## 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.
![New monitoring regions]()
## 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!
## 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.
![Phare on Discord]()
## 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)
![Preview regions]()
## 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.
![Telegram integration]()
## 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.
![Telegram integration]()
## 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.
![Integration logs]()
## 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]()
### 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]()
### 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.
## 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.
![Custom status page error]()
## 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.
![Password confirmation]()
## 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.
![Embed status badges customization]()
## 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.
## 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]()
#### Static badge
The static badge displays the current status of your status page with a pulse and a static label.
![Embed static badges]()
#### Live badge
The live badge displays the current status of your status page with a pulse and a live label.
![Embed live badges]()
# Changelog
Source: https://docs.phare.io/changelog/platform/2026
Follow the updates and improvements made to the Phare platform in 2026.
![Private status pages]()
## Private status pages
You can now restrict access to your status pages using three complementary control mechanisms, available on the Scale plan.
### IP allowlist
Grant automatic access to specific IP addresses or CIDR ranges. Requests from listed addresses bypass all other checks, making it the most seamless option for office networks or VPN exit nodes.
### Access token
Append a secret `token` query parameter to any status page URL to grant access, great for programmatic access. Works on the main page, feeds, and badge endpoints. When a browser visits with a valid token, a session cookie is set for 1 hour so subsequent visits don't need the token.
### Access password
Visitors are prompted with a login screen before they can view the page. Simple and effective for internal pages shared with team members or customers.
Read the [status pages access controls documentation](/uptime/status-pages#access-control) to learn more.
![Ordering datatables]()
## Ordering
It is now possible to order all data-tables on your Phare dashboard.
Order incidents by recovery date, monitors alphabetically, certificates by expiration dates, combined with filtering and text search this allows you to display the data you need for your workflow.
![Mistral Small 4 model]()
## Updated AI model
Phare updated the AI model used for to generate [incident summary and post-mortems](/uptime/incidents#incident-ai) from Magistral small to Mistral Small.
Mistral Small offers better performance, lower costs, optimized underlying architecture and a jump from 24B to 119B tokens.
![Partial API updates]()
## Partial API updates
The [update monitor](/api-reference/uptime/monitors/update-a-monitor) and [update incident](/api-reference/uptime/incidents/update-an-incident) endpoints now accepts partial update. This means you can update only the fields you want to change, leaving the rest unchanged and making the API more practical to use.
Support for more entities will be added in the near future, until all update endpoints support partial payloads.
![Custom region threshold]()
## Monitor region threshold
Monitor can now individually configure in how many regions they must be detected as down to trigger an incident. This allow you to fine tune your incident detection strategy to your specific needs.
![Support for dark and light status page logo]()
## Support for dark & light status page branding
It is now possible to show different logos and favicons on your status page depending on the theme shown.
![List of available ilert alert rules]()
## Upgraded ilert integration
You can now forward 5 alert events to your ilert account, and they all got upgraded with way more data than before. The following events are now compatible:
* Incident created
* Incident propagated
* Incident recovered
* Monitor certificate discovered
* Monitor certificate expiring
Checkout the full [ilert documentation](/integrations/ilert) to get started.
![Single region failure]()
## Single region failure detection
When monitoring from multiple regions, incidents were only triggered if at least two regions reported a failure, meaning a real regional outage could go completely undetected. Incidents are now flagged as soon as any single region goes down, regardless of how many regions you're monitoring from.
This change ensures your monitoring coverage actually reflects reality, with zero silent failures.
![2fa recovery codes]()
## 2FA recovery codes
It's now possible to get recovery codes when you have two-factor authentication (2FA) enabled on your account. This will allow you to recover your account if you ever loose access to your 2FA device.
![Dark theme status pages]()
## Status pages got a massive upgrade
Phare’s status pages just received a major upgrade. You can now fully customise the design with adjustable text and background colours, rounded or squared layouts, and flexible border styles to properly match your brand. And more importantly, DARK MODE IS FINALLY HERE, easier on the eyes and long overdue.
There’s now a complete uptime and incident history view, so users can clearly see what happened and when. A new RSS feed also makes it simple to stream real-time updates straight into Slack.
Phare status pages remain in the [top 1% for carbon efficiency with an A+ rating](https://www.websitecarbon.com/website/status-phare-io/).
![Incident data table of a monitor]()
## Monitor incidents datatable
The monitor page now includes a datatable showing all incidents for that monitor. You can search, filter, and sort incidents directly from the table, making it easier to track and review past issues.
![Terraform provider Phare in beta]()
## Official Terraform provider (beta)
Phare now has an official Terraform provider, available in beta. You can manage your projects, monitors, alert rules and status pages directly from your Terraform configuration. This has been one of the most requested features over the last three years, and it’s finally here after a huge amount of work.
Check out the [Terraform documentation](/integrations/terraform) to get started.
![New incident updates API endpoints]()
## New API endpoints for incident updates
Five new API endpoints are now available to help you manage incident updates through the API:
For organization-scoped API keys:
* [List incident updates](https://docs.phare.io/api-reference/uptime/incidents/updates/list-incident-updates)
* [Get an incident update](https://docs.phare.io/api-reference/uptime/incidents/updates/get-an-incident-update)
* [Create an incident update](https://docs.phare.io/api-reference/uptime/incidents/updates/create-an-incident-update)
* [Update an incident update](https://docs.phare.io/api-reference/uptime/incidents/updates/update-an-incident-update)
* [Delete an incident update](https://docs.phare.io/api-reference/uptime/incidents/updates/delete-an-incident-update)
Check out the [Phare API documentation](https://docs.phare.io/api-reference/introduction) for all available endpoints.
![New project API endpoints]()
## New API endpoints for project management
Five new API endpoints are now available to help you manage your projects directly through the API:
For organization-scoped API keys:
* [List projects](https://docs.phare.io/api-reference/platform/projects/list-projects)
* [Get a project](https://docs.phare.io/api-reference/platform/projects/get-a-project)
* [Create a project](https://docs.phare.io/api-reference/platform/projects/create-a-project)
* [Update a project](https://docs.phare.io/api-reference/platform/projects/update-a-project)
* [Delete a project](https://docs.phare.io/api-reference/platform/projects/delete-a-project)
Check out the [Phare API documentation](https://docs.phare.io/api-reference/introduction) for all available endpoints.
![Organization scoped API key]()
## Organization-scoped API keys
You can now create organization-scoped API keys. These keys provide access to all projects within your organization and allow full project management, including the ability to create and manage projects.
**Project-scoped API keys** remain available and are still best for setups where projects must stay clearly separated, such as agencies or larger organizations.
**Organization-scoped API keys** are ideal for small teams, startups, and infrastructure provisioning. Most API requests with these keys require a [project selection header](/api-reference/introduction#project-selection).
![Create update and recover incidents using the Phare API]()
## New API endpoints for incident management
Three new API endpoints are available to give you more possibilities to automate your incident workflows:
* [Create an Incident](https://docs.phare.io/api-reference/uptime/incidents/create-an-incident)
* [Update an Incident](https://docs.phare.io/api-reference/uptime/incidents/update-an-incident)
* [Recover an Incident](https://docs.phare.io/api-reference/uptime/incidents/recover-an-incident)
Check out the Phare [API documentation](https://docs.phare.io/api-reference/introduction) for all available endpoints.
![More control over incident timing]()
## More control over incident timing and history
Incidents can now be created with precise start and end times, and existing incidents can be adjusted if the original timing was off. This helps keep status pages accurate when something was detected late or when special circumstances change how an incident should be reported.
It’s also now possible to choose what type of status page update should be published at creation time. This is just a shortcut: all update types can still be posted later if needed.
![Monitor SMTP ports]()
## SMTP ports now available for monitoring
SMTP ports can now be monitored like other services over TCP. The usual ports are supported: **25**, **465**, **587**, and **2525**, making it easier to keep an eye on your in-house mail servers.
## 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 🌞
![New outgoing webhook JSON schema]()
## 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).
![Custom quota notification thresholds]()
## Improved notification preferences
Important organization-level notifications are now sent to all admins, not just the organization owner. In addition, every user can opt out of individual notification types from personal settings.
This removes the single-owner bottleneck while keeping you in control of what lands in your inbox.
![Custom quota notification thresholds]()
## 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.
![Custom legal and billing emails]()
## 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.
![ilert integration]()
## 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.
# 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]()
## Plan Selection
Now it's time to [choose your plan](https://phare.io/pricing). There are only two options: Hobby (free) and Scale (paid). Both plans pack the same powerful features, but the Hobby plan comes with more restricted usage limits. No long-term commitment is required, and plan changes or upgrades are available anytime.
![Plan selection]()
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.
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]()
Congratulations!
You've completed the Phare onboarding process. Now the fun part begins: start exploring the different products and features Phare has to offer.
Monitor your websites and APIs, handle incidents, manage certificates
and create status pages
# 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.
## 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.
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]()
## 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]()
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 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 25 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.
## 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]()
4. Give a name to your alert source and configure it as you wish
![Create and configure the Phare integration in ilert]()
5. Once configured, you will receive an integration key for the alert source
![Phare integration key in ilert]()
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
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]()
4. Click **Create** to save your integration
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 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]()
## 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.
# 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.
## 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.
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, find Ntfy in the list, and click the **New installation** button. Fill in the topic you created earlier and custom server hostname if required.
![Ntfy configuration]()
## 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.
![Outgoing webhooks installation]()
## 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]()
## 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
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.
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 }}"
}
}
```
### 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
* `monitor`
* `project`
* `monitor`
* `project`
* `certificate`
* `monitor`
* `project`
* `certificate`
* `monitor`
* `project`
* `incident`
* `project`
* `affected_monitors` (list)
* `incident`
* `project`
* `affected_monitors` (list)
* `incident`
* `project`
* `propagated_monitor` (the newly affected monitor)
* `affected_monitors` (list)
* `incident`
* `project`
* `recovered_monitor` (the recovered monitor)
* `affected_monitors` (list)
* `comment`
* `creator`
* `incident`
* `project`
* `affected_monitors` (list)
* `update`
* `creator`
* `incident`
* `project`
* `affected_monitors` (list)
### Available fields by object
| Field | What it means |
| :------------ | :------------------- |
| `id` | Unique incident ID |
| `slug` | Short incident code |
| `title` | Incident title |
| `description` | Incident description |
| `state` | Current state |
| `status` | Current status |
| `impact` | Impact level |
| Field | What it means |
| :----------------------- | :-------------------------------------------- |
| `id` | Unique monitor ID |
| `name` | Monitor name |
| `status` | Current status |
| `protocol` | Protocol type |
| `request` | Request details |
| `regions` | Regions used for checks |
| `interval` | Check interval (seconds) |
| `incident_confirmations` | Confirmations required to open an incident |
| `recovery_confirmations` | Confirmations required to resolve an incident |
| Field | What it means |
| :----- | :------------ |
| `id` | Project ID |
| `name` | Project name |
| `slug` | Project slug |
| Field | What it means |
| :-------------------------- | :------------------------ |
| `serial_number` | Certificate serial number |
| `subject_common_name` | Common name |
| `subject_alternative_names` | Alternative names |
| `issuer_common_name` | Issuer name |
| `issuer_organization` | Issuer organization |
| `not_before` | Valid from |
| `not_after` | Valid until |
| Field | What it means |
| :-------- | :-------------- |
| `id` | Comment ID |
| `content` | Comment content |
| Field | What it means |
| :-------- | :------------- |
| `id` | Update ID |
| `state` | Update state |
| `content` | Update content |
| Field | What it means |
| :------ | :------------ |
| `type` | Creator type |
| `label` | 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.
Here are some code examples to help you implement verification:
```javascript Node.js theme={null}
const crypto = require('crypto');
app.post('/webhook', (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 + ':' + JSON.stringify(req.body);
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}
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]()
# 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 to get started. Create as many connections as you need to ensure the right people have access to the right information.
![Phare integrations]()
## 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:
### 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]()
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.
## 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]()
## 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.
![Pushover configuration]()
## 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]()
# 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, find Slack in the list, and click the **New installation** button.
![Slack installation]()
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!
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]()
## 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]()
## 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]()
## 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]()
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.
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 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 page and follow the verification steps.
![Add phone number]()
## Configuration
You can include up to 25 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 after completing verification.
![SMS configuration]()
## 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:
* India
* Austria
* Belgium
* Croatia
* Denmark
* Estonia
* Finland
* France
* Germany
* Netherlands
* Norway
* Poland
* Portugal
* Slovenia
* Spain
* Sweden
* Switzerland
* United Kingdom
* 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.
## Configuration
After creating your Telegram integration in Phare, you'll get two convenient options:
* **Personal alerts**: 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 alerts**: A link/QR code for adding the bot to an existing Telegram group, ideal for team-wide monitoring alerts.
![Telegram configuration]()
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]()
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]()
## 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 website and server uptime monitoring, incident management, and much more.
![Phare.io]()
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.
Set up your account in a couple of minutes
Create programmatic interactions with the Phare API
Monitor your websites, manage incidents and create status pages
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. 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.
## 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.
## 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 updated | `uptime.monitor_certificate.discovered` | Sent when a monitor's SSL certificate is updated, 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. |
## 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.
# 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
## Certificate monitoring
Keep track of your SSL/TLS certificates with these helpful features:
* **Automatic notifications** when new certificates are discovered on your domains
* **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
## 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.
# 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 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.
## Manual incidents
Sometimes you need to create an incident even when your monitors haven't detected a problem. Perhaps a customer reported an issue with a service you're not actively monitoring, or you want to proactively communicate about planned maintenance.
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
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
* **Operational**: False alarm. Everything's working as expected
* **Maintenance**: Planned downtime for heavy-duty updates
* **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
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.
## Event timeline
![Incident event timeline]()
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.
## Incident updates
![Publish an incident update]()
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.
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]()
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.
### 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]()
### 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 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.
![Incident AI project settings]()
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.
# Monitors
Source: https://docs.phare.io/uptime/monitors
Monitor the availability of your websites, APIs and servers.
Monitors are the backbone of Phare Uptime. 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) and TCP checks according to your schedule.
## 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.
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.
When sending a request body with the POST, PUT or PATCH methods, a `Content-Type` header of your choice will be added automatically. You are free to change it if needed.
### 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)`
If you 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)`
### 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
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.
### Success assertions
![Phare Uptime success assertions]()
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.
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.
## 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.
## 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 two confirmations, but you can set this anywhere from one (immediate alerts) to five checks.
## 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.
### 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` |
| 🇳🇱 Netherlands | Amsterdam | `ng-nld-ams` |
#### 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` |
## 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]()
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 confirmation counts to prevent false positives
* Alerting you to redirections that might impact performance reporting
* Recommending more frequent checks for critical services
## Statistics
![Phare Uptime monitoring statistics]()
Each monitor will show detailed statistics to help you understand your service performance at a glance:
* **Performance charts** appear shortly after creating a monitor, showing response time trends
* 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 average response time, 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 protection
IP filtering is not reliable because the Phare Uptime monitoring agent is deployed on [Bunny.net's global network](https://bunnycdn.com/api/system/edgeserverlist), which means IPs could be shared with other Bunny.net customers.
The easiest way to filter the Phare Uptime monitoring agent is to use the `User-Agent` header. You can also add a secret value to the user agent to make it unique to your organization.
Need something more robust? [Contact support](https://phare.io/contact).
## 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, 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 your websites, manage incidents and create status pages
Phare Uptime is your digital babysitter that keeps an eye on your websites and APIs 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.
[Learn more about uptime monitoring](/uptime/monitors).
## 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 management table]()
## 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]()
## 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 rules]()
# 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 are lightning-fast and [among the most eco-friendly](https://www.websitecarbon.com/website/status-phare-io/) you can find.
## 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 page creation]()
## 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.
### 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]()
### 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:
Add this TXT record to your DNS settings to help Bunny.net verify your request:
| Type | Name | Target |
| :--- | :----------------- | :-------------------- |
| TXT | status.example.com | Bunny Support - Phare |
Head over to your [Bunny.net support hub](https://dash.bunny.net/support/tickets) and create a new ticket.
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 called `Bunny Support - Phare` as proof of ownership.
Thank you for being awesome!
```
Bunny's support team is usually quick, sit tight for a few minutes.
Once resolved, go back to your status page dashboard and hit the `Verify again` button to activate your custom domain.
![Verify failed status page domain]()
#### 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:
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).
## 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.
### 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
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]()
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]()
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]()
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 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]()
### 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]()
### 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]()
# User management
Source: https://docs.phare.io/user-management
Learn how to manage users and roles in Phare, invite team members, and control project access.
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.
## Roles
Phare keeps it simple with three roles: **Owner**, **Admin**, and **Member**. Each comes with its own permission set to help you build the right team structure.
* **Owner**: The organization's founder and primary administrator. Owners have all admin powers plus the ability to delete the organization and demote admins when necessary.
* **Admin**: The trusted lieutenants of your organization. Admins get full access to all resources, can join any project freely, and can promote other users to admin status.
* **Member**: Members have complete access to their assigned projects and can create new projects. They can also invite new members to join the organization, helping your team grow organically.
![Invite members]()
## Accessing projects
When inviting **Members** to your organization, you can customize which projects they can access. Need to adjust their access later? No problem. You can update permissions anytime as your team's needs evolve.
**Admins** and **Owners** can join any project they want, but the project selector only shows the ones they've actively joined. This keep 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]()