What's new in OnlineOrNot

March 14, 2023 - Announcing multi-location, and geo-specific monitoring

OnlineOrNot now lets you decide where we should run your check from.

To start with, we support:

• US East
• US West
• Europe
• Australia
• Japan

You can pick all of these locations, or just one - it's up to you!

March 6, 2023 - Uptime Checks every 30 seconds

All paid customers of OnlineOrNot now have access to uptime checks every 30 seconds.

This is particularly useful if you want to know if your website, web app, or API is down really fast, or to catch sub-minute outages.

March 1, 2023 - Public API and CLI

You can now check on your uptime checks from the comfort of your own terminal, thanks to our newly released open-source CLI.

On top of that, you can also write your own code to add and remove checks, and double check your uptime checks via the API.

For information on how to set it up, see our CLI documentation and API documentation.

August 23, 2022 - Private Status Pages

You can now keep your status pages private by setting a password on them.

This is useful if you want to share your status page with your team, but don't want to share it with the public.

For more information, as well as instructions on how to set it up, see our documentation.

March 21, 2022 - SMS via Twilio

You can now bring your Twilio account to OnlineOrNot, and receive unlimited SMS alerts when things go wrong!

For more information, check out the docs.

February 28, 2022 - SSL verification

OnlineOrNot now supports SSL verification!

If while doing a routine check, OnlineOrNot notices that your website's SSL certificate is no longer valid, we'll let you know as per your alert settings.

February 2, 2022 - Alert after several failed checks

The internet can be a pretty flaky place, and sometimes you only want to be notified if a check has failed several times sequentially.

OnlineOrNot now lets all users delay their alerts until they've been failing several times in a row (this feature used to be only for customers on paid plans).

January 5, 2022 - Uptime Checks on the go

Sometimes you just want to see how your sites are doing at a glance.

OnlineOrNot now has first-class support for mobile in its web app, having redesigned the main dashboard to make it easier to see all your checks at a glance.

December 14, 2021 - Everyone can invite their team!

It's pretty common for monitoring to fall to a single person, and OnlineOrNot wants that to change. Keeping your business running is your whole team's job, not just one person.

As of today, all of our plans allow you to invite your team mates.

November 29, 2021 - Assertions

Monitoring that your website or API is still running is great and all, but there's no guarantee that the data coming back is correct.

A few weeks ago with the release of our API Monitoring feature, we promised a way to run more advanced correctness checks.

Today we're releasing Assertions - a way to check that your API is responding the way you expect it to.

November 16, 2021 - API Monitoring

Before today, OnlineOrNot had only basic API monitoring support: you could monitor your API endpoint with GET requests.

Today we're launching our API Monitoring support with the following features:

• Setting HTTP request method (GET, POST, etc)
• Setting HTTP request body
• Setting HTTP request custom headers
• Following redirects

In the coming weeks you'll also be able to make requests with HTTP Authorization, verify HTTP status codes, and perform more advanced correctness checks.

October 21, 2021 - Uptime and Browser Checks, Around the World

OnlineOrNot's Uptime and Browser Checks have always automatically checked around the world before alerting you that your website is down. However, unless you were a paying customer, the first check would come from Virginia, USA by default.

(This lead to some interesting false-positives for those of us with clients that geo-block certain regions from visiting their sites!)

As of today, you can now pick which one of our supported regions OnlineOrNot monitors from, on all new and existing Uptime and Browser Checks!

October 4, 2021 - Discord Alerts

Not a fan of Slack? If your team is using Discord, as of today you can send all of your notifications to a channel in Discord.

Head over to the Docs for more details, or skip the details and add the Discord integration to your OnlineOrNot account.

August 19, 2021 - Alert Priority and Pausing checks

When you're running scheduled maintenance, the last thing you need is a noisy uptime check spamming your team.

OnlineOrNot now provides you with two more ways to control your alerting.

1. Alert Priority - define your alerts as either High priority, or Low priority. When low priority uptime checks fail, you'll receive fewer alerts. For more information, check out the docs.
2. Pausing Checks - completely stop your uptime checks from running, anytime you want. Particularly useful for when you know your page will flip/flop while recovering from maintenance, and you don't want to be alerted. For more information, check out the docs.

June 22, 2021 - Browser Checks

Tired of looking for uptime checks for your client-rendered web app, and winding up disappointed that client-side rendered apps (using React, Vue, or Angular) aren't supported?

As of today, OnlineOrNot supports running Google's Puppeteer to drive a browser that checks your web app is working as expected.

Check out our pricing to see plan inclusions.

May 28, 2021 - Webhook Alerts

Webhook Alerts are here! Users on paid plans can now receive JSON, to any provided URL for incidents.

For more details, including sample JSON, see the docs.

May 11, 2021 - SMS Alerts

SMS Alerts are here! Users on paid plans are now able to receive SMS alerts for incidents.

Particularly handy for when you mute Slack and Email notifications overnight, but still want an alert to wake you up if things go wrong.

Mar 28, 2021 - Weekly uptime report

For easier reporting, OnlineOrNot now sends a weekly email every Monday at midnight UTC with a summary of your pages' uptime percentage, downtime (in minutes), and number of incidents.