Skip to content

Outage tracker / Google Drive

Is Google Drive down?

I'm having a problem

Vendor reports no incidentWhat Google Drive reports

Google Drive reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:14 UTC.

Google Drive'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 1 minute ago

Our checks of Google Drive pass from all 10 regions we check.

As of Nov 5, 2026, 2:27 PM UTC, RealUptime's checks of Google Drive passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:27 PM UTC
US-East464 msChecks passing
US-West1333 msChecks passing
Europe843 msChecks passing
Asia-Pacific1209 msChecks passing
US-Central956 msChecks passing
Canada795 msChecks passing
UK529 msChecks passing
Southeast Asia1502 msChecks passing
Australia2247 msChecks passing
South America1537 msChecks passing
their status pagetheir claim, not our reading

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

Google Drive response time, by region

US-East
2.3sp95 · 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-07 UTC: p95 917ms2026-10-08 UTC: p95 948ms2026-10-09 UTC: p95 777ms2026-10-10 UTC: p95 794ms2026-10-11 UTC: p95 806ms2026-10-12 UTC: p95 860ms2026-10-13 UTC: p95 898ms2026-10-14 UTC: p95 946ms2026-10-15 UTC: p95 835ms2026-10-16 UTC: p95 971ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
US-West
2.0sp95 · 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-07 UTC: p95 597ms2026-10-08 UTC: p95 607ms2026-10-09 UTC: p95 577ms2026-10-10 UTC: p95 633ms2026-10-11 UTC: p95 648ms2026-10-12 UTC: p95 587ms2026-10-13 UTC: p95 675ms2026-10-14 UTC: p95 821ms2026-10-15 UTC: p95 617ms2026-10-16 UTC: p95 605ms2026-10-17 UTC: p95 912ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Europe
1.5sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 376ms2026-10-08 UTC: p95 493ms2026-10-09 UTC: p95 478ms2026-10-10 UTC: p95 431ms2026-10-11 UTC: p95 538ms2026-10-12 UTC: p95 611ms2026-10-13 UTC: p95 294ms2026-10-14 UTC: p95 364ms2026-10-15 UTC: p95 410ms2026-10-16 UTC: p95 287ms2026-10-17 UTC: p95 673ms2026-10-18 UTC: p95 877ms2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 791ms2026-10-21 UTC: p95 905ms2026-10-22 UTC: p95 888ms2026-10-23 UTC: p95 872ms2026-10-24 UTC: p95 770ms2026-10-25 UTC: p95 777ms2026-10-26 UTC: p95 875ms2026-10-27 UTC: p95 875ms2026-10-28 UTC: p95 896ms2026-10-29 UTC: p95 948ms2026-10-30 UTC: p95 860ms2026-10-31 UTC: p95 954ms2026-11-01 UTC: p95 995ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
Asia-Pacific
2.0sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 612ms2026-10-08 UTC: p95 745ms2026-10-09 UTC: p95 774ms2026-10-10 UTC: p95 578ms2026-10-11 UTC: p95 702ms2026-10-12 UTC: p95 699ms2026-10-13 UTC: p95 613ms2026-10-14 UTC: p95 686ms2026-10-15 UTC: p95 653ms2026-10-16 UTC: p95 619ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 3.5s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
US-Central
1.4sp95 · 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-07 UTC: p95 452ms2026-10-08 UTC: p95 397ms2026-10-09 UTC: p95 353ms2026-10-10 UTC: p95 294ms2026-10-11 UTC: p95 408ms2026-10-12 UTC: p95 327ms2026-10-13 UTC: p95 476ms2026-10-14 UTC: p95 653ms2026-10-15 UTC: p95 611ms2026-10-16 UTC: p95 583ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 935ms2026-10-25 UTC: p95 966ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 932ms2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
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-10-07 UTC: p95 707ms2026-10-08 UTC: p95 685ms2026-10-09 UTC: p95 584ms2026-10-10 UTC: p95 609ms2026-10-11 UTC: p95 413ms2026-10-12 UTC: p95 494ms2026-10-13 UTC: p95 502ms2026-10-14 UTC: p95 425ms2026-10-15 UTC: p95 491ms2026-10-16 UTC: p95 616ms2026-10-17 UTC: p95 901ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
UK
993msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 291ms2026-10-08 UTC: p95 442ms2026-10-09 UTC: p95 402ms2026-10-10 UTC: p95 308ms2026-10-11 UTC: p95 248ms2026-10-12 UTC: p95 272ms2026-10-13 UTC: p95 376ms2026-10-14 UTC: p95 399ms2026-10-15 UTC: p95 188ms2026-10-16 UTC: p95 330ms2026-10-17 UTC: p95 669ms2026-10-18 UTC: p95 909ms2026-10-19 UTC: p95 931ms2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 771ms2026-10-22 UTC: p95 882ms2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 979ms2026-10-29 UTC: p95 893ms2026-10-30 UTC: p95 914ms2026-10-31 UTC: p95 957ms2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 858ms2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 993ms
Oct 7Oct 21Nov 5
Southeast Asia
2.1sp95 · 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-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 2.9s2026-10-24 UTC: p95 2.7s2026-10-25 UTC: p95 2.7s2026-10-26 UTC: p95 3.0s2026-10-27 UTC: p95 2.6s2026-10-28 UTC: p95 2.7s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.6s2026-11-01 UTC: p95 2.7s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Australia
2.8sp95 · 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-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.8s2026-10-17 UTC: p95 3.4s2026-10-18 UTC: p95 3.1s2026-10-19 UTC: p95 2.9s2026-10-20 UTC: p95 3.5s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 3.3s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.8s
Oct 7Oct 21Nov 5
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-07 UTC: p95 794ms2026-10-08 UTC: p95 717ms2026-10-09 UTC: p95 886ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 966ms2026-10-12 UTC: p95 1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 3.1s2026-10-23 UTC: p95 9.9s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.4s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 2.2s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
Why some readings show as awaiting data. 1 of 20 readings for Google Drive came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about Google Drive's health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Check your own site while you wait on Google Drive

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 Google Drive. It cannot diagnose Google Drive's own systems.

What we measured, function by function

Google Drive 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
  • DocsUS-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
  • DriveUS-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
  • SheetsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Awaiting dataUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

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

Get an email when Google Drive reports an incident

Email me when Google Drive reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

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

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: 464msstatus code: 401checked: Nov 5, 2026, 2:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Google Drive normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1333msstatus code: 401checked: Nov 5, 2026, 2:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Google Drive normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 956msstatus code: 401checked: Nov 5, 2026, 2:18 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Google Drive normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 795msstatus code: 401checked: Nov 5, 2026, 2:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Google Drive normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1537msstatus code: 401checked: Nov 5, 2026, 2:14 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Google Drive 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: 843msstatus code: 401checked: Nov 5, 2026, 2:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Google Drive normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 529msstatus code: 401checked: Nov 5, 2026, 2:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Google Drive 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: 1209msstatus code: 401checked: Nov 5, 2026, 2:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Google Drive normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1502msstatus code: 401checked: Nov 5, 2026, 2:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Google Drive normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2247msstatus code: 401checked: Nov 5, 2026, 2:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Google Drive 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 Google Drive, 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 started counting reports for Google Drive on September 24, 2026.

Recent probe events

We experienced intermittent latency with Google Drive, 37mdeclared on their status page2026-09-16
Some customers may experience slowness while using Google Drive., 12h 42mdeclared on their status page2026-08-18
Multiple Workspace Products experiencing Issues., 56mdeclared on their status page2026-05-31
Description, 2h 30mdeclared on their status page2026-03-13

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

We have been measuring Google Drive 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 Google Drive covering any window you pick, with our check readings and Google Drive's own claim at the time, side by side.

Full check history for Google Drive: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Google Drive uptime by RealUptime's checksLive, from this page's own readings.
[![Google Drive uptime by RealUptime's checks](https://realuptime.io/outages/google-drive/badge.svg?days=30)](https://realuptime.io/outages/google-drive)
<a href="https://realuptime.io/outages/google-drive"><img src="https://realuptime.io/outages/google-drive/badge.svg?days=30" alt="Google Drive 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 Google Drive down?", https://realuptime.io/outages/google-drive. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://www.googleapis.com/drive/v3/about
secondary
https://www.google.com/appsstatus/dashboard/
secondary
https://drive.google.com/
secondary
https://docs.google.com/document/
secondary
https://docs.google.com/spreadsheets/

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: www.googleapis.com

RealUptime is not affiliated with Google Drive; the name identifies what we checked, and nothing here speaks for Google Drive's own team. We send a single web request to Google Drive from 10 regions on our own schedule and time the response. We do not see inside Google Drive's systems, do not use an account or real transaction, and are not the same signal Google Drive's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Google Drive 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.