outages.live
Live
TwitchIncident · 2026-08-27 20:09 UTC

Service Negatively Impacted

ResolvedOfficial update

🛠 We have resolved all known negative service impacts.

The latest update from Twitch.

State

Resolved

Started

66 d ago

2026-08-27 20:09 UTC

Lasted

6 h 22 min

until 2026-08-28 02:31 UTC

Worst impact

Major outage

Timeline

3 updates
20:0921:4523:2000:5602:31
Major outageUpdate postedTimes in UTC

Investigating

1 h 54 min 30%

Monitoring

4 h 28 min 70%

Updates

Times in UTC

As posted by Twitch

Resolved2026-08-28 02:31 UTC

🛠 We have resolved all known negative service impacts.

Monitoring2026-08-27 22:03 UTC

A fix has been implemented and we are monitoring the results.

Investigating2026-08-27 20:09 UTC

We have received reports of impacted services. This could manifest in chat not working, login difficulties, search impaired, etc. We're looking into the issue.

Affected components

3
WebChatVideo (Watching)

Twitch in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

5

Median duration

1 h 42 min

This incident

3.8× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 h 22 min
median 1 h 42 min
90 days agoToday

Other Twitch incidents

All incidents

Twitch·Identified Emotes Issues

This incident has been resolved.

Resolvedresolved 11 d ago

Twitch·Identified Checkout Issues

🛠 We have resolved all known issues causing some users to be unable to checkout.

Resolvedresolved 46 d ago

Twitch·Watch Streak/Channel Points downtime

We've fixed an issue where watching streams/VODs during did not extend watch streaks or award Channel Points

Resolvedresolved 59 d ago

Follow Twitch

Your coding agent knows when Twitch is down, and tells you when a failure is theirs, not yours. You can also get Twitch incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "twitch" and tell me if Twitch has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=twitch
Slack
/feed subscribe https://outages.cc/feed.xml?providers=twitch

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane