Twitch service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for twitch.tv. Compare the regional responses with the problem you see in Twitch.
Find Twitch help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Twitch viewing, chat, creator broadcasts and ingest connections can fail independently.
The checker above requests twitch.tv from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Twitch action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse streaming and media checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Choose viewer or broadcaster support and never include a stream key.
Open the website in your browser and compare it with the result above.
Open Twitch help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Channel, viewer/creator role, player/encoder, error and UTC time without stream keys.
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 Twitch.
These are troubleshooting comparisons, not claims that Twitch is currently experiencing a particular incident.
Compare another channel and distinguish a viewer playback error from a creator streaming/ingest failure.
Check the relevant Twitch Status component and use viewer or broadcaster support as appropriate.
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 Twitch seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open twitch.tv 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 Twitch 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 Twitch support.
Run the twitch.tv check and compare its original timestamps and responses with your actual error. Twitch viewing, chat, creator broadcasts and ingest connections can fail independently.
Use the community buttons on this page to share whether the service works for you. For help from Twitch, use the official help/reporting resource linked above. Choose viewer or broadcaster support and never include a stream key.
Compare another channel and distinguish a viewer playback error from a creator streaming/ingest failure. Check the relevant Twitch Status component and use viewer or broadcaster support as appropriate.
Channel, viewer/creator role, player/encoder, error and UTC time without stream keys.