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. I assume when most folks ask this that they're looking for the one thing they can do to finally start getting paid customers. Let me be clear: it's never just one thing.

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.

If you don't know what a "cron job" is or how the cron job expression syntax works (and at this point are too afraid to ask), you're in the right place. In this article, we'll dive into what is a cron job, how they work, and the details that often get overlooked, like cron job schedule syntax and common cron job errors.

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

When you're building a serverless web app, it can be pretty easy to forget about the database. You build a backend, send some data to a frontend, write some tests, and it'll scale to infinity with no effort, right? Not quite. Especially not with a tiny Postgres server. As the number of users of your frontend increases, your app will open more and more database connections until the database is unable to accept any more. That's just the frontend - it gets worse on the backend.

Imagine you're sitting in your office, and you start noticing emails coming in asking if you'd like to buy your domain. "Huh, that's weird, I already own that domain" you think to yourself. A few more emails come in, and they're getting past the spam filter, so you decide to double check your domain manager. Doubt starts creeping into your mind, you start panicking, and you frantically scroll down to where the domain should be, and... It's gone.

Ever wonder how to check if a website is still working, without having to load up the website and manually check every few minutes? In this article, we'll go over the various ways to check if a website is online.

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. If this sounds familiar, it's because it's almost a replay of what happened on December 7, 2021, although that outage was significantly more severe and took longer to restore.

A fairly common claim among website uptime monitoring services is that downtime costs $5600 per minute. Chances are, you'll have one of two reactions to this claim: The reality of what downtime costs your business lies somewhere in between. As a company that runs 3.6 million uptime checks per week, we have a bit of insight into the cost of downtime, so if you're curious - read on.

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.