Skip to content

Outage tracker / Twitch

Is Twitch down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Twitch from all 10 regions we check.

As of Sep 23, 2026, 9:09 AM UTC, Twitch answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Twitch (since Aug 8, 2026).

our independent probeslive · checked Sep 23, 2026, 9:09 AM UTC
US-East344 msOperational
US-West62 msOperational
Europe206 msOperational
Asia-Pacific438 msOperational
US-Central452 msOperational
Canada411 msOperational
UK416 msOperational
Southeast Asia2021 msOperational
Australia252 msOperational
South America386 msOperational
their status pagetheir claim, not our reading

Twitch reports: All systems operational (“All Systems Operational”)

from Twitch's own status page, checked Sep 23, 2026, 8:51 AM UTC
Our probes and Twitch's own status page agree: both show Twitch as reachable right now.

Twitch's own component breakdown, as they publish it

  • LoginOperational
  • WebOperational
  • ChatOperational
  • Video (Watching)Operational
  • Video (Broadcasting)Operational
  • PurchasesOperational

These are Twitch's components, named and scored by Twitch. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Twitch's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Twitch response time, by region

US-East
570msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 714ms2026-08-26 UTC: p95 612ms2026-08-27 UTC: p95 617ms2026-08-28 UTC: p95 561ms2026-08-29 UTC: p95 709ms2026-08-30 UTC: p95 584ms2026-08-31 UTC: p95 700ms2026-09-01 UTC: p95 698ms2026-09-02 UTC: p95 595ms2026-09-03 UTC: p95 528ms2026-09-04 UTC: p95 464ms2026-09-05 UTC: p95 570ms2026-09-06 UTC: p95 427ms2026-09-07 UTC: p95 383ms2026-09-08 UTC: p95 400ms2026-09-09 UTC: p95 367ms2026-09-10 UTC: p95 348ms2026-09-11 UTC: p95 389ms2026-09-12 UTC: p95 401ms2026-09-13 UTC: p95 378ms2026-09-14 UTC: p95 366ms2026-09-15 UTC: p95 432ms2026-09-16 UTC: p95 480ms2026-09-17 UTC: p95 490ms2026-09-18 UTC: p95 674ms2026-09-19 UTC: p95 467ms2026-09-20 UTC: p95 482ms2026-09-21 UTC: p95 396ms2026-09-22 UTC: p95 419ms2026-09-23 UTC: p95 570ms
Aug 25Sep 8Sep 23
US-West
244msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 500ms2026-08-26 UTC: p95 453ms2026-08-27 UTC: p95 514ms2026-08-28 UTC: p95 757ms2026-08-29 UTC: p95 645ms2026-08-30 UTC: p95 508ms2026-08-31 UTC: p95 663ms2026-09-01 UTC: p95 415ms2026-09-02 UTC: p95 392ms2026-09-03 UTC: p95 541ms2026-09-04 UTC: p95 521ms2026-09-05 UTC: p95 409ms2026-09-06 UTC: p95 367ms2026-09-07 UTC: p95 386ms2026-09-08 UTC: p95 291ms2026-09-09 UTC: p95 147ms2026-09-10 UTC: p95 180ms2026-09-11 UTC: p95 164ms2026-09-12 UTC: p95 146ms2026-09-13 UTC: p95 175ms2026-09-14 UTC: p95 125ms2026-09-15 UTC: p95 367ms2026-09-16 UTC: p95 402ms2026-09-17 UTC: p95 426ms2026-09-18 UTC: p95 607ms2026-09-19 UTC: p95 556ms2026-09-20 UTC: p95 589ms2026-09-21 UTC: p95 435ms2026-09-22 UTC: p95 404ms2026-09-23 UTC: p95 244ms
Aug 25Sep 8Sep 23
Europe
563msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 394ms2026-08-26 UTC: p95 418ms2026-08-27 UTC: p95 476ms2026-08-28 UTC: p95 421ms2026-08-29 UTC: p95 358ms2026-08-30 UTC: p95 420ms2026-08-31 UTC: p95 485ms2026-09-01 UTC: p95 472ms2026-09-02 UTC: p95 519ms2026-09-03 UTC: p95 583ms2026-09-04 UTC: p95 412ms2026-09-05 UTC: p95 640ms2026-09-06 UTC: p95 507ms2026-09-07 UTC: p95 508ms2026-09-08 UTC: p95 387ms2026-09-09 UTC: p95 379ms2026-09-10 UTC: p95 576ms2026-09-11 UTC: p95 476ms2026-09-12 UTC: p95 320ms2026-09-13 UTC: p95 342ms2026-09-14 UTC: p95 455ms2026-09-15 UTC: p95 469ms2026-09-16 UTC: p95 450ms2026-09-17 UTC: p95 253ms2026-09-18 UTC: p95 257ms2026-09-19 UTC: p95 317ms2026-09-20 UTC: p95 320ms2026-09-21 UTC: p95 406ms2026-09-22 UTC: p95 342ms2026-09-23 UTC: p95 563ms
Aug 25Sep 8Sep 23
Asia-Pacific
472msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 948ms2026-08-26 UTC: p95 853ms2026-08-27 UTC: p95 695ms2026-08-28 UTC: p95 813ms2026-08-29 UTC: p95 855ms2026-08-30 UTC: p95 748ms2026-08-31 UTC: p95 770ms2026-09-01 UTC: p95 869ms2026-09-02 UTC: p95 875ms2026-09-03 UTC: p95 1.0s2026-09-04 UTC: p95 1.0s2026-09-05 UTC: p95 780ms2026-09-06 UTC: p95 527ms2026-09-07 UTC: p95 476ms2026-09-08 UTC: p95 566ms2026-09-09 UTC: p95 691ms2026-09-10 UTC: p95 568ms2026-09-11 UTC: p95 397ms2026-09-12 UTC: p95 420ms2026-09-13 UTC: p95 382ms2026-09-14 UTC: p95 470ms2026-09-15 UTC: p95 415ms2026-09-16 UTC: p95 849ms2026-09-17 UTC: p95 935ms2026-09-18 UTC: p95 483ms2026-09-19 UTC: p95 561ms2026-09-20 UTC: p95 619ms2026-09-21 UTC: p95 563ms2026-09-22 UTC: p95 560ms2026-09-23 UTC: p95 472ms
Aug 25Sep 8Sep 23
US-Central
604msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 538ms2026-09-04 UTC: p95 617ms2026-09-05 UTC: p95 418ms2026-09-06 UTC: p95 380ms2026-09-07 UTC: p95 377ms2026-09-08 UTC: p95 455ms2026-09-09 UTC: p95 444ms2026-09-10 UTC: p95 395ms2026-09-11 UTC: p95 391ms2026-09-12 UTC: p95 422ms2026-09-13 UTC: p95 465ms2026-09-14 UTC: p95 393ms2026-09-15 UTC: p95 408ms2026-09-16 UTC: p95 635ms2026-09-17 UTC: p95 679ms2026-09-18 UTC: p95 588ms2026-09-19 UTC: p95 612ms2026-09-20 UTC: p95 591ms2026-09-21 UTC: p95 630ms2026-09-22 UTC: p95 537ms2026-09-23 UTC: p95 604ms
Aug 25Sep 8Sep 23
Canada
829msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 748ms2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 942ms2026-09-06 UTC: p95 593ms2026-09-07 UTC: p95 505ms2026-09-08 UTC: p95 436ms2026-09-09 UTC: p95 612ms2026-09-10 UTC: p95 435ms2026-09-11 UTC: p95 442ms2026-09-12 UTC: p95 492ms2026-09-13 UTC: p95 677ms2026-09-14 UTC: p95 660ms2026-09-15 UTC: p95 609ms2026-09-16 UTC: p95 490ms2026-09-17 UTC: p95 538ms2026-09-18 UTC: p95 574ms2026-09-19 UTC: p95 650ms2026-09-20 UTC: p95 684ms2026-09-21 UTC: p95 896ms2026-09-22 UTC: p95 824ms2026-09-23 UTC: p95 829ms
Aug 25Sep 8Sep 23
UK
516msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 391ms2026-09-04 UTC: p95 577ms2026-09-05 UTC: p95 415ms2026-09-06 UTC: p95 422ms2026-09-07 UTC: p95 274ms2026-09-08 UTC: p95 223ms2026-09-09 UTC: p95 315ms2026-09-10 UTC: p95 327ms2026-09-11 UTC: p95 271ms2026-09-12 UTC: p95 234ms2026-09-13 UTC: p95 248ms2026-09-14 UTC: p95 273ms2026-09-15 UTC: p95 258ms2026-09-16 UTC: p95 307ms2026-09-17 UTC: p95 376ms2026-09-18 UTC: p95 513ms2026-09-19 UTC: p95 474ms2026-09-20 UTC: p95 441ms2026-09-21 UTC: p95 544ms2026-09-22 UTC: p95 503ms2026-09-23 UTC: p95 516ms
Aug 25Sep 8Sep 23
Southeast Asia
2.5sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 944ms2026-09-05 UTC: p95 988ms2026-09-06 UTC: p95 834ms2026-09-07 UTC: p95 790ms2026-09-08 UTC: p95 899ms2026-09-09 UTC: p95 950ms2026-09-10 UTC: p95 804ms2026-09-11 UTC: p95 828ms2026-09-12 UTC: p95 701ms2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 921ms2026-09-16 UTC: p95 747ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.3s2026-09-23 UTC: p95 2.5s
Aug 25Sep 8Sep 23
Australia
560msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 952ms2026-09-05 UTC: p95 975ms2026-09-06 UTC: p95 952ms2026-09-07 UTC: p95 783ms2026-09-08 UTC: p95 745ms2026-09-09 UTC: p95 972ms2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 768ms2026-09-12 UTC: p95 752ms2026-09-13 UTC: p95 831ms2026-09-14 UTC: p95 846ms2026-09-15 UTC: p95 815ms2026-09-16 UTC: p95 703ms2026-09-17 UTC: p95 814ms2026-09-18 UTC: p95 765ms2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 622ms2026-09-22 UTC: p95 827ms2026-09-23 UTC: p95 560ms
Aug 25Sep 8Sep 23
South America
882msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 661ms2026-09-05 UTC: p95 981ms2026-09-06 UTC: p95 999ms2026-09-07 UTC: p95 815ms2026-09-08 UTC: p95 854ms2026-09-09 UTC: p95 888ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 978ms2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 906ms2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 915ms2026-09-21 UTC: p95 904ms2026-09-22 UTC: p95 827ms2026-09-23 UTC: p95 882ms
Aug 25Sep 8Sep 23

Is it Twitch, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Twitch -- it cannot diagnose Twitch's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 344msstatus code: 401checked: Sep 23, 2026, 9:01 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Twitch normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 62msstatus code: 401checked: Sep 23, 2026, 9:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Twitch normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 452msstatus code: 401checked: Sep 23, 2026, 9:01 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Twitch normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 411msstatus code: 401checked: Sep 23, 2026, 9:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Twitch normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 386msstatus code: 401checked: Sep 23, 2026, 9:05 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Twitch normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 206msstatus code: 401checked: Sep 23, 2026, 9:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Twitch normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 416msstatus code: 401checked: Sep 23, 2026, 9:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Twitch normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 438msstatus code: 401checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Twitch normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 2021msstatus code: 401checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Twitch normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 252msstatus code: 401checked: Sep 23, 2026, 9:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Twitch normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Twitch, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Twitch yet, which is not evidence that nothing is wrong.

Recent outages

Identified Checkout Issues, 2h 49mdeclared on their status page2026-09-16
Watch Streak/Channel Points downtime, 1mdeclared on their status page2026-09-03
Service Negatively Impacted, 6h 22mdeclared on their status page2026-08-27
Identified Checkout Issues, 53mdeclared on their status page2026-03-31
Identified Web Issues, 49mdeclared on their status page2025-06-12
Identified Web Issues, 1h 8mdeclared on their status page2024-09-25
Resolved Service Impact, 17h 6mdeclared on their status page2024-08-29
Service Negatively Impacted, 1mdeclared on their status page2024-08-29

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Twitch since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Twitch covering any window you pick, with our measurements and Twitch's own claim at the time, side by side.

Full availability history for Twitch: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Twitch, and again when they can reach it again. That is our own measurement from ten regions, not Twitch's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Twitch uptime measured by RealUptimeLive, from this page's own readings.
[![Twitch uptime measured by RealUptime](https://realuptime.io/outages/twitch/badge.svg?days=30)](https://realuptime.io/outages/twitch)
<a href="https://realuptime.io/outages/twitch"><img src="https://realuptime.io/outages/twitch/badge.svg?days=30" alt="Twitch uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Twitch's SLA implies, from our measurement

At or above your target

We measured none of downtime for Twitch over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Twitch's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.twitch.tv/helix/games/top
secondary
https://status.twitch.com/
RealUptime is not affiliated with Twitch; the name identifies what we measured, and nothing here speaks for Twitch's own team. We send a single web request to Twitch from 10 regions on our own schedule and time the response. We do not see inside Twitch's systems, do not use an account or real transaction, and are not the same signal Twitch's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Twitch is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.