Changelog

Not all requests should return a 200 status code to be successful. Sometimes you want to assert on the status code of a request. For example, you might want to check that a request returns a 404 status code when a resource is not found.

You can now do this with OpenStatus when you configure your monitor.

You can now create tags for your monitors to easily categorize them. Tags can be used to filter monitors on the dashboard and in the monitor list.

Create, update or delete a tag via your monitor settings.

When visiting your status page section, you will find a list displaying all individuals who have subscribed to receive updates from your status page.

This feature enables you to easily identify and manage the subscribers who are following your page for notifications and alerts regarding updates on your services.

We have added auto-resolved incidents to the incident management feature. Now, once your endpoint is back up and running i.e. more than 50% of the regions are not failing, the incident will be automatically resolved. The time between the creation and resolution of the incident will be marked as downtime on the status page.

Additionally, the calculated p95 latency over a day has been removed. It is costly to calculate and was not providing much value.

Instead, we are thinking of adding a chart that shows the latency of the last X days/hours. If you have ideas, let us know!

You can now see more insights into your services with the new metrics card on the monitor's overview.

Choose a period and see the: uptime percentage, number of errors, number of total requests, average, p99, p95, p90, and p75 response times - and compare the metrics with the previous period.

You'll also notice that you can now filter the charts by region and combine or split the regions separately for simpler comparison.

Additionally, we've updated the monitor settings section to improve the UI/UX.

So go to your dashboard to check it out!

We are excited to announce the release of the Terraform provider for OpenStatus. This provider allows you to manage your Grafana Cloud resources using Terraform, enabling you to define and manage your OpenStatus resources as code.

Here's the link to the: OpenStats Terraform Provider

You can now test your API or website from multiple regions around the world and experience the performance of your application from the different continents.

Learn more about dns, tls, ttfb and more metrics that are collected by the checker.

Go to the Playground to test your endpoint.

But there is more: use the https://checker.openstatus.dev/ping API endpoint to get the metrics by yourself.

For example:

curl --request POST \
  --url https://checker.openstatus.dev/ping/ams \
  --header 'Content-Type: application/json' \
  --header 'x-openstatus-key: <YOUR_API_KEY>' \
  --header 'prefer-fly-region: ams' \
  --data '{
  "url": "https://api.openstatus.dev/ping",
  "method": "GET"
}'

curl --request POST \
  --url https://checker.openstatus.dev/ping/ams \
  --header 'Content-Type: application/json' \
  --header 'x-openstatus-key: <YOUR_API_KEY>' \
  --header 'prefer-fly-region: ams' \
  --data '{
  "url": "https://api.openstatus.dev/ping",
  "method": "GET"
}'

Read more about the Checker API in our docs.

You can now refine your latency data more effectively with quantiles: p99, p95, p90, and p75. The average (avg) has been retained.

The <Tracker /> data on your status pages now displays the p95 quantile instead of the average.

Furthermore, the /monitors layout has been updated. The data table has its dedicated tab to prevent loading excessive data at once, along with the edit form. The pause button is also now more quickly accessible.

Every created status report now has its own page. That will make it easier to share the status report with your team and across your users.

Additionally, we've addded a neutral blue color to the tracker whenever a status report has been published.

You can now subscribe to pro plan status updates via email.

As a subscriber, we require you to verify your email address to avoid spam. You can do this by clicking the link in the email we send you after you subscribe.