Skip to content

Outage tracker / YouTube

Is YouTube down?

I'm having a problem

Operationalchecked moments ago

We reached YouTube from all 10 regions we check.

As of Oct 5, 2026, 9:04 PM UTC, YouTube 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 YouTube (since Aug 20, 2026).

Email me the next time we see YouTube go down

Measured by our own probes from ten regions, not YouTube's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 9:04 PM UTC
US-East134 msOperational
US-West548 msOperational
Europe119 msOperational
Asia-Pacific332 msOperational
US-Central89 msOperational
Canada238 msOperational
UK115 msOperational
Southeast Asia28 msOperational
Australia1141 msOperational
South America411 msOperational
their status pagetheir claim, not our reading

YouTube publishes no status feed we can read, so the only independent reading here is ours on the left.

YouTube response time, by region

US-East
319msp95 · latest
500ms250ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 289ms2026-09-07 UTC: p95 258ms2026-09-08 UTC: p95 272ms2026-09-09 UTC: p95 258ms2026-09-10 UTC: p95 291ms2026-09-11 UTC: p95 315ms2026-09-12 UTC: p95 303ms2026-09-13 UTC: p95 281ms2026-09-14 UTC: p95 303ms2026-09-15 UTC: p95 297ms2026-09-16 UTC: p95 327ms2026-09-17 UTC: p95 352ms2026-09-18 UTC: p95 365ms2026-09-19 UTC: p95 392ms2026-09-20 UTC: p95 287ms2026-09-21 UTC: p95 326ms2026-09-22 UTC: p95 359ms2026-09-23 UTC: p95 371ms2026-09-24 UTC: p95 377ms2026-09-25 UTC: p95 382ms2026-09-26 UTC: p95 340ms2026-09-27 UTC: p95 348ms2026-09-28 UTC: p95 393ms2026-09-29 UTC: p95 405ms2026-09-30 UTC: p95 398ms2026-10-01 UTC: p95 322ms2026-10-02 UTC: p95 370ms2026-10-03 UTC: p95 356ms2026-10-04 UTC: p95 334ms2026-10-05 UTC: p95 319ms
Sep 6Sep 20Oct 5
US-West
397msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 288ms2026-09-07 UTC: p95 286ms2026-09-08 UTC: p95 360ms2026-09-09 UTC: p95 328ms2026-09-10 UTC: p95 295ms2026-09-11 UTC: p95 263ms2026-09-12 UTC: p95 277ms2026-09-13 UTC: p95 238ms2026-09-14 UTC: p95 329ms2026-09-15 UTC: p95 367ms2026-09-16 UTC: p95 396ms2026-09-17 UTC: p95 523ms2026-09-18 UTC: p95 339ms2026-09-19 UTC: p95 303ms2026-09-20 UTC: p95 338ms2026-09-21 UTC: p95 381ms2026-09-22 UTC: p95 402ms2026-09-23 UTC: p95 637ms2026-09-24 UTC: p95 362ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 557ms2026-09-27 UTC: p95 846ms2026-09-28 UTC: p95 493ms2026-09-29 UTC: p95 407ms2026-09-30 UTC: p95 356ms2026-10-01 UTC: p95 405ms2026-10-02 UTC: p95 390ms2026-10-03 UTC: p95 378ms2026-10-04 UTC: p95 388ms2026-10-05 UTC: p95 397ms
Sep 6Sep 20Oct 5
Europe
248msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 189ms2026-09-07 UTC: p95 201ms2026-09-08 UTC: p95 160ms2026-09-09 UTC: p95 202ms2026-09-10 UTC: p95 171ms2026-09-11 UTC: p95 213ms2026-09-12 UTC: p95 174ms2026-09-13 UTC: p95 179ms2026-09-14 UTC: p95 230ms2026-09-15 UTC: p95 226ms2026-09-16 UTC: p95 220ms2026-09-17 UTC: p95 355ms2026-09-18 UTC: p95 332ms2026-09-19 UTC: p95 178ms2026-09-20 UTC: p95 172ms2026-09-21 UTC: p95 189ms2026-09-22 UTC: p95 193ms2026-09-23 UTC: p95 188ms2026-09-24 UTC: p95 220ms2026-09-25 UTC: p95 225ms2026-09-26 UTC: p95 210ms2026-09-27 UTC: p95 246ms2026-09-28 UTC: p95 207ms2026-09-29 UTC: p95 266ms2026-09-30 UTC: p95 238ms2026-10-01 UTC: p95 220ms2026-10-02 UTC: p95 216ms2026-10-03 UTC: p95 184ms2026-10-04 UTC: p95 198ms2026-10-05 UTC: p95 248ms
Sep 6Sep 20Oct 5
Asia-Pacific
630msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 604ms2026-09-07 UTC: p95 570ms2026-09-08 UTC: p95 531ms2026-09-09 UTC: p95 622ms2026-09-10 UTC: p95 565ms2026-09-11 UTC: p95 510ms2026-09-12 UTC: p95 518ms2026-09-13 UTC: p95 470ms2026-09-14 UTC: p95 470ms2026-09-15 UTC: p95 412ms2026-09-16 UTC: p95 498ms2026-09-17 UTC: p95 533ms2026-09-18 UTC: p95 577ms2026-09-19 UTC: p95 558ms2026-09-20 UTC: p95 600ms2026-09-21 UTC: p95 674ms2026-09-22 UTC: p95 646ms2026-09-23 UTC: p95 756ms2026-09-24 UTC: p95 658ms2026-09-25 UTC: p95 632ms2026-09-26 UTC: p95 714ms2026-09-27 UTC: p95 732ms2026-09-28 UTC: p95 690ms2026-09-29 UTC: p95 712ms2026-09-30 UTC: p95 688ms2026-10-01 UTC: p95 695ms2026-10-02 UTC: p95 645ms2026-10-03 UTC: p95 660ms2026-10-04 UTC: p95 650ms2026-10-05 UTC: p95 630ms
Sep 6Sep 20Oct 5
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-09-06 UTC: p95 399ms2026-09-07 UTC: p95 457ms2026-09-08 UTC: p95 513ms2026-09-09 UTC: p95 476ms2026-09-10 UTC: p95 367ms2026-09-11 UTC: p95 453ms2026-09-12 UTC: p95 566ms2026-09-13 UTC: p95 388ms2026-09-14 UTC: p95 445ms2026-09-15 UTC: p95 467ms2026-09-16 UTC: p95 415ms2026-09-17 UTC: p95 383ms2026-09-18 UTC: p95 374ms2026-09-19 UTC: p95 379ms2026-09-20 UTC: p95 353ms2026-09-21 UTC: p95 357ms2026-09-22 UTC: p95 385ms2026-09-23 UTC: p95 536ms2026-09-24 UTC: p95 544ms2026-09-25 UTC: p95 623ms2026-09-26 UTC: p95 731ms2026-09-27 UTC: p95 431ms2026-09-28 UTC: p95 442ms2026-09-29 UTC: p95 434ms2026-09-30 UTC: p95 492ms2026-10-01 UTC: p95 504ms2026-10-02 UTC: p95 507ms2026-10-03 UTC: p95 424ms2026-10-04 UTC: p95 356ms2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
Canada
590msp95 · 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-06 UTC: p95 496ms2026-09-07 UTC: p95 534ms2026-09-08 UTC: p95 590ms2026-09-09 UTC: p95 628ms2026-09-10 UTC: p95 483ms2026-09-11 UTC: p95 514ms2026-09-12 UTC: p95 409ms2026-09-13 UTC: p95 576ms2026-09-14 UTC: p95 334ms2026-09-15 UTC: p95 605ms2026-09-16 UTC: p95 544ms2026-09-17 UTC: p95 599ms2026-09-18 UTC: p95 431ms2026-09-19 UTC: p95 329ms2026-09-20 UTC: p95 421ms2026-09-21 UTC: p95 675ms2026-09-22 UTC: p95 485ms2026-09-23 UTC: p95 391ms2026-09-24 UTC: p95 522ms2026-09-25 UTC: p95 483ms2026-09-26 UTC: p95 416ms2026-09-27 UTC: p95 429ms2026-09-28 UTC: p95 561ms2026-09-29 UTC: p95 440ms2026-09-30 UTC: p95 418ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 899ms2026-10-03 UTC: p95 506ms2026-10-04 UTC: p95 674ms2026-10-05 UTC: p95 590ms
Sep 6Sep 20Oct 5
UK
335msp95 · 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-06 UTC: p95 232ms2026-09-07 UTC: p95 285ms2026-09-08 UTC: p95 227ms2026-09-09 UTC: p95 251ms2026-09-10 UTC: p95 234ms2026-09-11 UTC: p95 284ms2026-09-12 UTC: p95 384ms2026-09-13 UTC: p95 252ms2026-09-14 UTC: p95 269ms2026-09-15 UTC: p95 253ms2026-09-16 UTC: p95 256ms2026-09-17 UTC: p95 227ms2026-09-18 UTC: p95 199ms2026-09-19 UTC: p95 245ms2026-09-20 UTC: p95 595ms2026-09-21 UTC: p95 416ms2026-09-22 UTC: p95 387ms2026-09-23 UTC: p95 440ms2026-09-24 UTC: p95 844ms2026-09-25 UTC: p95 393ms2026-09-26 UTC: p95 370ms2026-09-27 UTC: p95 384ms2026-09-28 UTC: p95 429ms2026-09-29 UTC: p95 376ms2026-09-30 UTC: p95 363ms2026-10-01 UTC: p95 415ms2026-10-02 UTC: p95 288ms2026-10-03 UTC: p95 293ms2026-10-04 UTC: p95 302ms2026-10-05 UTC: p95 335ms
Sep 6Sep 20Oct 5
Southeast Asia
692msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 763ms2026-09-07 UTC: p95 708ms2026-09-08 UTC: p95 756ms2026-09-09 UTC: p95 860ms2026-09-10 UTC: p95 795ms2026-09-11 UTC: p95 880ms2026-09-12 UTC: p95 853ms2026-09-13 UTC: p95 860ms2026-09-14 UTC: p95 915ms2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 752ms2026-09-17 UTC: p95 825ms2026-09-18 UTC: p95 805ms2026-09-19 UTC: p95 845ms2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 795ms2026-09-22 UTC: p95 758ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 918ms2026-09-25 UTC: p95 884ms2026-09-26 UTC: p95 875ms2026-09-27 UTC: p95 892ms2026-09-28 UTC: p95 719ms2026-09-29 UTC: p95 816ms2026-09-30 UTC: p95 884ms2026-10-01 UTC: p95 800ms2026-10-02 UTC: p95 737ms2026-10-03 UTC: p95 828ms2026-10-04 UTC: p95 796ms2026-10-05 UTC: p95 692ms
Sep 6Sep 20Oct 5
Australia
1.5sp95 · 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-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.7s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
South America
917msp95 · 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-06 UTC: p95 1.0s2026-09-07 UTC: p95 926ms2026-09-08 UTC: p95 936ms2026-09-09 UTC: p95 820ms2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 848ms2026-09-13 UTC: p95 843ms2026-09-14 UTC: p95 825ms2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 961ms2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 815ms2026-09-22 UTC: p95 657ms2026-09-23 UTC: p95 962ms2026-09-24 UTC: p95 938ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 915ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 904ms2026-09-29 UTC: p95 847ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 834ms2026-10-02 UTC: p95 855ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 917ms
Sep 6Sep 20Oct 5

Is it YouTube, 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 YouTube -- it cannot diagnose YouTube's own systems.

What we measured, function by function

YouTube 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 api 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.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
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: 134msstatus code: 200checked: Oct 5, 2026, 9:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach YouTube normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 548msstatus code: 200checked: Oct 5, 2026, 9:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach YouTube normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 89msstatus code: 200checked: Oct 5, 2026, 9:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach YouTube normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 238msstatus code: 200checked: Oct 5, 2026, 9:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach YouTube normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 411msstatus code: 200checked: Oct 5, 2026, 9:01 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach YouTube normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 119msstatus code: 200checked: Oct 5, 2026, 9:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach YouTube normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 115msstatus code: 200checked: Oct 5, 2026, 9:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach YouTube 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: 332msstatus code: 200checked: Oct 5, 2026, 9:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach YouTube normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 28msstatus code: 200checked: Oct 5, 2026, 9:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach YouTube normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1141msstatus code: 200checked: Oct 5, 2026, 9:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach YouTube 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 YouTube, 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 YouTube yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for YouTube.

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

We have been measuring YouTube since August 20, 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 YouTube covering any window you pick, with our measurements and YouTube's own claim at the time, side by side.

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

Put this badge in your README

YouTube uptime measured by RealUptimeLive, from this page's own readings.
[![YouTube uptime measured by RealUptime](https://realuptime.io/outages/youtube/badge.svg?days=30)](https://realuptime.io/outages/youtube)
<a href="https://realuptime.io/outages/youtube"><img src="https://realuptime.io/outages/youtube/badge.svg?days=30" alt="YouTube 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 YouTube's SLA implies, from our measurement

At or above your target

We measured none of downtime for YouTube 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 YouTube'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: live API
https://www.youtube.com/oembed?url=https://www.youtube.com/watch?v=jNQXAC9IVRw
secondary
https://www.youtube.com/
RealUptime is not affiliated with YouTube; the name identifies what we measured, and nothing here speaks for YouTube's own team. We send a single web request to YouTube from 10 regions on our own schedule and time the response. We do not see inside YouTube's systems, do not use an account or real transaction, and are not the same signal YouTube's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for YouTube 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.