Changelog

You can now sort your monitors by importance on your status page. This allows you to prioritize the most important monitors and show them at the top of your status page.

Powered by sortable.sadmn.com.

You can now protect your status page with a password. This will hide the page from the public and only allow access to users with the password.

You can enable the password protection from the status page within the Visibility settings. You will be able to:

• Enable the feature with a simple checkbox to easily turn it on and off
• Set your password
• Share the protected page with a ?authorize=your-password query parameter to auto-complete the password field

This feature is available on the Starter plan and above.

We have added a new feature to embed the status of your service everywhere.

Just copy the following code and paste it into your website or GitHub README:

<img src="https://YOUR-SLUG.openstatus.dev/badge" />

<img src="https://YOUR-SLUG.openstatus.dev/badge" />

And it will look like this:

You can now change the monitors visibility to public. This will allow you to share the monitor's metrics (the overview page) with your users. The period is restricted to 1d and 7d for now.

The monitor can be accessed either by the public URL or/and by embedding the monitor within a status page.

• Public URL: openstatus.dev/public/monitors/1
• Status Page URL: status.openstatus.dev/monitors/1

You can enable public mode from the monitor Danger section setting.

We want to provide you with as much context as possible when an incident occurs. That's why we've added website screenshots to incidents.

When creating an incident, we capture a website screenshot for added context. We also take a screenshot upon resolving the incident to see the website post-resolution.

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!