Measured every minute
The real status of the services you depend on
Measured per component by our own monitors, next to what each company's status page said. Last 90 days.
– up – slow – down Reading the latest checks…
All services
Our live feed could not be reached. The numbers refresh on their own once it is back.
How we measure
The same monitors that power our "Is it down?" pages, split by component.
-
1
Per component, not per company
Each service is split into the parts people use: websites, apps and APIs. A failing marketing site never makes the API look down. APIs are called without credentials, so an answer such as 401 Unauthorized proves the API is up.
-
2
Every minute, re-checked from other continents
Every component is requested every minute by the same UptimeTea monitors that power the "Is it down?" pages. A failed check is repeated from Frankfurt and Singapore. If either reaches the service, the failure was our network's problem and never counts.
-
3
Three failed minutes before it is an outage
An outage starts when three checks in a row fail everywhere and ends at the first successful check. Two monitors of the same component failing together count as one outage.
-
4
Matched to their status page, component by component
We copy each vendor's incident history every 10 minutes. An outage counts as reported when an incident naming the same component overlaps it in time. Outages under 5 minutes are never counted as missing from their status page.
-
5
Some components have no official counterpart
When a vendor lists no matching component, or publishes no incident feed at all, you see our measurements only and the component is left out of the comparison.
Know before your customers do
Watch your own site and API with the same one-minute monitors. 50 monitors free, no credit card.