OnlineOrNot now supports over a hundred external status pages.

You can add their components to your status page, and let your customers know when your dependencies are down.

The full list is here: onlineornot.com/docs/third-p...

The results page for an uptime check now lets you pick:
- number of results per page
- how far back you want to search (24h/7d for now)

and you can share the filter settings through the URL

Neat, @onlineornot.com isn't too far off 10 million checks per week + 3k users

Not bad for the 200th alternative to pingdom

Here's OnlineOrNot's own internal status, for example: api.onlineornot.com/v1/status_pa...

There's a new API endpoint for fetching a summary of a status page - useful if you want to embed your status into your product:

developers.onlineornot.com/api/status-p...

Fixed up a few performance issues in the OnlineOrNot dashboard (N+1 queries for the technical folks), checking out the list of uptime checks, and clicking into an uptime check is now significantly faster

Users can now pick quantile and location for each component on your status page:

(before, we were using average over 5 minutes, meaning an outlier would massively skew the data, making your site look slower than it actually is) (edited)

Oh hey, it's the story of how OnlineOrNot became a thing

I'm just going to leave this here 🥰

a meme of the "this is fine" dog between a try/catch block