Browser checks for your critical pages

Your server might be responding, but can your customers actually load your page? OnlineOrNot's Browser Checks verify that your most business-critical pages still work.

OnlineOrNot's browser check dashboard view containing charts of page response time


Real Browsers

Browser Checks are run in real Chrome browsers, isolated from each other for extra security.

Verified Alerts

Each failed check gets retried, and re-checked in separate regions before sending you an alert.

Alerts where you need them

Get notified when your check starts failing and when it works again via SMS, Email, Slack, and Webhooks.

Text Search

Search your page for text to catch blank pages that don't display obvious errors (such as React, Vue and Angular apps)

Global Monitoring

Monitor from any one of 18 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.

What others are saying about OnlineOrNot

  • I'm using @Online_Or_Not to monitor my @cloakist customers' sites, so I can respond quickly if they stop working Love it. Super clean interface, very intuitive. Particularly impressed at how it can wait for full page load Thanks @RozenMD for making this awesome tool!
  • I just set up some site aliveness checks for @Archium_io with @RozenMD's Took me less than five minutes and it was completely self-explanatory, not to mention gorgeous. Seriously good experience. Great job, Max! 👏👏

Last week kept us busy

With plenty of room for more pages to check, incidents to catch, and notifications to send

Pages checked
Incidents caught
Notifications sent

Cool screenshot, but what does this actually do?

Let me provide a bit of context: OnlineOrNot builds website monitoring tools - the first of which was a simple* uptime checker.

After running a few million checks, my customers started asking why I didn't support Single Page Applications (SPAs) like React - and the answer was pretty simple: the basic uptime checker just fetched the page, it didn't render anything.

OnlineOrNot's Browser Checks feature is how we solve that problem - by plugging Google's Puppeteer and real Chrome browsers into OnlineOrNot's existing uptime monitoring service, you can now reliably check whether your React (or Vue, or Angular, or whatever comes next) apps successfully render, and display the text you expect.

So you run Puppeteer in the cloud... can you run my Puppeteer scripts for me?


My aim for this Browser Checks feature is to allow Puppeteer test scripts to be added, and have the service send you screenshots of your app when things go wrong.

To start with however, Browser Checks currently supports:

  • Loading your web app
  • Searching for text on the page
  • Retrying, and waiting for several failed checks before alerting
  • Sending alerts to Email, Slack, SMS, and Webhooks when things go wrong

*Turns out running millions of uptime checks per week isn't as simple as you'd think!

Have questions? Ready to get going? Let's go:

No time limit, and no credit card required.

The average cost of downtime for smaller businesses is around $137 to $427 per minute. For larger companies this rises to $5600 per minute, according to a 2014 study by Gartner.

While it's easier than ever to build websites and web apps, it's harder than ever to be sure they stay online.

Most teams struggle with two challenges when it comes to monitoring:

  • Noisy, irrelevant alerts (so they miss important ones)
  • Their tools are so slow and difficult to use that the team gives up on them

That's why I built OnlineOrNot — to make uptime monitoring better for teams.

Over the last 9 months we've checked over 45.4 million pages (like yours). I'd love you to give it a try.

Max Rozen, creator of OnlineOrNot
Max Rozen
Founder of OnlineOrNot