Sydney, Australia
Jan 14, 2022   |  By Max Rozen
Imagine you're having a regular day at work, opening up your browser, double checking something for a client in that web app your team built for them, when suddenly, you see this screen: You hit refresh a few times, just to be sure. Nope. Still down. What happens next depends on how well your team has planned for incidents like this (some folks call it unplanned downtime).
Dec 8, 2021   |  By Max Rozen / December 08, 2021
In case you missed it, for several hours on December 7, 2021, AWS's us-east-1 region had an outage impacting multiple AWS APIs, taking out various websites across the internet. According to our own monitoring at OnlineOrNot, the outage started at 2021-12-07 15:32 UTC and began to recover well at 2021-12-07 22:48 UTC (with minor signs of life for a few minutes around 2021-12-07 20:08 UTC). Had we relied solely on AWS to update their status page before reacting, we would have been waiting a while.
Dec 1, 2021   |  By Max Rozen
Say you've been tasked with monitoring an application, so you set up some alerts to let you know when errors are coming in. The minutes roll by, the errors start coming... ...and they don't stop coming... Oh my, there seems to be quite a few errors coming through. Alerting on each error isn't going to help, better report on changes in the error rate instead right? Not quite.
Nov 18, 2021   |  By Max Rozen / November 18, 2021
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 Postgres. 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. It gets worse.
Nov 2, 2021   |  By Max Rozen / November 02, 2021
September and October were relatively quiet, so I thought I would write a single article for both months. While I'd normally try to write at least one useful article per month for OnlineOrNot's audience (as well as an update on how the business is going), I wrote no articles, and no code, actually. Instead, I packed up my life in Sydney, Australia, escaped lockdown, and relocated to France with my wife, and just enjoyed living for a while.
Aug 24, 2021   |  By Max Rozen @RozenMD
A few weeks before I sat down to write this article, I reshared my two month review of OnlineOrNot around the internet. Surprisingly, the article was quite popular: So I thought I'd clear up some confusion for the folks who only just read my two month review: I started OnlineOrNot on February 25, 2021, shipped the first version for people to use on March 2, 2021, and here I am in August writing the six month review.
Aug 10, 2021   |  By Max Rozen
Your engineers probably dislike going on-call for your services. Some might even dread it. It doesn't have to be this way. With a few changes to how your team runs on-call, and deals with recurring alerts, you might find your team starting to enjoy it (as unimaginable as that sounds). I wrote this article as a follow-up to Getting over on-call anxiety.
Jul 26, 2021   |  By Max Rozen
You've joined a company, or worked there a little while, and you've just now realised that you'll have to do on-call. You feel like you don't know much about how everything fits together, how are you supposed to fix it at 2am when you get paged? So you're a little nervous. Understandable. Here are a few tips to help you become less nervous.
Jul 12, 2021   |  By Max Rozen
Like all good things in infrastructure, picking whether or not to self-host your database is full of trade-offs. On the one hand, you have the absolute freedom to do whatever it is you want with your database - whether it's adding a useful Postgres extension, or experimenting with new technologies. On the other hand, you now have to dedicate resources to keeping your database reliably online.
Jun 9, 2021   |  By Max Rozen
In case you missed it, for about 15 minutes on June 8, 2021, Fastly's CDN had an outage, taking some of the internet's largest websites down (including the BBC, UK government, Reddit, and the New York Times - also had its CSS fail to load).

OnlineOrNot monitors your website, letting you know instantly if anything goes wrong.

OnlineOrNot is an website monitoring service. In particular, it monitors whether your site is online, or not (hence the name). It allows you to continuously monitor any website or API server. It notifies you instantly in the case of any problems - whether that's a timeout, 4xx error, or 5xx error.

Monitor With Confidence:

  • Configurable Alerts: You don't want alerts for sites that aren't really down for everyone. Configure retries, and how many minutes of downtime to wait before sending an alert.
  • Fast Alerts: Getting alerts ages after your site goes down isn't great. We use email deliverability best-practices so your alerts get delivered, fast.
  • Alerts where you need them: Get notified when your site goes down, and when it comes back via Email and Slack. Alerts via SMS and phone call coming soon!
  • Text Search: Want to detect when your page stops showing certain text? OnlineOrNot can search your page for text to catch error pages that don't send error codes.
  • Global Monitoring: Monitor from any one of 10 major cities around the world. Check out our supported regions.
  • Bring the whole team: Monitoring is your whole team's job, not the responsibility of just one person. Bring your whole team at no extra cost.

Everything you need to be sure that your website is running smoothly.