OnlineOrNot

Status page tools give customers one place to check whether your service is working, what went wrong, and when they can expect another update.

Atlassian Statuspage is one of the best-known tools for communicating outages and scheduled maintenance.

Last month I focused on adding Telegram alerts to OnlineOrNot, making scripted browser checks generally available, and making it clearer to understand why checks fail.

UptimeRobot is one of the most popular uptime monitoring tools because it is simple, recognizable, and easy to start with.

Pingdom is one of the best-known website monitoring products.

Uptime monitoring tools check your website, API, or app on a schedule and alert you when something stops working.

Synthetic monitoring tools check your websites and APIs before your users do.

Your website is down.

February was all about making OnlineOrNot better for dev teams.

It's 2am.

Cron jobs have a nasty habit of failing silently.

Your API is the backbone of your product.

Hopefully this will be one of the last major "behind-the-scenes" updates for a while, because OnlineOrNot's frontend now runs on a React framework that's easy to deploy across multiple providers, and is fully off GraphQL, being powered by its own REST API.

Continuing on with the tradition I started to wrap up 2024, in this article I'll go over what's new in OnlineOrnot from 2025.

On 2025-11-18 at 11:48 UTC, Cloudflare declared an incident affecting the global network (that also affected OnlineOrNot).

A bit more behind-the-scenes work than usual this month, but I still managed to ship some public-facing features you might be interested in.

In this latest update, I'll walk you through a few features I added that will make working with uptime checks less noisy, an alerts integration with Teams, and a few behind-the-scenes changes that will finally let me build mobile apps for OnlineOrNot.

As OnlineOrNot has grown, I've been building features quickly to get them into your hands as fast as possible.

In April I worked on a behind the scenes refactor, webhooks for status pages, a new endpoint, and more.

Some of your most critical infrastructure runs on AWS EC2, so it's pretty damn important to know when your EC2 instances shut down.

I can't believe it's April already.

When you're part of a small team running a system with thousands of users or more, it can be pretty daunting to think about going on holiday, or even relaxing for a weekend.

curl is one of those programs that feels like its always been there for you in a pinch, like when you're trying to debug what your API is doing, and yet we never take the time to actually learn how to use it (I only ever used it via "copy as curl" from my…

The other day I realized that while I write monthly updates on what's new in OnlineOrNot, and keep the changelog updated, I didn't have a yearly review of what was shipped, and what folks could expect from the coming year - so here we are!

Chances are, you've heard one of the main promises of serverless compute: "you only pay for what you use".

A quieter month this time around: you can now customize your status pages, there are additional overall statuses for status pages, and I fixed a few bugs.

This month I continued adding features to OnlineOrNot's status page functionality, while also taking the time to fix bugs, and add an integration for Pingdom.

If you remember the last update, I originally planned to ship quite a few features in June.

In May I mostly took the time to plan out the rest of the year, as well as one big feature to make OnlineOrNot's incident management more realistic.

In April I kept focusing on making Status Pages better than ever, and added a new on-call integration: incident.io.

March was a fun month for OnlineOrNot.

Incidents are a stressful time for your team: your service isn't working the way you expect and your customers/stakeholders want to know what's going on.

Ever wonder how to check if a website is still working, without having to load up the website and manually check every few minutes?

Over December and January I focused on OnlineOrNot's public API, making it possible to see what OnlineOrNot saw when it detected a failing uptime check, as well as fixing bugs and cleaning up tech debt across all of OnlineOrNot (it's getting faster and fa…

You might be thinking “building HTTP API docs from scratch?

It'll soon be the third anniversary of publicly launching OnlineOrNot on Twitter, and I often get asked what I did to get my first paying customers - so I felt like sharing.

Over October and November I focused on adding new features to Status Pages and making it easier to iterate on new features, as well as fixing bugs across all of OnlineOrNot.

Coming back from August holidays, I felt the need to take a hard look at what OnlineOrNot does, and keep improving it.

Jumping into monitoring software for the first time can be pretty overwhelming.

When you're building a serverless web app, it can be pretty easy to forget about the database.

Chances are, you already know how important it is to keep WordPress and its plugins up to date.

Imagine you're sitting in your office, and you start noticing emails coming in asking if you'd like to buy your domain.

In case you missed it, AWS experienced an outage or "elevated error rates" on their AWS Lambda APIs in the us-east-1 region between 18:52 UTC and 20:15 UTC on June 13, 2023.

A fairly common claim among website uptime monitoring services is that downtime costs $5600 per minute.

It's a warm afternoon here in Toulouse, I feel like it's as good a time as any to update folks about what's new in OnlineOrNot.

You're browsing your favorite website, clicking around, when suddenly, you're rudely interrupted by a white screen, proclaiming: Error 503 Service Unavailable (I don't mean to pick on Varnish cache here, It's just a screenshot I had handy) As a developer,…

Last Saturday, our API went down.

I'm excited to be launching onlineornot - OnlineOrNot's newly-built, open source (TypeScript) CLI for managing your uptime checks, all from the comfort of your terminal!

Two years ago, OnlineOrNot started as a little toy app I built in an afternoon to see what it's like using the Next.js framework, to see if a URL is down from around the world.

It's a story as old as the web itself: someone on your team gets excited to install a new tool.