How we check — our methodology
Two signals decide what you see on this site: automated server checks run by us, and problem reports submitted by visitors. This page explains exactly how both work — and what they cannot tell you.
1. Automated server checks
Our server contacts each service’s official website directly and records the result:
2. User reports
Anyone can report a problem from a service’s status page — website not loading, app not working, login or OTP failing, payment failing, or slow service. Reports are counted per service over the last 24 hours:
A service is flagged on the Reports page when its latest automated check has failed, or when 3 or more users have reported it in the last 24 hours.
3. What we cannot detect
Our check asks one question: does the service’s official website answer? It cannot tell you whether login works, whether a payment will go through, whether an app works on your phone, or whether a problem affects only your city or network. A site can answer our check and still be broken for you — that is exactly what user reports are for.
4. History builds over time
Outage history on this site is built only from checks and reports that actually happened. Automated background checking started on 12 November 2026, so history before that date does not exist here and is not shown. We never invent past outages.
5. What we do not do
We do not copy outage data from other sites, we do not invent reports, and we do not speak for the companies listed here. Status labels describe what our checks and the community observed — for an official statement, always check the service’s own status page or support channels.