# API Introduction
Source: https://docs.phare.io/api-reference/introduction
Create programmatic interactions with the Phare API.
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
Welcome, this API allows you to interact programmatically with the Phare platform, enabling seamless integration and automation of almost everything that can be done in your control panel.
## Create an API key
<Info>Only team members with the **Owner** or **Admin** role can create an API key in your organization.</Info>
To access the Phare API, you will need to create an API key with the right accesses, this can be done on [your control panel](https://app.phare.io/organization/api-keys).
While creating an API key, you will be able to choose an access scope (Read / Write) for each Phare product as well as access to the resources of the Phare platform. You can find the list of available endpoints in the left navigation of this documentation.
You can create as many keys as necessary to fit your use case.
<Frame type="glass">
<div style={{position: 'relative', width: '100%', 'padding-top': '56.25%'}}>
<iframe src="https://iframe.mediadelivery.net/embed/238508/0ec7b14b-4512-4fc5-b74e-b42f8152c596?autoplay=false&loop=true&muted=true&preload=true&responsive=true" loading="lazy" allow="accelerometer;gyroscope;autoplay;encrypted-media;picture-in-picture;fullscreen" style={{border: 0, position: 'absolute', top: 0, height: '100%', width: '100%'}} />
</div>
</Frame>
## 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. The format for this header is as follows:
```bash Request Authorization header
Authorization: Bearer YOUR_API_KEY
```
Here’s an example of a cURL command to list the monitors in your project using your API key:
```sh
curl \
-X GET "https://api.phare.io/uptime/monitors" \
-H "Authorization: Bearer YOUR_API_KEY"
```
<Warning>Keep your API key confidential at all time. Do not share it publicly or expose it in client-side code.</Warning>
If you suspect that your API key has been compromised, revoke it immediately through your control panel and generate a new one.
## Rate limiting
Access to the API is currently rate limited to **100 calls per minute** across your organization. This means that all the API keys in your organization will share the same rate limiting.
***
If you are missing an API endpoint or need a custom rate limit for your organization, feel free to [contact us](mailto:support@phare.io), we'll be happy to find a solution for your 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
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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.
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# Get API info
Source: https://docs.phare.io/api-reference/platform/get-api-info
get /
Get basic API information
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# Delete an incident
Source: https://docs.phare.io/api-reference/uptime/incidents/delete-an-incident
delete /uptime/incidents/{incidentId}
Delete an incident by ID
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# Get an incident
Source: https://docs.phare.io/api-reference/uptime/incidents/get-an-incident
get /uptime/incidents/{incidentId}
Get an incident by ID
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# List incidents
Source: https://docs.phare.io/api-reference/uptime/incidents/list-incidents
get /uptime/incidents
Get a paginated list of incidents
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# Create a monitor
Source: https://docs.phare.io/api-reference/uptime/monitors/create-a-monitor
post /uptime/monitors
Create a monitor
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# Delete a monitor
Source: https://docs.phare.io/api-reference/uptime/monitors/delete-a-monitor
delete /uptime/monitors/{monitorId}
Delete a monitor by ID
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# Get a monitor
Source: https://docs.phare.io/api-reference/uptime/monitors/get-a-monitor
get /uptime/monitors/{monitorId}
Get a monitor by ID
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# List monitors
Source: https://docs.phare.io/api-reference/uptime/monitors/list-monitors
get /uptime/monitors
Get a paginated list of monitors
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# Update a monitor
Source: https://docs.phare.io/api-reference/uptime/monitors/update-a-monitor
post /uptime/monitors/{monitorId}
Update a monitor by ID
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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
<Warning>Please be aware that **the Phare API is currently in beta** and is subject to change.</Warning>
# 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.
<Frame type="glass">
<div style={{position: 'relative', width: '100%', 'padding-top': '56.25%'}}>
<iframe src="https://iframe.mediadelivery.net/embed/238508/9e75f896-215f-4b5c-96c9-fc61ba7d38bf?autoplay=true&loop=true&muted=true&preload=true&responsive=true" loading="lazy" allow="accelerometer;gyroscope;autoplay;encrypted-media;picture-in-picture;fullscreen" style={{border: 0, position: 'absolute', top: 0, height: '100%', width: '100%'}} />
</div>
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Status Page branding" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/37-status-page-branding.webp" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Incident impact & comments" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/36-incident-impact-and-comments.webp" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Incident management" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/35-incident-management.webp" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Invite user" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/34-user-roles.webp%20" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Status Page" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/33-status-pages.webp" />
</Frame>
***
## European mail server
*September 17th, 2023*
The mail server used to send you 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 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 symbole is a good representation of our mission to give you a signal when you need it so that you can run high quality production websites.
We hope that you like the new name and logo.
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.
<Frame type="glass">
<img class="border rounded-lg" alt="New branding" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/32-minkit-becomes-phare.webp" />
</Frame>
***
## 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).
<Frame type="glass">
<img class="border rounded-lg" alt="Monitoring statistics" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/31-monitoring-statistics.webp" />
</Frame>
***
## 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 for our own standard, because we're obsessed with speed. [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! You're welcome.
***
## 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**!
<Frame type="glass">
<img class="border rounded-lg" alt="Write a review" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/30-review.webp" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Deletion safeguard" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/29-deletion-safeguard.webp" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Alert rules duplication" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/28-alert-rule-duplication.webp" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Performance monitoring history" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/27-performance-history.webp" />
</Frame>
***
## Improved uptime precision
*May 29th, 2023*
Uptime percentage is now calculated with four digits precision which allows us to better calculate your long time SLA. 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Improved uptime precision" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/26-improved-uptime-precision.webp" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Incident event date time" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/24-incident-event-date-time.webp" />
</Frame>
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.
<Frame type="glass">
<img class="border rounded-lg" alt="Datetime tooltip" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/25-datetime-tooltip.webp" />
</Frame>
***
## 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, we now offer two different billing quotas: SMS alerts and monitoring events. The billing alert system, which is responsible for sending you 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 all the required foundation to bill anything, as part of a monthly plan or as additional usage. New feature will not require work on the billing infrastructure anymore, allowing me to ship faster!
<Frame type="glass">
<img class="border rounded-lg" alt="Multi-quota alerts" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/23-multi-quota-alerts.webp" />
</Frame>
***
## 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 country, the address email and phone numbers we use to send alerts, and much more.
<Frame type="glass">
<img class="border rounded-lg" alt="Integration documentation" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/22-integrations-documentation.webp" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="SMS integration" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/20-sms-integrations.webp" />
</Frame>
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.
<Frame type="glass">
<img class="border rounded-lg" alt="SMS integration" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/21-sms-integration-configuration.webp" />
</Frame>
***
## Improved design
*May 10th, 2023*
The [home](https://phare.io) and [pricing](https://phare.io/pricing) pages got updated with frostier design; we hope that you like as much as we do. A few other pages got updated as well to improve consistency across the website.
<Frame type="glass">
<img class="border rounded-lg" alt="Improved design" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/19-improved-design.webp" />
</Frame>
***
## Public launch
*May 5th, 2023*
The public launch on [ProductHunt](https://www.producthunt.com/posts/phare-uptime) went well, we're happy to see the first unsolicited users signing up and using the platform. We're also happy to see that the platform is stable and reliable, as only a few minor bugs were reported and fixed since the launch.
Thanks to everyone who voted for us on ProductHunt and participated in any way to the launch, it means a lot.
During the same period, we also acquired our first paying customer, which is a great milestone for the project.
<Frame type="glass">
<img class="border rounded-lg" alt="Phare on ProductHunt" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/18-producthunt-launch.webp" />
</Frame>
***
## Documentation
*May 4th, 2023*
Documentation has been published, it's still a work in progress, but it's already a great resource to learn about what our platform has to offer and how to use it.
<Frame type="glass">
<img class="border rounded-lg" alt="Documentation" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/17-documentation.webp" />
</Frame>
***
## Bunny CDN
*April 10th, 2023*
This week we migrated from [Cloudflare](https://www.cloudflare.com/) to [Bunny.net](https://bunny.net/). Bunny is a reliable content delivery platform with lightning-fast performances, making our platform even faster than before.
<Frame type="glass">
<img class="border rounded-lg" alt="Performance" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/16-performance.webp" />
</Frame>
But speed is not the only reason we spent a few days to migrate our service. Bunny is a European Union company, based in Slovenia.
This migration is part of our effort to rely as much as possible on European provider and ensure maximum privacy to our 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Overage management" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/15-overage-management.webp" />
</Frame>
***
## End of beta
*April 8th, 2023*
With 3.5M checks successfully performed, 272 incidents reported, and 639 notifications sent, we can confidently say all systems are stable enough to end the beta program. The last 6 weeks have been productive, with lots of features and improvements on the platform, and we heard a public launch might happen in early May!
If you would like to support our 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! We spent most of this week 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Incidents on performance chart" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/14-incidents-on-performance-chart.webp" />
</Frame>
***
## Frequently asked questions
*April 1st, 2023*
The pricing page now shows some frequently asked questions that I hope makes everything clearer about how Phare works. This is a small first step to fully fledged documentation.
<Frame type="glass">
<img class="border rounded-lg" alt="Frequently asked questions" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/13-faq.webp" />
</Frame>
***
## Stress test
*March 28th, 2023*
To make sure that our platform continues to work flawlessly under load, thousands of test monitors have been created for a few days to expose any performance weakness. We could identify a few culprits in the way we calculated uptime average and stored monitoring results, that 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Pagination" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/12-pagination.webp" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Authentication pages" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/11-authentication-pages.webp" />
</Frame>
***
## Legal
*March 22nd, 2023*
We published our [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 we approach open beta.
***
## 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:
<Frame type="glass">
<img class="border rounded-lg" alt="Phare billing management" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/10-billing-management.webp" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Phare members management" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/9-members-management.webp" />
</Frame>
You can assign members to projects and choose who has access to a project during creation.
<Frame type="glass">
<img class="border rounded-lg" alt="Phare project with members" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/8-project-with-members.webp" />
</Frame>
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*
Our 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Incident alert rules" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/7-incident-alert-rules.webp" />
</Frame>
Theses two new rules replace the former `Monitor status changed` rule that longer exists. All user's 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Incident management configuration" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/6-incident-management-configuration.webp" />
</Frame>
All incidents are shown in the incidents section of MinUptime, you can quickly see their status and act accordingly.
<Frame type="glass">
<img class="border rounded-lg" alt="Incidents" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/5-incidents.webp" />
</Frame>
To help you fix the situation, a timeline of events linked to an incident is shown on the incident's page.
<Frame type="glass">
<img class="border rounded-lg" alt="Incidents timeline" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/4-incidents-timeline.webp" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" alt="Discord integration" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/3-discord-integration.webp" />
</Frame>
***
## Timezone and time format
*March 2nd, 2023*
Users can now select their Timezone and preferred time format (24 or 12-hour clock)
<Frame type="glass">
<img class="border rounded-lg" alt="Timezone and time format" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/2-timezone-and-time-format.webp" />
</Frame>
***
## New monitor alert rules
*April 14th, 2023*
Two new alert rules have been added to receive alerts when a monitor is created or deleted
<Frame type="glass">
<img class="border rounded-lg" alt="New monitor rules" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/1-new-monitor-rules.webp" />
</Frame>
# 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/64-status-badges.webp" alt="Status badges" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/63-test-notifications.webp" alt="Test notifications" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/62-pushover-integration.webp" alt="Pushover integration" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/61-quick-pause-resume.webp" alt="Quick pause resume monitors" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/60-status-page-favicon.webp" alt="Status page favicon" />
</Frame>
***
## Simplified TCP monitoring
*November 20th, 2024*
TCP monitoring has been simplified to make it easier to set up and manage monitoring your services. No more need to specify a payload and an expected response.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/59-simplified-tcp-monitoring.webp" alt="Simplified TCP monitoring" />
</Frame>
***
## Refreshed status pages
*November 11th, 2024*
Status pages design has been slightly refreshed to provide a better look and feel. This also includes a few bug fixes and improve how incidents and downtime is presented to your users in a more coherent way.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/58-refreshed-status-pages.webp" alt="Refreshed status pages" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/55-resolve-incidents.webp" alt="Manually resolve incidents" />
</Frame>
### 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/56-publish-incident-updates-at-creation.webp" alt="Incident updates at creation" />
</Frame>
### 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/57-control-incident-downtime.webp" alt="Control incident downtime" />
</Frame>
***
## 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 incident 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 incident uses alert policies under the hood, and are not automatically resolved when associated monitors are successful.
We hope that you will be able to better communicate with your users during incidents with this new feature.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/54-create-incidents.webp" alt="Phare incident creation" />
</Frame>
***
## Phare for good
*August 30th, 2024*
We are thrilled to announce the "Phare for Good" initiative, offering an extended free plan to open source projects and nonprofit organizations.
This is our way of supporting those who are making a positive impact by providing our full suite of monitoring and incident management tools, completely free.
If you're driving change through technology or social causes, we're here to help keep your online presence strong and reliable.
Join the program here: [https://phare.io/for-good](https://phare.io/for-good)
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/53-phare-for-good.webp" alt="Phare platform makeover" />
</Frame>
***
## Blog
*August 22th, 2024*
We've had some exciting knowledge to share recently, so we've decided to launch an official blog for Phare. We'll post new content occasionally, but only when we have something valuable to share.
You can already read a few articles:
* [Downsampling time series data](https://phare.io/blog/downsampling-time-series-data/)
* [The Importance of Uptime Monitoring for SaaS Solutions](https://phare.io/blog/the-importance-of-uptime-monitoring-for-saas-solutions/)
* [How we run Ghost on Docker with subdirectory routing](https://phare.io/blog/how-we-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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/52-platform-makeover.webp" alt="Phare platform makeover" />
</Frame>
***
## 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 showed by your monitor.
Incidents are now displayed on the chart with their respective impact color, making it easier to understand any correlation at a glance.
If you're interested in learning more about how we generate the performance chart, you can read our article on [downsampling time series data](/articles/downsampling-time-series-data).
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/51-performance-chart.webp" alt="Performance chart" />
</Frame>
***
## 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).
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/50-custom-domain-status-pages.webp" alt="Custom domain status pages" />
</Frame>
***
## Outgoing webhooks integration
*July 17th, 2024*
Outgoing webhooks are now available 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/48-outgoing-webhook-alert-rule.webp" alt="Outgoing webhooks alert rules" />
</Frame>
Webhooks are secured with an HMAC sha256 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/49-outgoing-webhook-logs.webp" alt="Outgoing webhooks logs" />
</Frame>
You can learn more about the outgoing webhooks integration in the [documentation](/integrations/outgoing-webhook).
***
## Billing quotas estimation
*July 11th, 2024*
Billing quotas 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/46-billing-quotas-estimation.webp" alt="Billing quotas estimation" />
</Frame>
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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/47-monitoring-quotas-forecast.webp" alt="Monitoring quotas forecast" />
</Frame>
Billing transparency is a key part of our platform, and we are committed to providing you with the tools you need to monitor and control your 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 us to focus on stability to plan the end of the beta phase.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/45-new-api-endpoints.webp" alt="New API endpoints" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/44-monitoring-timeout.webp" alt="Monitoring timeout customization" />
</Frame>
***
## Smart monitoring suggestion
*July 3rd, 2024*
We are 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/43-monitoring-suggestions.webp" alt="Smart monitoring suggestion" />
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/42-30-second-monitoring.webp" alt="30 second monitoring" />
</Frame>
***
## New changelog
*July 1st, 2024*
Phare's changelog has been moved on our documentation site to harmonize the way that we write content on new Phare features. All previous entries where migrated to [this page](/changelog/platform/2024). We hope this new format will allow us to publish new entries faster and with a higher frequency.
***
## New monitoring regions
*May 28th, 2024*
Following our recent monitoring infrastructure migration, three new regions are released for uptime monitoring:
Say hello to Japan, the United Kingdom and Mexico.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/41-new-monitoring-regions.webp" alt="New monitoring regions" />
</Frame>
***
## New monitoring infrastructure
*May 26th, 2024*
Our monitoring infrastructure is the biggest operating cost and most important piece of the Phare Uptime product. As we perform millions of monitoring checks from many regions around the world, this infrastructure should be scalable, efficient and more importantly reliable. As we grew over the past few months, our previous solution based on [AWS Lambda](https://aws.amazon.com/lambda/) started to show its limit in terms of performance and cost, forcing us to look for an alternative solution.
Today we migrated all monitoring checks to a newly written infrastructure based on [Cloudflare workers](https://workers.cloudflare.com/). This solution allows us to maintain our generous free plan and a competitive price for our paid customers.
***
## Alert policies API
*May 24th, 2024*
API endpoints to [manage alert policies](/api-reference/alert-policies/list-alert-policies) have been released and documented.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/40-alert-policy-api.webp" alt="Alert policies API" />
</Frame>
***
## 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 action you can perform in your dashboard can also be done programmatically.
You will need to generate an API key to authenticate your organization, you are able to choose an access scope (Read / Write) for each Phare product as well as access to the resources of the Phare platform.
More informations are available on the [API documentation](/api-reference/introduction) page.
<Frame type="glass">
<div style={{position: 'relative', width: '100%', 'padding-top': '56.25%'}}>
<iframe src="https://iframe.mediadelivery.net/embed/238508/0ec7b14b-4512-4fc5-b74e-b42f8152c596?autoplay=false&loop=true&muted=true&preload=true&responsive=true" loading="lazy" allow="accelerometer;gyroscope;autoplay;encrypted-media;picture-in-picture;fullscreen" style={{border: 0, position: 'absolute', top: 0, height: '100%', width: '100%'}} />
</div>
</Frame>
***
## 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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/39-new-documentation.webp" alt="New documentation" />
</Frame>
***
## 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 everytime a new comment is published on an incident timeline, and the second when a team member publishes a status update for the incident.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/38-new-alert-rules.webp" alt="Incident comment and update alert" />
</Frame>
***
## 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 our 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.
## SSL certificate tracking is now built into Phare
*May 1st, 2025*
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.
But that's not all, you can also set up a new alert rule to get notified when a new certificate is discovered on any monitor. It's a great way to make sure they're getting renewed on time.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/79-monitor-certificate-discovered.webp" alt="Monitor certificate discovered notification" />
</Frame>
***
## New scoped alert rules system
*April 29th, 2025*
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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/78-alerting-system.webp" alt="New alerting system" />
</Frame>
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.
***
## Enhanced messaging reliability and logging
*April 18th, 2025*
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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/77-recipient-delivery-logs.webp" alt="Recipient delivery logs" />
</Frame>
***
## New monitoring regions and infrastructure overhaul
*April 14th, 2025*
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!
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/76-new-monitoring-regions.webp" alt="New monitoring regions" />
</Frame>
***
## New Scale plan price
*April 7th, 2025*
After nearly a year of intense optimization and some seriously messy spreadsheet formulas, it's finally done, 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, let’s scale together.
***
## Discord community
**April 2nd, 2025**
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 that write the code, and bully him into adding a dark mode (please don’t).
Jump in, say hi, and let’s have fun: [https://phare.io/discord](https://phare.io/discord)
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/75-phare-discord.webp" alt="Phare on Discord" />
</Frame>
***
## Preview regions
**February 17th, 2025**
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 why not all of them to help us test the new infrastructure at scale?
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/74-preview-regions.webp" alt="Preview regions" />
</Frame>
***
## Telegram integration
**January 30th, 2025**
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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/73-telegram-integration.webp" alt="Telegram integration" />
</Frame>
Read the [Telegram integration documentation](/integrations/telegram) to get started.
***
## Improved integration reliability
**January 27th, 2025**
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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/70-integration-logs.webp" alt="Integration logs" />
</Frame>
### 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 number, address 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 organization owner will be notified [1 hour and 18 minutes](https://docs.phare.io/integrations/outgoing-webhook#retry-policy) after the event creation.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/71-integration-issue-notification.webp" alt="Integration issue notification" />
</Frame>
### Automatic pause
Integrations that have been failing more than 3 consecutive times in a 7 days rolling window will be automatically paused. A notification will be sent to the organization owner when this happens.
***
## Data retention change
**January 20th, 2025**
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 email 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.
Monitor 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 error pages for status pages
**January 14th, 2025**
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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/72-custom-status-page-error.webp" alt="Custom satus page error" />
</Frame>
***
## Account security improvements
**January 8th, 2025**
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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/69-password-confirmation-flow.webp" alt="Password confirmation" />
</Frame>
***
## Embed status badge customization
**January 6th, 2025**
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.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/68-embed-status-badges-customization.webp" alt="Embed status badges customization" />
</Frame>
***
## Embed status badges
**January 3rd, 2025**
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 mode.
#### Pulse badge
The pulse badge only display the current status of your status page without any additional information, making it perfect to build your own components around it.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/65-embed-pulse-badge.webp" alt="Embed pulse badges" />
</Frame>
#### Static badge
The static badge displays the current status of your status page with a pulse and a static label.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/66-embed-static-badge.webp" alt="Embed static badges" />
</Frame>
#### Live badge
The live badge displays the current status of your status page with a pulse and a live label.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/changelog/67-embed-live-badge.webp" alt="Embed live badges" />
</Frame>
# Getting started
Source: https://docs.phare.io/getting-started
Get up and running with the Phare platform
In this guide, we will walk you through the onboarding process to get started with Phare. At the end of this guide, you will have your own organization account, and a basic understanding of how to make the most out of Phare.
## Account Creation
To get started with Phare, you need to create an account. You can create one on [the registration page](https://app.phare.io/register).
Once you have created your account, you will receive a confirmation email. Click on the link in the email to confirm your account and log in to Phare.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/getting-started/email-verification.webp" alt="Email verification" />
</Frame>
## Plan Selection
The first step of the onboarding process is to [select a plan](https://phare.io/pricing) for your organization between Phare's Hobby (free) and Scale (paid) offer. Both plans offer the same features, but the Hobby (free) plan has a more limited monthly usage. You can change or upgrade your organization's plan at any point in the future.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/getting-started/plan-selection.webp" alt="Plan selection" />
</Frame>
If you choose to subscribe to the Scale (paid) plan, you will be automatically redirected to our payment processor website to fill your billing information.
## Project creation
Once you have selected your plan, you can create your first project to organize your resources. In Phare, every resource is attached to your organization, or a project inside your organization. Using multiple projects to organize resources is optional, to keep things simple, try to replicate the internal structure of your organization in Phare.
Finally, keep in mind that projects are also used to organize team management access. If a resource should only be accessible by a subset of your organization's team members, this resource should be in its own project.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/getting-started/project-creation.webp" alt="Project creation" />
</Frame>
Congratulations! You have now completed the onboarding process for Phare. You can start to monitor your website and server uptime, manage incidents, and receive automated alerts.
<CardGroup cols={2}>
<Card title="Uptime" icon="wave-pulse" href="/uptime/overview">
Monitor your websites, manage incidents and create status pages
</Card>
<Card title="Integrations" icon="puzzle-piece" href="/integrations/overview">
Connect your favorite apps and services with Phare
</Card>
</CardGroup>
# Discord
Source: https://docs.phare.io/integrations/discord
Set up the Phare Discord integration to receive a message in your Discord server when your website or server is down.
The Discord integration allows you to send alert on a Discord server channel. You can find and configure it in the [integration](https://app.phare.io/organization/apps) section of your dashboard.
## Configuration
You can configure a single Discord channel per integration, and create as many integrations as needed to receive alerts on multiple Discord channels. When installing the Discord integration, you will be redirected to Discord to authorize the Phare application to send messages to your Discord server.
If you are a member of multiple Discord server, make sure to select the right one when authorizing the Phare application.
A default name will be used for your integration, but you can change it to anything you want. The name will be used to identify the integration in the list of integrations when configuring alert rules.
# Email
Source: https://docs.phare.io/integrations/email
Set up the Phare email integration to receive alerts when your website or server is down.
The Email integration allows you to send alert on any of your team members' emails. You can find and configure it in the [integration](https://app.phare.io/organization/apps) section of your dashboard.
## Email validation
To avoid spam and abuse, emails can only be sent to one of your registered team member's email. Support for generic email addresses will be added in the future.
## Configuration
Up to 25 team members can be configured to receive alerts for each Email integration.
## Receiving Emails
All alert emails are sent from the following email address:
* **[alerts@phare.io](mailto:alerts@phare.io)**
Phare's rely on two SMTP providers to send emails for reliability and redundancy:
* [Scaleway](https://www.scaleway.com/)
* [Brevo](https://www.brevo.com/)
# Outgoing webhook
Source: https://docs.phare.io/integrations/outgoing-webhook
Receive alerts by webhooks on third-party tools or build your own integration.
Outgoing webhooks enable Phare to communicate information to another service using HTTP callbacks. An HTTP POST request with a payload is sent to a designated URL that could be an HTTP endpoint in your own stack or a compatible third party.
## Configuration
To configure an outgoing webhook, two information are required:
* **Callback URL**: The URL where the webhook payload will be sent.
* **Signing secret**: A secret key that will be used to sign the webhook payload, allowing you to verify that the payload was sent by Phare.
Phare generates a safe secret for you, but you can provide your own if needed.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/outgoing-webhook/outgoing-webhook-installation.webp" alt="Outgoing webhooks installation" />
</Frame>
## Using the integration
Once installed in one of your projects, the outgoing webhook integration can be used when creating new alert rules. A default JSON payload is pre-filled based on the alert event you selected, but you can customize the payload JSON structure to fit your needs.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/outgoing-webhook/outgoing-webhook-alert-rule.webp" alt="Outgoing webhooks alert rule" />
</Frame>
## Payload customization
You can use a defined set of variables in the JSON payload to customize the message sent to the webhook, with each alert event having its own set of variables. The structure of the payload is not restricted as long as it is a valid JSON object.
The list of available variables for each alert event is defined as follows:
### Monitors
<AccordionGroup>
<Accordion title="Monitor Created">
| Variable | Value |
| :------------------------------------- | :--------------------------------------------------------------------------- |
| **\$PROJECT\_ID** | Id of the project this monitor belongs to |
| **\$PROJECT\_NAME** | Name of the project this monitor belongs to |
| **\$PROJECT\_SLUG** | Slug of the project this monitor belongs to |
| **\$MONITOR\_ID** | Id of the monitor |
| **\$MONITOR\_NAME** | Name of the monitor |
| **\$MONITOR\_STATUS** | Status of the monitor |
| **\$MONITOR\_PROTOCOL** | Protocol used by the monitor |
| **\$MONITOR\_REQUEST** | Object containing request information for the monitor |
| **\$MONITOR\_REGIONS** | Array of regions where the monitor is running |
| **\$MONITOR\_INTERVAL** | Interval in seconds between each check for the monitor |
| **\$MONITOR\_INCIDENT\_CONFIRMATIONS** | Number of confirmations required to trigger an incident for the monitor |
| **\$MONITOR\_RECOVERY\_CONFIRMATIONS** | Number of confirmations required to recover from an incident for the monitor |
</Accordion>
<Accordion title="Monitor Deleted">
| Variable | Value |
| :------------------------------------- | :--------------------------------------------------------------------------- |
| **\$PROJECT\_ID** | Id of the project this monitor belongs to |
| **\$PROJECT\_NAME** | Name of the project this monitor belongs to |
| **\$PROJECT\_SLUG** | Slug of the project this monitor belongs to |
| **\$MONITOR\_ID** | Id of the monitor |
| **\$MONITOR\_NAME** | Name of the monitor |
| **\$MONITOR\_STATUS** | Status of the monitor |
| **\$MONITOR\_PROTOCOL** | Protocol used by the monitor |
| **\$MONITOR\_REQUEST** | Object containing request information for the monitor |
| **\$MONITOR\_REGIONS** | Array of regions where the monitor is running |
| **\$MONITOR\_INTERVAL** | Interval in seconds between each check for the monitor |
| **\$MONITOR\_INCIDENT\_CONFIRMATIONS** | Number of confirmations required to trigger an incident for the monitor |
| **\$MONITOR\_RECOVERY\_CONFIRMATIONS** | Number of confirmations required to recover from an incident for the monitor |
</Accordion>
</AccordionGroup>
### Incidents
<AccordionGroup>
<Accordion title="Incident Created">
| Variable | Value |
| :------------------------------------- | :------------------------------------------------------------------------------------------------------- |
| **\$PROJECT\_ID** | Id of the project this incident belongs to |
| **\$PROJECT\_NAME** | Name of the project this incident belongs to |
| **\$PROJECT\_SLUG** | Slug of the project this incident belongs to |
| **\$MONITOR\_ID** | Id of the monitor that triggered the incident |
| **\$MONITOR\_NAME** | Name of the monitor that triggered the incident |
| **\$MONITOR\_STATUS** | Status of the monitor that triggered the incident |
| **\$MONITOR\_PROTOCOL** | Protocol used by the monitor that triggered the incident |
| **\$MONITOR\_REQUEST** | Object containing request information for the monitor that triggered the incident |
| **\$MONITOR\_REGIONS** | Array of regions where the monitor that triggered the incident is running |
| **\$MONITOR\_INTERVAL** | Interval in seconds between each check for the monitor that triggered the incident |
| **\$MONITOR\_INCIDENT\_CONFIRMATIONS** | Number of confirmations required to trigger an incident for the monitor that triggered the incident |
| **\$MONITOR\_RECOVERY\_CONFIRMATIONS** | Number of confirmations required to recover from an incident for the monitor that triggered the incident |
| **\$INCIDENT\_ID** | Id of the incident |
| **\$INCIDENT\_SLUG** | Slug of the incident |
| **\$INCIDENT\_TITLE** | Title of the incident |
| **\$INCIDENT\_ERROR** | Error message of the incident |
| **\$INCIDENT\_STATE** | State of the incident |
| **\$INCIDENT\_STATUS** | Status of the incident |
| **\$INCIDENT\_IMPACT** | Impact of the incident |
</Accordion>
<Accordion title="Incident Recovered">
| Variable | Value |
| :------------------------------------- | :------------------------------------------------------------------------------------------------------- |
| **\$PROJECT\_ID** | Id of the project this incident belongs to |
| **\$PROJECT\_NAME** | Name of the project this incident belongs to |
| **\$PROJECT\_SLUG** | Slug of the project this incident belongs to |
| **\$MONITOR\_ID** | Id of the monitor that triggered the incident |
| **\$MONITOR\_NAME** | Name of the monitor that triggered the incident |
| **\$MONITOR\_STATUS** | Status of the monitor that triggered the incident |
| **\$MONITOR\_PROTOCOL** | Protocol used by the monitor that triggered the incident |
| **\$MONITOR\_REQUEST** | Object containing request information for the monitor that triggered the incident |
| **\$MONITOR\_REGIONS** | Array of regions where the monitor that triggered the incident is running |
| **\$MONITOR\_INTERVAL** | Interval in seconds between each check for the monitor that triggered the incident |
| **\$MONITOR\_INCIDENT\_CONFIRMATIONS** | Number of confirmations required to trigger an incident for the monitor that triggered the incident |
| **\$MONITOR\_RECOVERY\_CONFIRMATIONS** | Number of confirmations required to recover from an incident for the monitor that triggered the incident |
| **\$INCIDENT\_ID** | Id of the incident |
| **\$INCIDENT\_SLUG** | Slug of the incident |
| **\$INCIDENT\_TITLE** | Title of the incident |
| **\$INCIDENT\_ERROR** | Error message of the incident |
| **\$INCIDENT\_STATE** | State of the incident |
| **\$INCIDENT\_STATUS** | Status of the incident |
| **\$INCIDENT\_IMPACT** | Impact of the incident |
</Accordion>
<Accordion title="Incident Comment Created">
| Variable | Value |
| :------------------------------------- | :------------------------------------------------------------------------------------------------------- |
| **\$PROJECT\_ID** | Id of the project this incident belongs to |
| **\$PROJECT\_NAME** | Name of the project this incident belongs to |
| **\$PROJECT\_SLUG** | Slug of the project this incident belongs to |
| **\$MONITOR\_ID** | Id of the monitor that triggered the incident |
| **\$MONITOR\_NAME** | Name of the monitor that triggered the incident |
| **\$MONITOR\_STATUS** | Status of the monitor that triggered the incident |
| **\$MONITOR\_PROTOCOL** | Protocol used by the monitor that triggered the incident |
| **\$MONITOR\_REQUEST** | Object containing request information for the monitor that triggered the incident |
| **\$MONITOR\_REGIONS** | Array of regions where the monitor that triggered the incident is running |
| **\$MONITOR\_INTERVAL** | Interval in seconds between each check for the monitor that triggered the incident |
| **\$MONITOR\_INCIDENT\_CONFIRMATIONS** | Number of confirmations required to trigger an incident for the monitor that triggered the incident |
| **\$MONITOR\_RECOVERY\_CONFIRMATIONS** | Number of confirmations required to recover from an incident for the monitor that triggered the incident |
| **\$INCIDENT\_ID** | Id of the incident |
| **\$INCIDENT\_SLUG** | Slug of the incident |
| **\$INCIDENT\_TITLE** | Title of the incident |
| **\$INCIDENT\_ERROR** | Error message of the incident |
| **\$INCIDENT\_STATE** | State of the incident |
| **\$INCIDENT\_STATUS** | Status of the incident |
| **\$INCIDENT\_IMPACT** | Impact of the incident |
| **\$USER\_ID** | Id of the user who created the comment |
| **\$USER\_EMAIL** | Email of the user who created the comment |
| **\$INCIDENT\_COMMENT\_ID** | Id of the comment |
| **\$INCIDENT\_COMMENT\_CONTENT** | Content of the comment |
</Accordion>
<Accordion title="Incident Comment Created">
| Variable | Value |
| :------------------------------------- | :------------------------------------------------------------------------------------------------------- |
| **\$PROJECT\_ID** | Id of the project this incident belongs to |
| **\$PROJECT\_NAME** | Name of the project this incident belongs to |
| **\$PROJECT\_SLUG** | Slug of the project this incident belongs to |
| **\$MONITOR\_ID** | Id of the monitor that triggered the incident |
| **\$MONITOR\_NAME** | Name of the monitor that triggered the incident |
| **\$MONITOR\_STATUS** | Status of the monitor that triggered the incident |
| **\$MONITOR\_PROTOCOL** | Protocol used by the monitor that triggered the incident |
| **\$MONITOR\_REQUEST** | Object containing request information for the monitor that triggered the incident |
| **\$MONITOR\_REGIONS** | Array of regions where the monitor that triggered the incident is running |
| **\$MONITOR\_INTERVAL** | Interval in seconds between each check for the monitor that triggered the incident |
| **\$MONITOR\_INCIDENT\_CONFIRMATIONS** | Number of confirmations required to trigger an incident for the monitor that triggered the incident |
| **\$MONITOR\_RECOVERY\_CONFIRMATIONS** | Number of confirmations required to recover from an incident for the monitor that triggered the incident |
| **\$INCIDENT\_ID** | Id of the incident |
| **\$INCIDENT\_SLUG** | Slug of the incident |
| **\$INCIDENT\_TITLE** | Title of the incident |
| **\$INCIDENT\_ERROR** | Error message of the incident |
| **\$INCIDENT\_STATE** | State of the incident |
| **\$INCIDENT\_STATUS** | Status of the incident |
| **\$INCIDENT\_IMPACT** | Impact of the incident |
| **\$USER\_ID** | Id of the user who published the update |
| **\$USER\_EMAIL** | Email of the user who published the update |
| **\$INCIDENT\_UPDATE\_ID** | Id of the update |
| **\$INCIDENT\_UPDATE\_STATE** | State of the update |
| **\$INCIDENT\_UPDATE\_CONTENT** | Content of the update |
</Accordion>
</AccordionGroup>
## Webhook security
Outgoing webhooks sent by Phare are signed with HMAC-SHA256 to ensure that the payload is coming from Phare and has not been tampered with. The signature also includes a timestamp to prevent replay attacks.
Verifying the signature of the webhook payload is done by computing the HMAC-SHA256 of three parts concatenated in a single string with the following format:
```text
{version}.{timestamp}.{payload}
```
The version is always `v0`, it is used to ensure backward compatibility in case of future changes to the signature algorithm. The timestamp is sent in the `X-Phare-Request-Timestamp` header and the signature of the payload is sent in the `X-Phare-Request-Signature` header.
You can find a few implementation examples below:
<CodeGroup>
```javascript Node.js
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
<?php
$secret = 'your-signing-secret';
$version = 'v0';
$timestamp = $_SERVER['HTTP_X_PHARE_REQUEST_TIMESTAMP'];
$signature = $_SERVER['HTTP_X_PHARE_REQUEST_SIGNATURE'];
$payload = $version . ':' . $timestamp . ':' . file_get_contents('php://input');
$hash = hash_hmac('sha256', $payload, $secret);
if ($hash === $signature) {
echo 'Signature verified';
} else {
echo 'Signature verification failed';
}
```
</CodeGroup>
<Info>You should also ensure that the timestamp is not too old to prevent replay attacks. A good practice is to check that the timestamp is not older than 5 minutes.</Info>
## Retry policy
In case the webhook fails to deliver the payload to the callback URL, Phare will retry sending the payload up to five times with an exponential backoff strategy.
To be considered successful, the webhook must return a status code in the `2xx` range within 30 seconds. If the webhook fails to deliver the payload after all retries, the webhook will not be retried again.
The first webhook payload is sent immediately after the event is triggered, in case of failure, the same payload will be resented after 1 minute, then 5 minutes, 10 minutes, and finally 1 hour.
The theoretical maximum time between the first request and the last retry, including the 30-second timeout is 1 hour and 18 minutes.
## Debugging
To help you troubleshoot issues with your outgoing webhooks, Phare provides a log of all the requests sent to your callback URL including request and response details.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/outgoing-webhook/outgoing-webhook-logs.webp" alt="Outgoing webhooks logs" />
</Frame>
# Integrations overview
Source: https://docs.phare.io/integrations/overview
Seamlessly connect your favorite apps and services with Phare
Integrations are a way to connect your Phare account with external services. At the moment, integration can only be used as notification channels, but more integration types will be added in the future.
Integration can be configured in the [Integrations](https://app.phare.io/organization/apps) section of your dashboard. You can create an unlimited number of integrations and choose for each one if they're available for your whole organization or scope them by project.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/overview/phare-integrations.webp" alt="Phare integrations" />
</Frame>
## Alert integrations
Alert integrations are used to send notifications when an alert rule is triggered. You can define the integration to use for each alert rule to route the notification to the right channel for your team.
The following integrations are available for alerting:
<CardGroup cols={2}>
<Card title="Discord" icon="discord" href="/integrations/discord" horizontal />
<Card title="Email" icon="envelope" href="/integrations/email" horizontal />
<Card title="Outgoing webhooks" icon="webhook" href="/integrations/outgoing-webhook" horizontal />
<Card title="Pushover" icon={<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 600 600"><path fill="currentColor" d="m280.949 172.514 74.48-9.8-72.52 163.66c12.74-.98 25.233-5.307 37.48-12.98 12.253-7.68 23.527-17.317 33.82-28.91 10.287-11.6 19.187-24.503 26.7-38.71 7.513-14.213 12.903-28.18 16.17-41.9 1.96-8.493 2.86-16.66 2.7-24.5-.167-7.84-2.21-14.7-6.13-20.58-3.92-5.88-9.883-10.617-17.89-14.21-8-3.593-18.86-5.39-32.58-5.39-16.007 0-31.77 2.613-47.29 7.84-15.513 5.227-29.887 12.823-43.12 22.79-13.227 9.96-24.74 22.373-34.54 37.24-9.8 14.86-16.823 31.763-21.07 50.71-1.633 6.207-2.613 11.187-2.94 14.94-.327 3.76-.407 6.863-.24 9.31.16 2.453.483 4.333.97 5.64a35.55 35.55 0 0 1 1.23 3.92c-16.66 0-28.83-3.35-36.51-10.05-7.673-6.693-9.55-18.37-5.63-35.03 3.92-17.313 12.823-33.81 26.71-49.49 13.88-15.68 30.373-29.483 49.48-41.41 19.113-11.92 40.02-21.39 62.72-28.41 22.707-7.027 44.84-10.54 66.4-10.54 18.947 0 34.87 2.693 47.77 8.08 12.907 5.393 22.953 12.5 30.14 21.32 7.187 8.82 11.677 19.11 13.47 30.87 1.8 11.76 1.23 24.01-1.71 36.75-3.593 15.353-10.373 30.79-20.34 46.31-9.96 15.513-22.453 29.56-37.48 42.14-15.027 12.573-32.26 22.78-51.7 30.62-19.433 7.84-40.093 11.76-61.98 11.76h-2.45l-62.23 139.65h-70.56l138.67-311.64Z"/></svg>} href="/integrations/pushover" horizontal />
<Card title="SMS" icon="message-lines" href="/integrations/sms" horizontal />
<Card title="Slack" icon="slack" href="/integrations/slack" horizontal />
<Card title="Telegram" icon="telegram" href="/integrations/telegram" horizontal />
</CardGroup>
All integrations notify the organization owner when an issue occurs. For the SMS, Email and Outgoing Webhooks integrations, a detailed list of failed number, address or requests is provided to help you identify the issue.
***
If your team is using a service not yet supported by Phare, please [contact us](mailto:support@phare.io), we'll be happy to add it to our roadmap.
# Pushover
Source: https://docs.phare.io/integrations/pushover
Set up the Phare integration with Pushover to receive alerts on your preferred device.
The Pushover integration allows you to send alert on your preferred device using the Pushover app. You can find and configure it in the [integration](https://app.phare.io/organization/apps) section of your dashboard.
## Pre-requisites
In order to use the Pushover integration, you need to have a Pushover account and create an application on the Pushover website to obtain an API Key.
You can find your user key in the [Pushover dashboard](https://pushover.net/) and the link to [create a new application](https://pushover.net/apps/build) at the bottom of your dashboard page. You are free to configure the application as you wish, or you can copy the following 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)
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/pushover/pushover-app-creation.webp" alt="Pushover app creation" />
</Frame>
## Configuration
To configure the Pushover integration in Phare, you need to provide your user key and the API key you obtained when creating the application.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/pushover/pushover-configuration.webp" alt="Pushover configuration" />
</Frame>
## Usage
Once the integration is configured, you can select it as a notification channel when creating or editing alert rules. Each alert rule can specify a Pushover priority, allowing fine-grained control over the priority of each notification.
Alerts configured with the `Emergency` priority will require two additional parameters: `retry` and `expire`. These parameters are used to resend the notification if it's not acknowledged within the specified time frame and their behavior is [documented in the Pushover documentation](https://pushover.net/api#priority).
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/pushover/pushover-alert-rule.webp" alt="Pushover alert rule configuration" />
</Frame>
# Slack
Source: https://docs.phare.io/integrations/slack
Set up the Phare Slack integration to receive a message in your Slack workspace when your website or server is down.
The Slack integration allows you to send alerts on a Slack workspace channel.
## Installation
To add integrate Phare with your Slack workspace, browse the [list of available integrations](https://app.phare.io/organization/apps) on your dashboard, select Slack, and click on the **New installation** button.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/slack/slack-installation.webp" alt="Slack installation" />
</Frame>
You will then be redirected to Slack to authorize the Phare application to send messages to your Slack workspace.
## Configuration
You can configure a single Slack channel per integration, and create as many integrations as needed to receive alerts on multiple Slack channels. When installing the Slack integration you will be redirected to Slack to authorize the Phare application to send messages to your Slack workspace.
If you are a member of multiple Slack workspaces, make sure to select the right one when authorizing the Phare application.
A default name will be used for your integration, but you can change it to anything you want. The name will be used to identify the integration in the list of integrations when configuring alert rules.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/slack/slack-configuration.webp" alt="Slack configuration" />
</Frame>
## Receiving Slack messages
When an alert rule using the Slack integration is triggered, a message will be sent to the selected Slack channel. You can find out more about alert policies in the [alerting documentation](/uptime/alerting).
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/slack/slack-notification.webp" alt="Slack notification" />
</Frame>
## Privacy
Phare only shares with Slack the information required to display the notification you configured. Phare store your workspace name and identifier, as well as an access token to send messages to your Slack workspace. You can review Phare's [privacy policy](https://phare.io/legal/privacy-policy) for more information on your data are handled.
# SMS
Source: https://docs.phare.io/integrations/sms
Set up the Phare SMS integration to receive a message on your phone when your website or server is down.
<Warning>This integration is only available with a Scale plan subscription and in selected countries</Warning>
The SMS integration allows you to send alert on any of your team members' phone numbers. You can find and configure it in the [integration](https://app.phare.io/organization/apps) section of your dashboard.
## Phone number validation
To avoid spam and abuse, we require every one of your team members to verify their phone number before they can receive an alert. To do so, they need to go to the [user settings](https://app.phare.io/user/settings) page and follow the process to add their phone number.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/sms/add-phone-number.webp" alt="Add phone number" />
</Frame>
## Configuration
Up to 25 team members can be configured to receive alerts for each SMS integration. When using the team members' search, you will see for each one if they have a verified phone number or not. You can add a team member without a verified phone number, but they will only receive alerts after they have verified their phone number.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/sms/sms-configuration.webp" alt="SMS configuration" />
</Frame>
## Receiving SMS
When an alert is triggered, the team members configured to receive SMS alerts will receive a message from the **Phare** originator.
## Supported countries
At the moment, the SMS integration is available in the following countries:
<AccordionGroup>
<Accordion title="Europe">
* Austria
* Belgium
* Bulgaria
* Croatia
* Cyprus
* Czech Republic
* Denmark
* Estonia
* Finland
* France
* Germany
* Greece
* Hungary
* Iceland
* Ireland
* Italy
* Latvia
* Lithuania
* Luxembourg
* Malta
* Netherlands
* Norway
* Poland
* Portugal
* Romania
* Slovakia
* Slovenia
* Spain
* Sweden
* Switzerland
* United Kingdom
</Accordion>
<Accordion title="North America">
* Canada
</Accordion>
</AccordionGroup>
## Request a new country
Each country requires a specific compliance process to be able to send SMS messages. If your team would like to receive alerts in a country that is not yet supported, please [ontact us](mailto:support@phare.io). It usually takes 3 business days to add a new country to the list.
# Telegram
Source: https://docs.phare.io/integrations/telegram
Set up the Phare Telegram integration to receive alerts when your website or server is down.
The Telegram integration allows you to send alerts to your Telegram account. You can find and configure it in the [integration](https://app.phare.io/organization/apps) section of your dashboard.
## Configuration
Once your Telegram integration created in your Phare dashboard, two links / QR codes will be displayed.
* The first one is used to receive Phare alerts in a private conversation with the Phare Telegram bot. You can share this link with your team members to allow them to receive alerts on their Telegram account.
* The second one is used to receive alerts on an existing Telegram group.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/telegram/telegram-configuration.webp" alt="Telegram configuration" />
</Frame>
After opening the link or scanning the QR code, follow the instructions on your device and start the conversation with the Phare Telegram bot. You will receive a message confirming that the integration is successfully configured.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/integrations/telegram/telegram-start.webp" alt="Telegram start" />
</Frame>
<Warning>For security reasons, it is not possible to receive Phare alerts by adding directly the Phare Telegram bot from the application. You must use the provided links or QR code.</Warning>
## Usage
Once the integration is configured, you will start receiving alerts in your Telegram application. If you would like to stop receiving alerts, you can use the `/stop` command in the conversation with the Phare Telegram bot and then delete the conversation.
# Introduction
Source: https://docs.phare.io/introduction
Discover how Phare can help with website and server uptime monitoring, incident management, and much more.
<img className="block rounded-md" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/hero.webp" alt="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 making websites, our comprehensive documentation will walk you through every step of the process.
<CardGroup cols={2}>
<Card title="Getting started" icon="rocket-launch" iconType="regular" href="/getting-started">
Set up your account in a couple of minutes
</Card>
<Card title="API Reference" icon="terminal" iconType="regular" href="/api-reference/introduction">
Create programmatic interactions with the Phare API
</Card>
<Card title="Uptime" icon="wave-pulse" iconType="regular" href="/uptime/overview">
Monitor your websites, manage incidents and create status pages
</Card>
<Card title="Integrations" icon="puzzle-piece" iconType="regular" href="/integrations/overview">
Seamlessly connect your favorite apps and services with Phare
</Card>
</CardGroup>
# Alerting
Source: https://docs.phare.io/uptime/alerting
Learn how to configure alert rules with Phare Uptime.
Phare Uptime allows you to receive real-time notifications when specific events occur, such as monitor failures, SSL certificate issues, or incident updates. The system is built around flexible, scoped alert rules.
<Frame type="glass">
<div style={{position: 'relative', width: '100%', 'padding-top': '56.25%'}}>
<iframe src="https://iframe.mediadelivery.net/embed/238508/be98c500-251c-41cc-90d7-a20f0077cbeb?autoplay=false&loop=true&muted=true&preload=true&responsive=true" loading="lazy" allow="accelerometer;gyroscope;autoplay;encrypted-media;picture-in-picture;fullscreen" style={{border: 0, position: 'absolute', top: 0, height: '100%', width: '100%'}} />
</div>
</Frame>
### Alert Rules
An alert rule defines:
* Event: The event that triggers the alert (e.g., incident created, certificate expiring).
* Scope: Whether the rule applies organization-wide or within a specific project.
* Rate limit: Prevents spamming your team members with notifications.
* Alert integration: Which integration to use for sending notifications (e.g., email, Slack, Discord).
### Event
The event specifies what action or occurrence will trigger the alert. Phare Uptime supports a variety of events, including:
* Monitor created
* Monitor deleted
* Monitor certificate updated
* Monitor certificate expiring
* Incident created
* Incident recovered
* Incident comment created
* Incident update published
### Scope
You can choose the scope of each alert rule:
* Organization: The rule applies to all matching events in the organization.
* Project: The rule applies only to events that occur within a specific project.
This scoped system provides both flexibility and clarity, ensuring alerts are relevant to the right context.
### Rate Limiting
To prevent notification overload, alert rules support rate limiting. This allows you to restrict how often an alert rule will send a notification in a given time frame. For example, you can set a rule to notify you only once every 10 minutes, even if the triggering event occurs multiple times within that period.
### Notification Channels
Any [alert rule integration](/integrations/overview) can be used to send notifications. You can create an unlimited number of alert rules for each integration, allowing you to customize how and when you receive notifications.
# Incident Management
Source: https://docs.phare.io/uptime/incident-management
Learn how to manage the lifecycle of an incident with Phare Uptime incident management.
Incident management is the process of managing the lifecycle of an incident. Phare Uptime provides a fully automated incident management system to manage the lifecycle of an incident, from creation to recovery.
## Incident creation
An incident is created when a monitor fails, in respect to the monitor's confirmation configuration and checks (keywords, SSL...). The default alert rules will email you a notification when an incident is created.
## Incident recovery
An incident is resolved when a monitor succeeds, in respect to the monitor's recovery configuration and checks (keywords, SSL...). The default alert rules will email you a notification when an incident recovers.
## Impact
Incidents can be classified by their impact on your users. Project members can manually set the impact of an incident to one of the following values:
* **Unknown**: The impact of the incident is not known yet. (default)
* **Operational**: The incident has no impact on your users.
* **Maintenance**: The incident is caused by a planned maintenance.
* **Degraded performance**: The incident has a degraded performance impact on your users.
* **Partial outage**: The incident impacts only some users or some parts of your service.
* **Major outage**: The incident impacts all your users or all your service.
The impact of an incident can be used internally to prioritize the incident resolution, and is reported in status pages if one is linked to the monitor that triggered the incident. In case of incident impact is set to **unknown**, Phare will set your monitor status to **down** without additional details in your status page.
## Event timeline
The event timeline is a powerful tool to help you understand what happened during an incident. It shows you the status of the monitor at each check, and the alert rules that were triggered.
Project members can comment on the incident timeline to share findings and resolve the incident faster. Comments can be written using a rich text editor, and are compatible with the Markdown syntax.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/uptime/incident-management/incident-timeline.webp" alt="Incident event timeline" />
</Frame>
# Monitors
Source: https://docs.phare.io/uptime/monitors
Monitor the availability of your website and servers.
Monitors are the core of Phare Uptime, they are used to monitor the availability of your website and servers, and send you alerts when something goes wrong. Monitors can perform HTTP(s) and TCP checks to determine if your website or server is online and working as expected.
<Frame type="glass">
<div style={{position: 'relative', width: '100%', 'padding-top': '56.25%'}}>
<iframe src="https://iframe.mediadelivery.net/embed/238508/2f903d7c-82ae-490b-a37c-9e6e7bcf446b?autoplay=false&loop=true&muted=true&preload=true&responsive=true" loading="lazy" allow="accelerometer;gyroscope;autoplay;encrypted-media;picture-in-picture;fullscreen" style={{border: 0, position: 'absolute', top: 0, height: '100%', width: '100%'}} />
</div>
</Frame>
### HTTP(s)
An HTTP(s) request is sent to your website, Phare Uptime check the response status code and the presence of an optional keyword in the response body to determine if your website is online and working. SSL certificate monitoring is automatically activated for websites using HTTPS, which will alert you when a certificate is expired or misconfigured.
### TCP
A TCP socket connection is established with your server to determine if it is online and working as expected.
## Interval
You can configure the interval at which Phare Uptime will send requests to your website or server. The default interval is 1 minute, but you can configure it to be as low as 30 seconds or 1 / 2 / 3 / 5 / 10 / 15 / 30 minutes.
## Confirmations & recovery
Phare Uptime uses a confirmation system to avoid false positives.
A monitor is marked as down or recovered only after a certain number of consecutive failures / successes.
The default number of confirmations is two, but you can configure it to be anything between one (immediate confirmation) and five confirmations.
## Regions
Phare Uptime provides 11 regions around the world to monitor your website or server from different locations. You can choose to monitor your website or server from a single region or from multiple regions. **Using at least two regions is recommended to avoid false positives, and be resilient against large scale outage**.
## Alert Rules
Phare Uptime provides a powerful alerting system to notify your team members of an incident based on [alert rules](/uptime/alerting).
## Firewall protection
IP filtering is not recommended as Phare rely on IPs provided by [Bunny.net global network](https://bunnycdn.com/api/system/edgeserverlist) to provide the widest available monitoring offer at an affordable price. The easiest solution to filter Phare's uptime agent traffic is to filter by user-agent.
If you require a more robust option, please [contact us](mailto:support@phare.io).
## User agent
Phare Uptime monitoring HTTP requests always contain the following user-agent:
> `Mozilla/5.0 (compatible; Phare/1.0; +https://phare.io/products/uptime)`
## Private monitoring agent
It is possible to set up a private monitoring agent in a region of your choice. This can be used to comply with complex requirements, large scale monitoring, or private VPN access.
You can [contact us](mailto:support@phare.io) to discuss your needs.
## Limits
Phare's monitoring infrastructure works at an extraordinary scale, but comes with a few drawbacks:
* **No IP filtering**: Phare uptime agent uses a vast range of IPs provided by [Bunny.net global network](https://bunnycdn.com/api/system/edgeserverlist) that are shared.
* **Enforced HTTPS validation**: Website accessed with the HTTPS protocol MUST use a valid SSL certificate.
* **Restricted ports**: The following ports are restricted and cannot be used for TCP monitoring: 25, 465, 587, and 2525.
We understand that these limits can be a major blocking point, feel free to [contact us](mailto:support@phare.io) if you would like to discuss alternative solutions.
# Uptime overview
Source: https://docs.phare.io/uptime/overview
Monitor your websites, manage incidents and create status pages
Phare Uptime helps you make sure your website and server are always up and running, and sends you an alerts when something goes wrong.
## Uptime Monitoring
Uptime monitoring is the process of monitoring the availability of your website and servers. Phare will browse your website or server at regular intervals to check if it is online and working as you expect.
[Learn more about uptime monitoring](/uptime/monitors).
<Frame type="glass">
<div style={{position: 'relative', width: '100%', 'padding-top': '56.25%'}}>
<iframe src="https://iframe.mediadelivery.net/embed/238508/d10fb3cf-ec4c-422b-9cf6-03e292942178?autoplay=false&loop=false&muted=false&preload=true&responsive=true" loading="lazy" allow="accelerometer;gyroscope;autoplay;encrypted-media;picture-in-picture;fullscreen" style={{border: 0, position: 'absolute', top: 0, height: '100%', width: '100%'}} />
</div>
</Frame>
## Status pages
Status pages are a simple way to communicate with your users when something goes wrong.
[Learn more about status pages](/uptime/status-pages).
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/uptime/overview/status-page.webp" alt="Status page" />
</Frame>
## Incident Management
Incident management is the process of managing the lifecycle of an incident. Phare Uptime provides a powerful incident management system to manage the lifecycle of an incident, including incident creation, incident updates, incident resolution, and incident escalation.
[Learn more about incident management](/uptime/incident-management).
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/uptime/overview/incident-management-table.webp" alt="Incident management table" />
</Frame>
## Alerting
Alerting is the process of notifying your team members of an incident. Phare Uptime provides a powerful alerting system to notify your team members of an incident, including email, Slack, and Discord with more integrations coming soon.
[Learn more about alerting](/uptime/alerting).
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/uptime/overview/alert-rules-table.webp" alt="Alert rules table" />
</Frame>
# 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 a great way to keep your users in the loop. They are a public page that displays the status of your monitors, and any incidents or maintenance periods that are currently ongoing. Status pages built with Phare are extremely fast and carbon efficient!
<Frame type="glass">
<div style={{position: 'relative', width: '100%', 'padding-top': '56.25%'}}>
<iframe src="https://iframe.mediadelivery.net/embed/238508/dc0fe30e-efbe-4192-a05c-5a0e6c1d5802?autoplay=false&loop=true&muted=true&preload=true&responsive=true" loading="lazy" allow="accelerometer;gyroscope;autoplay;encrypted-media;picture-in-picture;fullscreen" style={{border: 0, position: 'absolute', top: 0, height: '100%', width: '100%'}} />
</div>
</Frame>
## Creating a status page
You can create an unlimited number of status pages for all your projects. Choose which monitoring data you want to display, and customize the look and feel of your status page to match your brand. Allow Phare a few seconds to generate an SSL certificate for your status page, and you're good to go! The status page can be customized at any time.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/uptime/status-pages/status-pages-creation.webp" alt="Status page creation" />
</Frame>
## Phare domain
All status pages possesses a unique `*.status.phare.io` domain name, protected by an SSL certificate.
## Custom domain
You can host your status page on a custom domain. This is a great way to keep your brand consistent across all your services. To set up a custom domain, you need to create a CNAME record in your DNS settings that points to `cname.status.phare.io`.
| Type | Name | Target |
| :---- | :----------------- | :-------------------- |
| CNAME | status.example.com | cname.status.phare.io |
The domain name needs to be configured properly for Phare to generate a valid SSL certificate and activate HTTPS on your status page, which can take a few minutes.
Once your custom domain is verified, the Phare domain (`*.status.phare.io`) associated to your status page will automatically redirect to your custom domain.
### Custom domain with Cloudflare DNS
If you are using Cloudflare DNS, you need create the CNAME with proxy status in `DNS-only` mode (the cloud icon must stay gray and not orange) as shown on the following screenshot:
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/uptime/status-pages/custom-domain-cloudflare.webp" alt="Custom domain on Cloudflare" />
</Frame>
### Custom domain with Bunny.net
Hello there fellow Bunny.net enjoyer!
Because Phare also uses Bunny.net for sub-domain management, an extra security step is required on your end to allow us to generate an SSL certificate. Don't worry though, it's a quick and easy process!
1. Create a TXT record in your DNS settings with the following values, this will allow Bunny.net support to verify that your request is genuine:
| Type | Name | Target |
| :--- | :----------------- | :-------------------- |
| TXT | status.example.com | Bunny Support - Phare |
2. Navigate to your [Bunny.net support hub](https://dash.bunny.net/support/tickets) and open a new support ticket.
3. Select the **DNS** department and write a message similar to the following with the custom domain you want to use:
```text
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!
```
4. Wait a few minutes for the ticket to be processed by one of their great support agents.
5. Once the ticket is resolved, go back to [your status page dashboard](https://app.phare.io/uptime/status-pages) and click the `Verify again` button to activate your custom domain.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/uptime/status-pages/verify-failed-status-page-domain.webp" alt="Verify failed status page domain" />
</Frame>
If you're having trouble with the verification process, please [reach to get support](https://phare.io/contact).
## Status badges
Once your status page is created, you get access to a set of status badges that you can embed on your website or repository. These badges are a great way to show your users that your service is up and running, and can be accessed from your status page's action menu.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/uptime/status-pages/status-badges-menu.webp" alt="Status badges menu" />
</Frame>
### Embed badges
Embed badges are designed to be displayed on your website, and can be customized to match your brand. You can force a light or dark color theme, or let the badge automatically switch based on the user's system preferences. The following parameters are available:
* `align`: Only used for aligning the live status badge. Possible values are `start`, `center`, and `end`.
* `background-light`: Background color used when the badge is in light mode.
* `background-dark`: Background color used when the badge is in dark mode.
* `text-light`: Text color used when the badge is in light mode.
* `text-dark`: Text color used when the badge is in dark mode.
All colors accept hexadecimal values, with the following formats:
* `RGB`: #FFF
* `RGBA`: #FFFF
* `RRGGBB`: #FFFFFF
* `RRGGBBAA`: #FFFFFFFF
If you're not feeling creative, you can use one of the provided style presets.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/uptime/status-pages/embed-status-badge.webp" alt="Embed status badges" />
</Frame>
### Shield badges
Shield badges are the classic status badges to embed in your Git repository. They are designed to be displayed in your README file, and come in all the popular styles. Shield badges are based on the [Shields.io](https://shields.io) service, and [can be customized](https://shields.io/badges/endpoint-badge).
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/uptime/status-pages/shield-status-badge.webp" alt="Shield status badges" />
</Frame>
# User management
Source: https://docs.phare.io/user-management
Learn how to manage your organization’s members and roles.
Phare allows you to invite an unlimited number of team members to your organization and manage their access with roles and project scopes.
<Frame type="glass">
<div style={{position: 'relative', width: '100%', 'padding-top': '56.25%'}}>
<iframe src="https://iframe.mediadelivery.net/embed/238508/a285ada1-2d4a-425a-9ede-690af59694b2?autoplay=false&loop=true&muted=true&preload=true&responsive=true" loading="lazy" allow="accelerometer;gyroscope;autoplay;encrypted-media;picture-in-picture;fullscreen" style={{border: 0, position: 'absolute', top: 0, height: '100%', width: '100%'}} />
</div>
</Frame>
## Roles
Phare has three roles: **Owner**, **Admin**, and **Member**. Each role has a different set of permissions and access to your organization's resources.
* **Owner**: The owner is the creator of the organization. The owner hove the same access right as admin with the addition of deleting the organization and users with the admin role.
* **Admin**: Admins have full access to all the organization's resources. Admin can freely join any project in the organization and promote other users to the admin role.
* **Member**: Members have full access to the projects they are assigned to. They can also create new projects and invite new members to the organization.
## Accessing projects
You can choose which projects a **member** has access to when inviting them to your organization. You can also change a member's access to a project at any time.
**Admin** and **Owner** have the ability to join the projects of their choice. Only joined project will be visible in the project selector to avoid cluttering the interface with projects you don't usually work on. Other projects can still be modified or deleted at any time on the organization's project page, without having to join them.
<Frame type="glass">
<img class="border rounded-lg" src="https://mintlify.s3.us-west-1.amazonaws.com/phare/images/user-management/project-selector.webp" alt="Project selector" />
</Frame>