Medium service status
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
Live Domain Check
Run a live reachability check for medium.com. Compare the regional responses with the problem you see in Medium.
Find Medium help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Reading an article, membership access and publishing an editable draft are separate Medium actions.
The checker above requests medium.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Medium action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
Use the correct reading, membership or publishing help topic.
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
Use the correct reading, membership or publishing help topic.
Open Medium 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/draft reference privately, read/publish action, membership route, browser/app 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 Medium.
These are troubleshooting comparisons, not claims that Medium is currently experiencing a particular incident.
Compare another public article with the affected article and preserve a draft before refreshing.
Check sign-in and membership provider for access issues; use Medium Help for a publishing or account problem.
A 403 or 429 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 Medium seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open medium.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 Medium issue.
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Medium support.
Run the medium.com check and compare its original timestamps and responses with your actual error. Reading an article, membership access and publishing an editable draft are separate Medium actions.
Use the official help/reporting resource linked above. Use the correct reading, membership or publishing help topic.
Compare another public article with the affected article and preserve a draft before refreshing. Check sign-in and membership provider for access issues; use Medium Help for a publishing or account problem.
Article/draft reference privately, read/publish action, membership route, browser/app and error time.