Is it down, or is it just you?

When a website or app stops working, there are only a few possibilities: the service itself has a problem, something between you and the service is failing (your Wi-Fi, router, internet provider or a VPN), or the problem is with your device or account. Each status page on this site helps you tell these apart. It shows whether our own checks can reach the service right now, how many people have reported problems in the last hour compared with normal, and the service's recent outage history.

A 60-second checklist

1. Open another website. If nothing loads, the problem is your connection. Our guide to Wi-Fi connected but no internet walks through the fixes.
2. Search the service above. If our checks are failing or reports are well above normal, it's down for other people too and the best fix is to wait.
3. Try another device or network. If the service works on mobile data but not on Wi-Fi, your network is blocking or failing to reach it.
4. Read the error message. Codes such as 502 Bad Gateway, 503 Service Unavailable or DNS_PROBE_FINISHED_NXDOMAIN tell you where the problem is.

Why a service can look up but still not work

Our checks confirm that a service's website answers. Many outages hit only one part of a service, such as logins, the mobile app, payments or one region, while the main website keeps responding. That's why visitor reports matter: if lots of people report the same problem at once, we flag the service as having problems even when its website answers normally. Whenever several services start failing at the same time, often because they share a cloud or network provider, we list it on our incidents page.