Skip to content

Outage tracker / Gmail

Is Gmail down?

I'm having a problem

Operationalchecked moments ago

We reached Gmail from all 10 regions we check.

As of Oct 5, 2026, 8:15 PM UTC, Gmail answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

Email me the next time we see Gmail go down

Measured by our own probes from ten regions, not Gmail'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, 8:15 PM UTC
US-East150 msOperational
US-West166 msOperational
Europe133 msOperational
Asia-Pacific439 msOperational
US-Central158 msOperational
Canada306 msOperational
UK187 msOperational
Southeast Asia1324 msOperational
Australia1720 msOperational
South America362 msOperational
their status pagetheir claim, not our reading

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

Gmail response time, by region

US-East
331msp95 · 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-06 UTC: p95 300ms2026-09-07 UTC: p95 268ms2026-09-08 UTC: p95 271ms2026-09-09 UTC: p95 314ms2026-09-10 UTC: p95 302ms2026-09-11 UTC: p95 296ms2026-09-12 UTC: p95 248ms2026-09-13 UTC: p95 328ms2026-09-14 UTC: p95 341ms2026-09-15 UTC: p95 346ms2026-09-16 UTC: p95 298ms2026-09-17 UTC: p95 357ms2026-09-18 UTC: p95 317ms2026-09-19 UTC: p95 317ms2026-09-20 UTC: p95 303ms2026-09-21 UTC: p95 344ms2026-09-22 UTC: p95 414ms2026-09-23 UTC: p95 396ms2026-09-24 UTC: p95 810ms2026-09-25 UTC: p95 291ms2026-09-26 UTC: p95 379ms2026-09-27 UTC: p95 309ms2026-09-28 UTC: p95 383ms2026-09-29 UTC: p95 375ms2026-09-30 UTC: p95 378ms2026-10-01 UTC: p95 283ms2026-10-02 UTC: p95 348ms2026-10-03 UTC: p95 341ms2026-10-04 UTC: p95 314ms2026-10-05 UTC: p95 331ms
Sep 6Sep 20Oct 5
US-West
292msp95 · 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 268ms2026-09-07 UTC: p95 283ms2026-09-08 UTC: p95 299ms2026-09-09 UTC: p95 163ms2026-09-10 UTC: p95 145ms2026-09-11 UTC: p95 181ms2026-09-12 UTC: p95 266ms2026-09-13 UTC: p95 158ms2026-09-14 UTC: p95 146ms2026-09-15 UTC: p95 322ms2026-09-16 UTC: p95 406ms2026-09-17 UTC: p95 358ms2026-09-18 UTC: p95 386ms2026-09-19 UTC: p95 381ms2026-09-20 UTC: p95 416ms2026-09-21 UTC: p95 330ms2026-09-22 UTC: p95 343ms2026-09-23 UTC: p95 439ms2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 389ms2026-09-26 UTC: p95 428ms2026-09-27 UTC: p95 386ms2026-09-28 UTC: p95 392ms2026-09-29 UTC: p95 370ms2026-09-30 UTC: p95 332ms2026-10-01 UTC: p95 401ms2026-10-02 UTC: p95 344ms2026-10-03 UTC: p95 420ms2026-10-04 UTC: p95 480ms2026-10-05 UTC: p95 292ms
Sep 6Sep 20Oct 5
Europe
290msp95 · 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-09-06 UTC: p95 211ms2026-09-07 UTC: p95 220ms2026-09-08 UTC: p95 197ms2026-09-09 UTC: p95 227ms2026-09-10 UTC: p95 231ms2026-09-11 UTC: p95 188ms2026-09-12 UTC: p95 184ms2026-09-13 UTC: p95 226ms2026-09-14 UTC: p95 154ms2026-09-15 UTC: p95 198ms2026-09-16 UTC: p95 330ms2026-09-17 UTC: p95 557ms2026-09-18 UTC: p95 599ms2026-09-19 UTC: p95 671ms2026-09-20 UTC: p95 678ms2026-09-21 UTC: p95 710ms2026-09-22 UTC: p95 640ms2026-09-23 UTC: p95 761ms2026-09-24 UTC: p95 549ms2026-09-25 UTC: p95 261ms2026-09-26 UTC: p95 275ms2026-09-27 UTC: p95 270ms2026-09-28 UTC: p95 337ms2026-09-29 UTC: p95 337ms2026-09-30 UTC: p95 245ms2026-10-01 UTC: p95 323ms2026-10-02 UTC: p95 320ms2026-10-03 UTC: p95 335ms2026-10-04 UTC: p95 261ms2026-10-05 UTC: p95 290ms
Sep 6Sep 20Oct 5
Asia-Pacific
643msp95 · 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 559ms2026-09-07 UTC: p95 569ms2026-09-08 UTC: p95 556ms2026-09-09 UTC: p95 561ms2026-09-10 UTC: p95 511ms2026-09-11 UTC: p95 638ms2026-09-12 UTC: p95 574ms2026-09-13 UTC: p95 521ms2026-09-14 UTC: p95 485ms2026-09-15 UTC: p95 604ms2026-09-16 UTC: p95 563ms2026-09-17 UTC: p95 618ms2026-09-18 UTC: p95 698ms2026-09-19 UTC: p95 676ms2026-09-20 UTC: p95 533ms2026-09-21 UTC: p95 624ms2026-09-22 UTC: p95 591ms2026-09-23 UTC: p95 633ms2026-09-24 UTC: p95 716ms2026-09-25 UTC: p95 606ms2026-09-26 UTC: p95 615ms2026-09-27 UTC: p95 639ms2026-09-28 UTC: p95 665ms2026-09-29 UTC: p95 616ms2026-09-30 UTC: p95 662ms2026-10-01 UTC: p95 625ms2026-10-02 UTC: p95 625ms2026-10-03 UTC: p95 710ms2026-10-04 UTC: p95 681ms2026-10-05 UTC: p95 643ms
Sep 6Sep 20Oct 5
US-Central
288msp95 · 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-06 UTC: p95 525ms2026-09-07 UTC: p95 358ms2026-09-08 UTC: p95 331ms2026-09-09 UTC: p95 341ms2026-09-10 UTC: p95 296ms2026-09-11 UTC: p95 370ms2026-09-12 UTC: p95 354ms2026-09-13 UTC: p95 438ms2026-09-14 UTC: p95 506ms2026-09-15 UTC: p95 469ms2026-09-16 UTC: p95 300ms2026-09-17 UTC: p95 379ms2026-09-18 UTC: p95 334ms2026-09-19 UTC: p95 342ms2026-09-20 UTC: p95 350ms2026-09-21 UTC: p95 472ms2026-09-22 UTC: p95 411ms2026-09-23 UTC: p95 379ms2026-09-24 UTC: p95 397ms2026-09-25 UTC: p95 450ms2026-09-26 UTC: p95 466ms2026-09-27 UTC: p95 390ms2026-09-28 UTC: p95 431ms2026-09-29 UTC: p95 339ms2026-09-30 UTC: p95 397ms2026-10-01 UTC: p95 440ms2026-10-02 UTC: p95 373ms2026-10-03 UTC: p95 728ms2026-10-04 UTC: p95 374ms2026-10-05 UTC: p95 288ms
Sep 6Sep 20Oct 5
Canada
424msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 355ms2026-09-07 UTC: p95 380ms2026-09-08 UTC: p95 343ms2026-09-09 UTC: p95 339ms2026-09-10 UTC: p95 387ms2026-09-11 UTC: p95 442ms2026-09-12 UTC: p95 409ms2026-09-13 UTC: p95 407ms2026-09-14 UTC: p95 323ms2026-09-15 UTC: p95 320ms2026-09-16 UTC: p95 314ms2026-09-17 UTC: p95 379ms2026-09-18 UTC: p95 311ms2026-09-19 UTC: p95 343ms2026-09-20 UTC: p95 349ms2026-09-21 UTC: p95 352ms2026-09-22 UTC: p95 387ms2026-09-23 UTC: p95 636ms2026-09-24 UTC: p95 423ms2026-09-25 UTC: p95 405ms2026-09-26 UTC: p95 339ms2026-09-27 UTC: p95 476ms2026-09-28 UTC: p95 373ms2026-09-29 UTC: p95 559ms2026-09-30 UTC: p95 439ms2026-10-01 UTC: p95 384ms2026-10-02 UTC: p95 371ms2026-10-03 UTC: p95 662ms2026-10-04 UTC: p95 627ms2026-10-05 UTC: p95 424ms
Sep 6Sep 20Oct 5
UK
310msp95 · 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 221ms2026-09-07 UTC: p95 285ms2026-09-08 UTC: p95 221ms2026-09-09 UTC: p95 317ms2026-09-10 UTC: p95 208ms2026-09-11 UTC: p95 219ms2026-09-12 UTC: p95 406ms2026-09-13 UTC: p95 253ms2026-09-14 UTC: p95 239ms2026-09-15 UTC: p95 191ms2026-09-16 UTC: p95 171ms2026-09-17 UTC: p95 194ms2026-09-18 UTC: p95 194ms2026-09-19 UTC: p95 191ms2026-09-20 UTC: p95 187ms2026-09-21 UTC: p95 173ms2026-09-22 UTC: p95 306ms2026-09-23 UTC: p95 270ms2026-09-24 UTC: p95 636ms2026-09-25 UTC: p95 342ms2026-09-26 UTC: p95 356ms2026-09-27 UTC: p95 309ms2026-09-28 UTC: p95 322ms2026-09-29 UTC: p95 409ms2026-09-30 UTC: p95 262ms2026-10-01 UTC: p95 362ms2026-10-02 UTC: p95 278ms2026-10-03 UTC: p95 257ms2026-10-04 UTC: p95 289ms2026-10-05 UTC: p95 310ms
Sep 6Sep 20Oct 5
Southeast Asia
1.1sp95 · 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 689ms2026-09-07 UTC: p95 736ms2026-09-08 UTC: p95 798ms2026-09-09 UTC: p95 756ms2026-09-10 UTC: p95 590ms2026-09-11 UTC: p95 833ms2026-09-12 UTC: p95 817ms2026-09-13 UTC: p95 715ms2026-09-14 UTC: p95 680ms2026-09-15 UTC: p95 730ms2026-09-16 UTC: p95 841ms2026-09-17 UTC: p95 801ms2026-09-18 UTC: p95 754ms2026-09-19 UTC: p95 626ms2026-09-20 UTC: p95 666ms2026-09-21 UTC: p95 755ms2026-09-22 UTC: p95 830ms2026-09-23 UTC: p95 671ms2026-09-24 UTC: p95 918ms2026-09-25 UTC: p95 851ms2026-09-26 UTC: p95 800ms2026-09-27 UTC: p95 948ms2026-09-28 UTC: p95 873ms2026-09-29 UTC: p95 759ms2026-09-30 UTC: p95 834ms2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.1s
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.7s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
South America
861msp95 · 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 993ms2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 766ms2026-09-15 UTC: p95 786ms2026-09-16 UTC: p95 847ms2026-09-17 UTC: p95 736ms2026-09-18 UTC: p95 775ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 805ms2026-09-21 UTC: p95 702ms2026-09-22 UTC: p95 761ms2026-09-23 UTC: p95 871ms2026-09-24 UTC: p95 970ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 741ms2026-09-27 UTC: p95 691ms2026-09-28 UTC: p95 793ms2026-09-29 UTC: p95 793ms2026-09-30 UTC: p95 854ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 828ms2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 861ms
Sep 6Sep 20Oct 5

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

What we measured, function by function

Gmail 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
  • AuthUS-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: 150msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Gmail normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 166msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Gmail normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 158msstatus code: 401checked: Oct 5, 2026, 8:12 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Gmail normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 306msstatus code: 401checked: Oct 5, 2026, 8:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Gmail normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 362msstatus code: 401checked: Oct 5, 2026, 8:11 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Gmail normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 133msstatus code: 401checked: Oct 5, 2026, 8:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Gmail normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 187msstatus code: 401checked: Oct 5, 2026, 8:12 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Gmail 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: 439msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Gmail normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1324msstatus code: 401checked: Oct 5, 2026, 8:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Gmail normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1720msstatus code: 401checked: Oct 5, 2026, 8:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Gmail 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 Gmail, 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 Gmail yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Gmail.

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

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

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

Put this badge in your README

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

At or above your target

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