About isuptime

When something stops working, the first thing you need to know is whether the problem is yours. A failed deploy, a hanging API call and a broken laptop all feel identical from your side of the screen. The answer usually exists — it is sitting on the provider's own status page — but finding it means remembering which of forty status pages to open, and opening them one at a time while you are already firefighting.

isuptime reads all of those pages continuously so that the answer is one page load away instead of forty.

Every status shown here is read from the provider's own public status feed — usually the JSON API that sits behind their status page. isuptime does not test the services itself, does not run synthetic transactions against them, and does not guess. If GitHub says it is degraded, isuptime says degraded. If GitHub says nothing, isuptime says operational.

That is a deliberate limit, and it is worth understanding, because it is the main way a status aggregator can mislead you. Providers write their own status pages. A service can be visibly broken for an hour before its status page acknowledges it, and some incidents are never posted at all. A green dot here means the provider is not currently reporting a problem — not that the service is definitely fine.

A scheduled job checks every service on a fixed interval and records the result. That detail matters more than it sounds. The obvious way to build this is to check the services whenever somebody loads the page — but then the uptime figure measures the hours when people happened to be looking, and a quiet night leaves a hole in the data that reads as “nothing happened” rather than “everything was fine”. Checks run on a schedule, whether or not anyone is watching.

The figure is then the share of those checks where the provider was not reporting an outage, over a rolling 30-day window. It is labelled “No outage reported” rather than uptime, deliberately: uptime normally means the fraction of time a service actually worked, and that is not something you can derive from reading a status page. A check where the provider reported degraded performance counts as no-outage — the service was working, just worse. When a provider's status feed cannot be read at all, that check is discarded rather than counted as a failure, since a feed we could not fetch is not evidence about the service behind it.

It also cannot be compared between providers. Because degraded counts as no-outage, only a provider's most severe state costs it anything, and every status platform draws that line somewhere different — Slack registers only on a critical incident, Google only when it posts a public one. The number is a record of how often one provider admitted to a serious problem. Read it against that provider over time, not against another.

Two consequences worth knowing. A service can show 100% here while having had a bad week, because a month of degraded performance is not an outage. And a provider that leaves a genuine outage open for weeks — some do, for a single region — will show a low figure for as long as it stays open.

The full method — which feed each provider publishes, how eleven formats become four states, and why an amber indicator is not taken at face value — is written up in how isuptime works.

• Check any single service on its own page, such as is GitHub down or is OpenAI down.
• Watch all 102 services at once, with anything broken sorted to the top.
• Get alerted when something breaks, via browser notifications or a Discord, Slack or Telegram webhook. Alert settings live in your browser — there is no account.
• Read the data programmatically. The same JSON that powers this site is public at /api/status.

All product names, logos and brands shown on isuptime are the property of their respective owners. They are used here for one purpose only: to identify the service whose status is being reported, so you can tell at a glance which provider a row belongs to. Their use does not imply any affiliation with, endorsement by, or sponsorship from the companies concerned — isuptime has no relationship with any of them.

The marks themselves are drawn from Simple Icons and the SVG Logos collection, both of which release their artwork under CC0. That covers the artwork; it does not affect anyone's trademark rights, and nothing here is claimed to.

If you represent one of these companies and would prefer your mark not appear, it will be removed on request — the site is built so that a logo can be dropped without breaking anything, and no argument will be made about it. Please get in touch.

isuptime is an independent project, not affiliated with any of the services it monitors. It is free to use and requires no account. If something looks wrong — a service reporting incorrectly, a provider worth adding — please get in touch.