The Guardian help and reporting
Subscriber/digital help is different from donating to support the Guardian.
Live Domain Check
Run a live reachability check for theguardian.com. Compare the regional responses with the problem you see in The Guardian.
Find The Guardian help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Guardian articles, its app and paid digital access can fail independently.
The checker above requests theguardian.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual The Guardian action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse streaming and media checks.
Subscriber/digital help is different from donating to support the Guardian.
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
We have not linked a separate status page for this service. Check the official help page for current notices.
Open The Guardian help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Article, digital product, device/app, subscription access route and error/time.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to The Guardian.
These are troubleshooting comparisons, not claims that The Guardian is currently experiencing a particular incident.
Compare a public article with the app or subscription feature that fails.
Use Guardian digital/subscriber help; the donation/support-the-Guardian page is not itself a technical help desk.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when The Guardian seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open theguardian.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader The Guardian issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting The Guardian support.
Run the theguardian.com check and compare its original timestamps and responses with your actual error. Guardian articles, its app and paid digital access can fail independently.
Use the official help/reporting resource linked above. Subscriber/digital help is different from donating to support the Guardian.
Compare a public article with the app or subscription feature that fails. Use Guardian digital/subscriber help; the donation/support-the-Guardian page is not itself a technical help desk.
Article, digital product, device/app, subscription access route and error/time.