Skip to content

Outage tracker / Google Meet

Is Google Meet down?

I'm having a problem

Vendor reports no incidentWhat Google Meet reports

Google Meet reports no incident on its status page.

As of the last successful poll, 2026-10-19 21:24 UTC.

Google Meet'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.

Partially degradedchecked moments ago

Google Meet is answering our probes, but running at least 3.3x its 7-day median from US-East, UK and Asia-Pacific. The rest of the regions we check answered at their usual speed.

As of Oct 19, 2026, 9:29 PM UTC, RealUptime's checks of Google Meet passed in all 10 regions that returned a reading.

Front-door checks

Email me when Google Meet 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 Google Meet's own statement from its status page, with our regional reading beside it.

our check readinglive · checked Oct 19, 2026, 9:29 PM UTC
US-East4286 msDegraded
US-West2836 msChecks passing
Europe884 msChecks passing
Asia-Pacific6134 msDegraded
US-Central2198 msChecks passing
Canada1589 msChecks passing
UK1663 msDegraded
Southeast Asia3618 msChecks passing
Australia6329 msChecks passing
South America2371 msChecks passing
their status pagetheir claim, not our reading

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

Google Meet response time, by region

US-East
4.8sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.8s2026-09-24 UTC: p95 2.1s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 908ms2026-09-28 UTC: p95 872ms2026-09-29 UTC: p95 970ms2026-09-30 UTC: p95 975ms2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.6s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 3.7s2026-10-18 UTC: p95 4.6s2026-10-19 UTC: p95 4.8s
Sep 20Oct 4Oct 19
US-West
3.5sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.8s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.8s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 2.1s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.8s2026-10-10 UTC: p95 2.7s2026-10-11 UTC: p95 2.9s2026-10-12 UTC: p95 2.1s2026-10-13 UTC: p95 2.4s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 3.1s2026-10-18 UTC: p95 3.6s2026-10-19 UTC: p95 3.5s
Sep 20Oct 4Oct 19
Europe
1.9sp95 · 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-09-20 UTC: p95 777ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 866ms2026-09-24 UTC: p95 854ms2026-09-25 UTC: p95 816ms2026-09-26 UTC: p95 897ms2026-09-27 UTC: p95 787ms2026-09-28 UTC: p95 832ms2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 870ms2026-10-02 UTC: p95 939ms2026-10-03 UTC: p95 869ms2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 839ms2026-10-06 UTC: p95 822ms2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 715ms2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 718ms2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.9s
Sep 20Oct 4Oct 19
Asia-Pacific
6.2sp95 · 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-09-20 UTC: p95 2.2s2026-09-21 UTC: p95 2.4s2026-09-22 UTC: p95 2.2s2026-09-23 UTC: p95 1.9s2026-09-24 UTC: p95 2.0s2026-09-25 UTC: p95 2.0s2026-09-26 UTC: p95 2.5s2026-09-27 UTC: p95 2.7s2026-09-28 UTC: p95 2.4s2026-09-29 UTC: p95 2.3s2026-09-30 UTC: p95 2.5s2026-10-01 UTC: p95 2.2s2026-10-02 UTC: p95 2.0s2026-10-03 UTC: p95 2.0s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.8s2026-10-06 UTC: p95 2.4s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 2.0s2026-10-15 UTC: p95 2.1s2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 6.4s2026-10-18 UTC: p95 6.7s2026-10-19 UTC: p95 6.2s
Sep 20Oct 4Oct 19
US-Central
2.4sp95 · latest
5s2.5s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 997ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.9s2026-09-24 UTC: p95 1.9s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 2.3s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 2.2s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 958ms2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.9s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 2.5s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.4s
Sep 20Oct 4Oct 19
Canada
1.9sp95 · 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-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 787ms2026-09-24 UTC: p95 765ms2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.7s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 1.9s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 2.0s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.9s
Sep 20Oct 4Oct 19
UK
2.7sp95 · latest
5s2.5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 353ms2026-09-21 UTC: p95 413ms2026-09-22 UTC: p95 595ms2026-09-23 UTC: p95 466ms2026-09-24 UTC: p95 428ms2026-09-25 UTC: p95 413ms2026-09-26 UTC: p95 632ms2026-09-27 UTC: p95 649ms2026-09-28 UTC: p95 725ms2026-09-29 UTC: p95 655ms2026-09-30 UTC: p95 884ms2026-10-01 UTC: p95 820ms2026-10-02 UTC: p95 894ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 955ms2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 793ms2026-10-11 UTC: p95 951ms2026-10-12 UTC: p95 737ms2026-10-13 UTC: p95 792ms2026-10-14 UTC: p95 690ms2026-10-15 UTC: p95 528ms2026-10-16 UTC: p95 884ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.7s
Sep 20Oct 4Oct 19
Southeast Asia
3.8sp95 · 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-09-20 UTC: p95 2.4s2026-09-21 UTC: p95 2.3s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 2.2s2026-09-25 UTC: p95 3.3s2026-09-26 UTC: p95 2.3s2026-09-27 UTC: p95 2.8s2026-09-28 UTC: p95 2.4s2026-09-29 UTC: p95 2.3s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 2.5s2026-10-02 UTC: p95 2.4s2026-10-03 UTC: p95 2.3s2026-10-04 UTC: p95 2.7s2026-10-05 UTC: p95 2.3s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 2.0s2026-10-08 UTC: p95 1.9s2026-10-09 UTC: p95 1.9s2026-10-10 UTC: p95 2.0s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.9s2026-10-15 UTC: p95 2.1s2026-10-16 UTC: p95 1.8s2026-10-17 UTC: p95 2.9s2026-10-18 UTC: p95 3.0s2026-10-19 UTC: p95 3.8s
Sep 20Oct 4Oct 19
Australia
8.5sp95 · latest
10s5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 4.0s2026-09-21 UTC: p95 4.0s2026-09-22 UTC: p95 3.9s2026-09-23 UTC: p95 3.5s2026-09-24 UTC: p95 3.7s2026-09-25 UTC: p95 4.1s2026-09-26 UTC: p95 3.5s2026-09-27 UTC: p95 4.2s2026-09-28 UTC: p95 4.2s2026-09-29 UTC: p95 3.4s2026-09-30 UTC: p95 3.6s2026-10-01 UTC: p95 4.0s2026-10-02 UTC: p95 4.4s2026-10-03 UTC: p95 4.0s2026-10-04 UTC: p95 3.6s2026-10-05 UTC: p95 3.6s2026-10-06 UTC: p95 3.7s2026-10-07 UTC: p95 4.0s2026-10-08 UTC: p95 4.0s2026-10-09 UTC: p95 3.4s2026-10-10 UTC: p95 3.9s2026-10-11 UTC: p95 3.9s2026-10-12 UTC: p95 3.8s2026-10-13 UTC: p95 4.0s2026-10-14 UTC: p95 3.7s2026-10-15 UTC: p95 3.5s2026-10-16 UTC: p95 3.5s2026-10-17 UTC: p95 8.3s2026-10-18 UTC: p95 8.7s2026-10-19 UTC: p95 8.5s
Sep 20Oct 4Oct 19
South America
3.4sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 3.4s2026-09-21 UTC: p95 3.4s2026-09-22 UTC: p95 3.3s2026-09-23 UTC: p95 3.6s2026-09-24 UTC: p95 3.5s2026-09-25 UTC: p95 3.0s2026-09-26 UTC: p95 3.9s2026-09-27 UTC: p95 3.4s2026-09-28 UTC: p95 3.3s2026-09-29 UTC: p95 3.2s2026-09-30 UTC: p95 3.5s2026-10-01 UTC: p95 2.0s2026-10-02 UTC: p95 2.7s2026-10-03 UTC: p95 3.6s2026-10-04 UTC: p95 4.9s2026-10-05 UTC: p95 2.6s2026-10-06 UTC: p95 3.3s2026-10-07 UTC: p95 3.9s2026-10-08 UTC: p95 3.7s2026-10-09 UTC: p95 3.2s2026-10-10 UTC: p95 3.8s2026-10-11 UTC: p95 3.4s2026-10-12 UTC: p95 2.8s2026-10-13 UTC: p95 3.0s2026-10-14 UTC: p95 3.0s2026-10-15 UTC: p95 2.4s2026-10-16 UTC: p95 2.6s2026-10-17 UTC: p95 3s2026-10-18 UTC: p95 3.0s2026-10-19 UTC: p95 3.4s
Sep 20Oct 4Oct 19

Check your own site while you wait on Google Meet

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

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
    DegradedUS-East, US-West, US-Central, Canada
    • US-East
      Degradedlatency: 4286msstatus code: 200checked: Oct 19, 2026, 9:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Google Meet normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 2836msstatus code: 200checked: Oct 19, 2026, 9:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Google Meet normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 2198msstatus code: 200checked: Oct 19, 2026, 9:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Google Meet normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1589msstatus code: 200checked: Oct 19, 2026, 9:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Google Meet normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 2371msstatus code: 200checked: Oct 19, 2026, 9:13 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Google Meet normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    DegradedEurope, UK
    • Europe
      Checks passinglatency: 884msstatus code: 200checked: Oct 19, 2026, 9:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Google Meet normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Degradedlatency: 1663msstatus code: 200checked: Oct 19, 2026, 9:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Google Meet normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    DegradedAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Degradedlatency: 6134msstatus code: 200checked: Oct 19, 2026, 9:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Google Meet normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 3618msstatus code: 200checked: Oct 19, 2026, 9:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Google Meet normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 6329msstatus code: 200checked: Oct 19, 2026, 9:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Google Meet 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 Meet, 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 Google Meet yet, which is not evidence that nothing is wrong.

Recent probe events

Multiple Workspace Products experiencing Issues., 56mdeclared on their status page2026-05-31
Some Google Meet customers may experience an issue with ‘Continuous meeting chat’ feature, 85h 23mdeclared on their status page2025-12-01
Google Meet customers are experiencing issues loading meet.google.com in the Asia region., 4h 56mdeclared on their status page2025-11-26
Google Meet meetings are seeing elevated error rates in upgrading the call on Android., 20h 51mdeclared on their status page2025-10-30

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

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

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

Google Meet uptime by RealUptime's checksLive, from this page's own readings.
[![Google Meet uptime by RealUptime's checks](https://realuptime.io/outages/google-meet/badge.svg?days=30)](https://realuptime.io/outages/google-meet)
<a href="https://realuptime.io/outages/google-meet"><img src="https://realuptime.io/outages/google-meet/badge.svg?days=30" alt="Google Meet 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 Google Meet down?", https://realuptime.io/outages/google-meet. 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.

What we check

primary
https://meet.google.com/
secondary
https://www.google.com/appsstatus/dashboard/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: meet.google.com

RealUptime is not affiliated with Google Meet; the name identifies what we checked, and nothing here speaks for Google Meet's own team. We send a single web request to Google Meet from 10 regions on our own schedule and time the response. We do not see inside Google Meet's systems, do not use an account or real transaction, and are not the same signal Google Meet's own team has access to. Treat this as one external data point, not a verdict. What we check for Google Meet is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Read the full methodology.