To check whether a website or app is down, open its official status page, try an unrelated site, and test the affected service on another browser or connection. If several devices fail and the provider reports an incident affecting that feature, waiting for recovery usually makes more sense than reinstalling the app.
A page that will not load on your phone does not necessarily mean the whole service is offline. The problem can affect one account, region, network, or feature. This guide helps you narrow that down; it is not a live outage monitor.
Five checks to make first
- Test an unrelated website. If nothing loads, check your connection before investigating one app.
- Check the provider’s official status page. Match the reported feature and incident time to your problem.
- Try the service in another browser or its official app. A working alternative can help you finish the task and identify a browser-specific issue.
- Try another trusted connection. For example, use mobile data instead of Wi-Fi, keeping data charges in mind.
- Compare recent reports. Look for the same symptom at the same time, not merely complaints containing the service’s name.
Before repeating a payment, reservation, or important submission, check whether the original attempt completed. An error screen can appear after a request reached the server.
Where to find official service status
Open a status link from the provider’s own help center when possible. The following are official starting points, not statements that those services are down now.
| Service | Official status page | What to match |
|---|---|---|
| Apple services | Apple System Status | The individual service, such as iCloud or the App Store |
| Google Cloud | Google Cloud Service Health | The Cloud product and location; this does not cover every consumer Google app |
| PlayStation | PlayStation Network status | Account, store, gaming, or other network functions named in the incident |
Check the timestamp as well as the colored indicator. A resolved incident from yesterday does not explain every failure today. A provider may also report degraded performance while most of its site remains accessible.
Google Cloud notes that some issues may not appear on its public dashboard and points customers to support or personalized service health. An all-clear public dashboard does not diagnose your individual account.
Is the problem on your side or the service’s side?
| What you observe | What it suggests | Next step |
|---|---|---|
| Several unrelated sites fail on the same Wi-Fi | A connection or network problem is plausible. | Test another connection and check your router or network provider. |
| The website works in another browser | Browser data, settings, or an extension may be involved. | Save your work, then test browser settings one change at a time. |
| The website works but the mobile app crashes | An app-specific problem is more likely than a complete outage. | Follow the app-not-working checklist. |
| The home page works but login fails | The account or authentication service may be affected separately. | Check the status of sign-in, not just the home page. |
| Multiple devices fail and an official incident matches | There is stronger evidence of a service-side problem. | Follow the incident updates and avoid unnecessary resets. |
These are clues, not proof from a single test. Another device on the same Wi-Fi does not rule out a network issue because both devices use that connection.
What error messages can tell you
An HTTP 404 means a requested resource was not found, not that the entire website is down. HTTP 500 indicates a server error; 503 means the service cannot handle the request at that time. Either may affect only part of a site.
A 429 response means too many requests have hit a limit. Repeated refreshing can prolong the problem. If a retry time is supplied, wait until then. For definitions and examples, see what error codes mean and MDN’s HTTP status reference.
A browser connection or DNS error is different: you may not have received an HTTP response from the site at all. Save the exact message so you do not follow instructions for the wrong failure.
How much should you trust user reports?
A sudden group of similar reports can be useful when a provider has not posted an update yet. Check when the reports were made, which region or feature they describe, and whether they come from independent people.
One copied screenshot can appear in many posts. An old incident can also resurface during an unrelated problem. Report volume cannot establish whether your own account is affected or when service will return.
Do not enter your password into an unfamiliar “outage checker.” You should be able to read a public incident report without handing an unrelated site your credentials.
When to wait, troubleshoot, or contact support
Wait when an official incident matches your issue. Use an existing alternative, such as a working official web app, only after checking that the original action did not already complete.
Troubleshoot locally when the issue is isolated to one browser, device, or network. Start with reopening the affected software and checking official updates. Avoid deleting stored data as a first experiment.
Contact support when an account-specific failure persists or you cannot confirm the outcome of an important action. Provide the time, time zone, error, affected feature, and connection-test results.
FAQ
How do I know if an app is down for everyone?
You usually cannot prove “everyone” from a few reports. Look for a provider-confirmed incident and whether it affects your feature or region, then compare behavior across devices and connections.
Can a status page say everything is fine while the app fails?
Yes. Public dashboards can lag behind a new incident or omit account-specific and localized problems. Keep the exact error and contact support if it persists.
Is the website down if its home page loads but I cannot log in?
It may have a partial outage. Sign-in, checkout, search, and other features can fail independently of the home page.
Should I reset my password during an outage?
A routine outage is not a reason to reset a password. Follow the official account-recovery process if there is evidence of an account problem or a security notice.
Can a VPN or work network cause the problem?
Yes. Network rules or routing can affect access. On a managed device, ask your administrator before changing required VPN, proxy, or security settings.
Does this page report live outages?
No. It explains how to check a service and links to official status sources. Read the provider’s current incident report for live information.