Skip to content

Outage tracker / Twitch

Is Twitch down?

I'm having a problem

Vendor reports no incidentWhat Twitch reports

Twitch reports no incident on its status page.

As of the last successful poll, 2026-11-07 17:04 UTC.

Twitch's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Twitch pass from all 10 regions we check.

As of Nov 7, 2026, 5:37 PM UTC, RealUptime's checks of Twitch passed in all 10 regions that returned a reading.

Front-door and live API checks

Email me when Twitch reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Twitch's own statement from its status page, with our regional reading beside it.

our check readinglive · checked Nov 7, 2026, 5:37 PM UTC
US-East820 msChecks passing
US-West998 msChecks passing
Europe505 msChecks passing
Asia-Pacific2495 msChecks passing
US-Central585 msChecks passing
Canada778 msChecks passing
UK509 msChecks passing
Southeast Asia901 msChecks passing
Australia2252 msChecks passing
South America1611 msChecks passing
their status pagetheir claim, not our reading

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

from Twitch's own status page, checked Nov 7, 2026, 5:07 PM UTC
Twitch's own status page shows no incident, and our checks of Twitch pass right now.

Twitch's own component breakdown, as they publish it

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

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
1.5sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 475ms2026-10-10 UTC: p95 451ms2026-10-11 UTC: p95 482ms2026-10-12 UTC: p95 427ms2026-10-13 UTC: p95 436ms2026-10-14 UTC: p95 413ms2026-10-15 UTC: p95 386ms2026-10-16 UTC: p95 463ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 2.0s2026-11-06 UTC: p95 1.9s2026-11-07 UTC: p95 1.5s
Oct 9Oct 23Nov 7
US-West
2.1sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 403ms2026-10-10 UTC: p95 398ms2026-10-11 UTC: p95 358ms2026-10-12 UTC: p95 382ms2026-10-13 UTC: p95 337ms2026-10-14 UTC: p95 478ms2026-10-15 UTC: p95 364ms2026-10-16 UTC: p95 414ms2026-10-17 UTC: p95 990ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 1.9s2026-11-06 UTC: p95 1.9s2026-11-07 UTC: p95 2.1s
Oct 9Oct 23Nov 7
Europe
1.7sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 333ms2026-10-10 UTC: p95 286ms2026-10-11 UTC: p95 373ms2026-10-12 UTC: p95 393ms2026-10-13 UTC: p95 289ms2026-10-14 UTC: p95 453ms2026-10-15 UTC: p95 427ms2026-10-16 UTC: p95 356ms2026-10-17 UTC: p95 467ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 912ms2026-10-22 UTC: p95 946ms2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1s2026-10-26 UTC: p95 1.0s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 720ms2026-10-30 UTC: p95 792ms2026-10-31 UTC: p95 835ms2026-11-01 UTC: p95 789ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 2.0s2026-11-06 UTC: p95 2.0s2026-11-07 UTC: p95 1.7s
Oct 9Oct 23Nov 7
Asia-Pacific
2.6sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 524ms2026-10-10 UTC: p95 566ms2026-10-11 UTC: p95 708ms2026-10-12 UTC: p95 625ms2026-10-13 UTC: p95 744ms2026-10-14 UTC: p95 737ms2026-10-15 UTC: p95 831ms2026-10-16 UTC: p95 977ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 2.7s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 5.7s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.2s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.6s2026-11-06 UTC: p95 3.2s2026-11-07 UTC: p95 2.6s
Oct 9Oct 23Nov 7
US-Central
1.1sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 552ms2026-10-10 UTC: p95 579ms2026-10-11 UTC: p95 312ms2026-10-12 UTC: p95 487ms2026-10-13 UTC: p95 538ms2026-10-14 UTC: p95 500ms2026-10-15 UTC: p95 630ms2026-10-16 UTC: p95 451ms2026-10-17 UTC: p95 943ms2026-10-18 UTC: p95 950ms2026-10-19 UTC: p95 951ms2026-10-20 UTC: p95 965ms2026-10-21 UTC: p95 890ms2026-10-22 UTC: p95 335ms2026-10-23 UTC: p95 432ms2026-10-24 UTC: p95 531ms2026-10-25 UTC: p95 451ms2026-10-26 UTC: p95 540ms2026-10-27 UTC: p95 724ms2026-10-28 UTC: p95 771ms2026-10-29 UTC: p95 891ms2026-10-30 UTC: p95 745ms2026-10-31 UTC: p95 748ms2026-11-01 UTC: p95 800ms2026-11-02 UTC: p95 762ms2026-11-03 UTC: p95 988ms2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 954ms2026-11-06 UTC: p95 1.1s2026-11-07 UTC: p95 1.1s
Oct 9Oct 23Nov 7
Canada
1.3sp95 · latest
2.5s1.3s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 524ms2026-10-10 UTC: p95 514ms2026-10-11 UTC: p95 355ms2026-10-12 UTC: p95 466ms2026-10-13 UTC: p95 411ms2026-10-14 UTC: p95 553ms2026-10-15 UTC: p95 446ms2026-10-16 UTC: p95 488ms2026-10-17 UTC: p95 977ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 983ms2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.4s2026-11-06 UTC: p95 2.2s2026-11-07 UTC: p95 1.3s
Oct 9Oct 23Nov 7
UK
806msp95 · 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-10-09 UTC: p95 410ms2026-10-10 UTC: p95 355ms2026-10-11 UTC: p95 265ms2026-10-12 UTC: p95 272ms2026-10-13 UTC: p95 258ms2026-10-14 UTC: p95 301ms2026-10-15 UTC: p95 353ms2026-10-16 UTC: p95 304ms2026-10-17 UTC: p95 730ms2026-10-18 UTC: p95 732ms2026-10-19 UTC: p95 760ms2026-10-20 UTC: p95 919ms2026-10-21 UTC: p95 787ms2026-10-22 UTC: p95 620ms2026-10-23 UTC: p95 431ms2026-10-24 UTC: p95 366ms2026-10-25 UTC: p95 403ms2026-10-26 UTC: p95 554ms2026-10-27 UTC: p95 592ms2026-10-28 UTC: p95 762ms2026-10-29 UTC: p95 610ms2026-10-30 UTC: p95 523ms2026-10-31 UTC: p95 608ms2026-11-01 UTC: p95 560ms2026-11-02 UTC: p95 563ms2026-11-03 UTC: p95 759ms2026-11-04 UTC: p95 714ms2026-11-05 UTC: p95 916ms2026-11-06 UTC: p95 772ms2026-11-07 UTC: p95 806ms
Oct 9Oct 23Nov 7
Southeast Asia
2.0sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 792ms2026-10-11 UTC: p95 931ms2026-10-12 UTC: p95 761ms2026-10-13 UTC: p95 911ms2026-10-14 UTC: p95 756ms2026-10-15 UTC: p95 911ms2026-10-16 UTC: p95 868ms2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.0s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.7s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.5s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.9s2026-11-06 UTC: p95 1.9s2026-11-07 UTC: p95 2.0s
Oct 9Oct 23Nov 7
Australia
3.6sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 493ms2026-10-10 UTC: p95 635ms2026-10-11 UTC: p95 932ms2026-10-12 UTC: p95 844ms2026-10-13 UTC: p95 810ms2026-10-14 UTC: p95 990ms2026-10-15 UTC: p95 515ms2026-10-16 UTC: p95 852ms2026-10-17 UTC: p95 2.8s2026-10-18 UTC: p95 3.2s2026-10-19 UTC: p95 3.3s2026-10-20 UTC: p95 3.1s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 999ms2026-10-23 UTC: p95 953ms2026-10-24 UTC: p95 980ms2026-10-25 UTC: p95 964ms2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 2.3s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 2.9s2026-11-03 UTC: p95 3.3s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 2.4s2026-11-06 UTC: p95 4.0s2026-11-07 UTC: p95 3.6s
Oct 9Oct 23Nov 7
South America
2.4sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 991ms2026-10-15 UTC: p95 941ms2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 2.7s2026-10-18 UTC: p95 3.1s2026-10-19 UTC: p95 3.1s2026-10-20 UTC: p95 3.2s2026-10-21 UTC: p95 3.1s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 8.0s2026-10-24 UTC: p95 2.7s2026-10-25 UTC: p95 2.5s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.7s2026-10-28 UTC: p95 2.8s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.4s2026-10-31 UTC: p95 2.6s2026-11-01 UTC: p95 2.9s2026-11-02 UTC: p95 3.1s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 3.1s2026-11-05 UTC: p95 3.5s2026-11-06 UTC: p95 2.8s2026-11-07 UTC: p95 2.4s
Oct 9Oct 23Nov 7

Check your own site while you wait on Twitch

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 we measured, function by function

Twitch answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • ChatUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • EventSubUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • LoginUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Video (Broadcasting)US-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Video (Watching)US-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • WebsiteUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 820msstatus code: 401checked: Nov 7, 2026, 5:35 PM 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
      Checks passinglatency: 998msstatus code: 401checked: Nov 7, 2026, 5:37 PM 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
      Checks passinglatency: 585msstatus code: 401checked: Nov 7, 2026, 5:37 PM 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
      Checks passinglatency: 778msstatus code: 401checked: Nov 7, 2026, 5:35 PM 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
    Checks passinglatency: 1611msstatus code: 401checked: Nov 7, 2026, 5:17 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 505msstatus code: 401checked: Nov 7, 2026, 5:37 PM 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
      Checks passinglatency: 509msstatus code: 401checked: Nov 7, 2026, 5:33 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2495msstatus code: 401checked: Nov 7, 2026, 5:34 PM 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
      Checks passinglatency: 901msstatus code: 401checked: Nov 7, 2026, 5:36 PM 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
      Checks passinglatency: 2252msstatus code: 401checked: Nov 7, 2026, 5:19 PM 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 probe events

Identified Emotes Issues, 34mdeclared on their status page2026-10-21
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

check 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 check readings and Twitch's own claim at the time, side by side.

Full check history for Twitch: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Twitch uptime by RealUptime's checksLive, from this page's own readings.
[![Twitch uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Twitch down?", https://realuptime.io/outages/twitch. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://api.twitch.tv/helix/games/top
secondary
https://status.twitch.com/
secondary
https://www.twitch.tv/
secondary
https://id.twitch.tv/oauth2/.well-known/openid-configuration
secondary
wss://irc-ws.chat.twitch.tv:443
secondary
https://ingest.twitch.tv/ingests
secondary
https://static-cdn.jtvnw.net/ttv-boxart/509658-285x380.jpg
secondary
wss://eventsub.wss.twitch.tv/ws

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.twitch.tv

RealUptime is not affiliated with Twitch; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.