Why we built it

Most website owners don't need a complex observability platform. They need to know, reliably, when their website stops working, and they need a clear record of how it behaved over time. UptimeStats exists to do exactly that, with a free plan that is genuinely useful rather than a short trial.

How our checks work

Every monitored website is checked from our server every 5 minutes with an HTTP GET request identified by the User-Agent UptimeStatsBot/1.0. We follow up to 5 redirects, read only the response headers and a small part of the page, and record the HTTP status code, the response time and, when something fails, the reason.

How UptimeStats works in four steps: add your website, it is checked every 5 minutes, a failed check is confirmed about a minute later, and you get one alert when it is down and one when it is back. How UptimeStats works in four steps: add your website, it is checked every 5 minutes, a failed check is confirmed about a minute later, and you get one alert when it is down and one when it is back.
How UptimeStats works, from adding a website to receiving an alert.

Before declaring an outage we run a confirmation check about a minute later. This keeps one-off network problems from turning into false alarms. You can read the exact rules on our features page.

Checks currently run from a single location. If your website blocks traffic from certain regions or from data centres, our results may differ from what some visitors see. Multi-region monitoring is planned for a future Business plan.

Our principles

  • Real data only. Your dashboard shows results from actual checks of your website. If we haven't checked it yet, we say so.
  • No exaggerated claims. Features that aren't available yet are labelled as planned.
  • Minimal data. We ask for an email address and the websites you want to monitor. That's it.
  • Respect for your servers. One lightweight request every 5 minutes, never a full page download.
  • Security first. Our checker refuses to contact private or internal network addresses, so it can't be misused to probe internal systems.

Who writes our articles

Articles are written and reviewed by the UptimeStats editorial team. We aim for technically accurate, practical explanations and link to primary sources such as RFCs and official documentation where it helps.

Get in touch

Questions, feedback or a bug to report? Send us a message. We read everything.

Start monitoring in under a minute

Free for up to 5 websites.