Changelog

You can deploy our checker within your infrastructure, any cloud providers or coolify by pulling the image from the container registry.

The image is available at ghcr.io/openstatushq/checker:latest.

It opens up a lot of possibilities to run the checker in your own environment, on your own infrastructure, or on any cloud provider. We will be able to add private locations soon.

We have wrote a guide to help you deploy our checker on Koyeb.

Thanks to Depot for the fast build and the easy integration with GitHub Actions.

We have reworked our status page!

• less flashy colors for operational, degraded, downtime and maintenance
• new sticky navigation bar, merging maintenances and incidents into an events page (your old links will still work)
• redesign of status reports

Sometimes you need to create a copy of your monitor with the same settings quickly and easily.

You can now clone a monitor directly from the action menu in the monitor table.

We have added this feature to the monitor settings.

Shout-out to @Ipriyankrajai for his contribution!

The location of your reports has changed. The can be found within the connected status page. No need to connect manually to a status page.

If you encounter any issues. Please contact us.

Sometimes you need to get notified if your monitor is taking too long to respond or if it's degrading.

You can set custom request timeouts and degradation timing for your monitors.

We have added this feature to the monitor settings.

We've added a PagerDuty integration to the notification feature. This allows you to receive incident alerts through PagerDuty.

We have added more regions to OpenStatus.

You can now monitor your endpoint from 35 regions.

Here is the list of the all our supported regions:

Africa

• Johannesburg, South Africa 🇿🇦

Asia

• Hong Kong, Hong Kong 🇭🇰
• Mumbai, India 🇮🇳
• Singapore, Singapore 🇸🇬
• Tokyo, Japan 🇯🇵

Europe

• Amsterdam, Netherlands 🇳🇱
• Bucharest, Romania 🇷🇴
• Frankfurt, Germany 🇩🇪
• London, United Kingdom 🇬🇧
• Madrid, Spain 🇪🇸
• Paris, France 🇫🇷
• Stockholm, Sweden 🇸🇪
• Warsaw, Poland 🇵🇱

North America

• Ashburn, Virginia, USA 🇺🇸
• Atlanta, Georgia, USA 🇺🇸
• Boston, Massachusetts, USA 🇺🇸
• Chicago, Illinois, USA 🇺🇸
• Dallas, Texas, USA 🇺🇸
• Denver, Colorado, USA 🇺🇸
• Guadalajara, Mexico 🇲🇽
• Los Angeles, California, USA 🇺🇸
• Miami, Florida, USA 🇺🇸
• Montreal, Canada 🇨🇦
• Phoenix, Arizona, USA 🇺🇸
• Queretaro, Mexico 🇲🇽
• Seattle, Washington, USA 🇺🇸
• San Jose, California, USA 🇺🇸
• Toronto, Canada 🇨🇦

South America

• Bogota, Colombia 🇨🇴
• Buenos Aires, Argentina 🇦🇷
• Rio de Janeiro, Brazil 🇧🇷
• Sao Paulo, Brazil 🇧🇷
• Santiago, Chile 🇨🇱

Oceania

• Sydney, Australia 🇦🇺

Let's make synthetic monitoring more global! 🌐

We have added a new API to launch a check with OpenStatus. You can now test your endpoint's latency programmatically.

It's useful if you want to integrate OpenStatus with your CI/CD pipeline.

You can read the API documentation.

You can now set your status to Under Maintenance to inform your users that you're performing maintenance. You'll be able to set the start and end times for the maintenance period. During this time, we will pause the connected monitors and suppress any notifications.

To create a maintenance, go to the corresponding status page and click the 'Maintenance' sub navigation. From there, you can create a new maintenance status, including title and description.

The users will be able to see all maintenances under a new tab on the status page.

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.