Skip to content

Outage tracker / YouTube

Is YouTube down?

I'm having a problem

Checks passingchecked moments ago

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

As of Oct 22, 2026, 7:05 PM UTC, RealUptime's checks of YouTube passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of YouTube did not fail from two or more distant regions in the 63 days we have checked it (since Aug 20, 2026). This does not show YouTube works for users.

Email me when our checks of YouTube fail from two or more distant regions

One email when our checks of YouTube fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not YouTube's official status.

our check readinglive · checked Oct 22, 2026, 7:05 PM UTC
US-East692 msChecks passing
US-West586 msChecks passing
Europe120 msChecks passing
Asia-Pacific889 msChecks passing
US-Central668 msChecks passing
Canada577 msChecks passing
UK302 msChecks passing
Southeast Asia986 msChecks passing
Australia1296 msChecks passing
South America1741 msChecks passing
their status pagetheir claim, not our reading

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

YouTube response time, by region

US-East
613msp95 · 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-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 328ms2026-10-06 UTC: p95 422ms2026-10-07 UTC: p95 332ms2026-10-08 UTC: p95 341ms2026-10-09 UTC: p95 321ms2026-10-10 UTC: p95 320ms2026-10-11 UTC: p95 351ms2026-10-12 UTC: p95 341ms2026-10-13 UTC: p95 359ms2026-10-14 UTC: p95 317ms2026-10-15 UTC: p95 343ms2026-10-16 UTC: p95 402ms2026-10-17 UTC: p95 784ms2026-10-18 UTC: p95 922ms2026-10-19 UTC: p95 783ms2026-10-20 UTC: p95 782ms2026-10-21 UTC: p95 734ms2026-10-22 UTC: p95 613ms
Sep 23Oct 7Oct 22
US-West
1.7sp95 · 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-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 428ms2026-10-06 UTC: p95 388ms2026-10-07 UTC: p95 427ms2026-10-08 UTC: p95 402ms2026-10-09 UTC: p95 471ms2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 408ms2026-10-13 UTC: p95 406ms2026-10-14 UTC: p95 423ms2026-10-15 UTC: p95 412ms2026-10-16 UTC: p95 628ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22
Europe
336msp95 · 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-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 244ms2026-10-06 UTC: p95 205ms2026-10-07 UTC: p95 254ms2026-10-08 UTC: p95 190ms2026-10-09 UTC: p95 189ms2026-10-10 UTC: p95 204ms2026-10-11 UTC: p95 170ms2026-10-12 UTC: p95 209ms2026-10-13 UTC: p95 221ms2026-10-14 UTC: p95 201ms2026-10-15 UTC: p95 162ms2026-10-16 UTC: p95 151ms2026-10-17 UTC: p95 255ms2026-10-18 UTC: p95 344ms2026-10-19 UTC: p95 424ms2026-10-20 UTC: p95 345ms2026-10-21 UTC: p95 310ms2026-10-22 UTC: p95 336ms
Sep 23Oct 7Oct 22
Asia-Pacific
1.2sp95 · 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-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 629ms2026-10-06 UTC: p95 694ms2026-10-07 UTC: p95 650ms2026-10-08 UTC: p95 634ms2026-10-09 UTC: p95 698ms2026-10-10 UTC: p95 598ms2026-10-11 UTC: p95 606ms2026-10-12 UTC: p95 648ms2026-10-13 UTC: p95 622ms2026-10-14 UTC: p95 578ms2026-10-15 UTC: p95 732ms2026-10-16 UTC: p95 646ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.2s
Sep 23Oct 7Oct 22
US-Central
1.8sp95 · 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-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.0s2026-10-06 UTC: p95 525ms2026-10-07 UTC: p95 840ms2026-10-08 UTC: p95 545ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 985ms2026-10-11 UTC: p95 407ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 842ms2026-10-14 UTC: p95 450ms2026-10-15 UTC: p95 412ms2026-10-16 UTC: p95 474ms2026-10-17 UTC: p95 598ms2026-10-18 UTC: p95 567ms2026-10-19 UTC: p95 732ms2026-10-20 UTC: p95 804ms2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.8s
Sep 23Oct 7Oct 22
Canada
1.1sp95 · 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-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 595ms2026-10-06 UTC: p95 608ms2026-10-07 UTC: p95 558ms2026-10-08 UTC: p95 548ms2026-10-09 UTC: p95 512ms2026-10-10 UTC: p95 540ms2026-10-11 UTC: p95 548ms2026-10-12 UTC: p95 434ms2026-10-13 UTC: p95 523ms2026-10-14 UTC: p95 926ms2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 932ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.1s
Sep 23Oct 7Oct 22
UK
576msp95 · 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-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 378ms2026-10-06 UTC: p95 341ms2026-10-07 UTC: p95 289ms2026-10-08 UTC: p95 309ms2026-10-09 UTC: p95 349ms2026-10-10 UTC: p95 360ms2026-10-11 UTC: p95 351ms2026-10-12 UTC: p95 295ms2026-10-13 UTC: p95 326ms2026-10-14 UTC: p95 332ms2026-10-15 UTC: p95 264ms2026-10-16 UTC: p95 274ms2026-10-17 UTC: p95 325ms2026-10-18 UTC: p95 485ms2026-10-19 UTC: p95 604ms2026-10-20 UTC: p95 547ms2026-10-21 UTC: p95 531ms2026-10-22 UTC: p95 576ms
Sep 23Oct 7Oct 22
Southeast Asia
1.2sp95 · 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-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 691ms2026-10-06 UTC: p95 656ms2026-10-07 UTC: p95 665ms2026-10-08 UTC: p95 759ms2026-10-09 UTC: p95 670ms2026-10-10 UTC: p95 664ms2026-10-11 UTC: p95 649ms2026-10-12 UTC: p95 563ms2026-10-13 UTC: p95 678ms2026-10-14 UTC: p95 728ms2026-10-15 UTC: p95 744ms2026-10-16 UTC: p95 640ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.2s
Sep 23Oct 7Oct 22
Australia
2.4sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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.5s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.4s
Sep 23Oct 7Oct 22
South America
1.7sp95 · 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-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 915ms2026-10-06 UTC: p95 878ms2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 830ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 903ms2026-10-11 UTC: p95 981ms2026-10-12 UTC: p95 994ms2026-10-13 UTC: p95 940ms2026-10-14 UTC: p95 849ms2026-10-15 UTC: p95 683ms2026-10-16 UTC: p95 884ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22

Check your own site while you wait on YouTube

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: 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
  • APIprimaryUS-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: 692msstatus code: 200checked: Oct 22, 2026, 7:05 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
      Checks passinglatency: 586msstatus code: 200checked: Oct 22, 2026, 7:05 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
      Checks passinglatency: 668msstatus code: 200checked: Oct 22, 2026, 7:04 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
      Checks passinglatency: 577msstatus code: 200checked: Oct 22, 2026, 7:05 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
    Checks passinglatency: 1741msstatus code: 200checked: Oct 22, 2026, 7:04 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 120msstatus code: 200checked: Oct 22, 2026, 7:04 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
      Checks passinglatency: 302msstatus code: 200checked: Oct 22, 2026, 7: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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 889msstatus code: 200checked: Oct 22, 2026, 7: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
      Checks passinglatency: 986msstatus code: 200checked: Oct 22, 2026, 7:05 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
      Checks passinglatency: 1296msstatus code: 200checked: Oct 22, 2026, 7:04 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 probe events

No probe events on record yet for YouTube.

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

Full check history for YouTube: 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

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

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with YouTube's stated SLA

At or above your target

Our checks of YouTube failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: www.youtube.com

RealUptime is not affiliated with YouTube; the name identifies what we checked, 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 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.