Twitch status history

Current state: operational — “All Systems Operational” per https://status.twitch.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

2incidents, last 30 days

2incidents, last 90 days

3incidents on record

Incidents per week, last 12 weeks:

Get Twitch alerts in your Slack — free template RSS for Twitch

How long do Twitch incidents last?

52 minmedian incident duration3 measured

6.3 h90th percentile1 in 10 ran longer

6.3 hmedian, major/critical only1 incident

From 3 incidents with a vendor-posted start and resolve time. Longest on record: Service Negatively Impacted — 6.3 h (2026-08-27 20:09 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (3)

Started	Incident	Status	Impact	Duration
2026-09-03 15:00 UTC	Watch Streak/Channel Points downtime	resolved	none	0 min
2026-08-27 20:09 UTC	Service Negatively Impacted	resolved	critical	6 h 21 min
2026-03-31 18:09 UTC	Identified Checkout Issues	resolved	none	52 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Twitch with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "twitch"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}