Skip to content

Outage tracker / Google Meet

Is Google Meet down?

I'm having a problem

Operationalchecked 4 minutes ago

We reached Google Meet from all 10 regions we check.

As of Oct 6, 2026, 9:53 PM UTC, Google Meet answered RealUptime's probes in all 10 regions that returned a reading.

Reachability verified

No outage recorded in the 47 days we have measured Google Meet (since Aug 20, 2026).

Email me the next time we see Google Meet go down

Measured by our own probes from ten regions, not Google Meet'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 6, 2026, 9:53 PM UTC
US-East1222 msOperational
US-West1527 msOperational
Europe946 msOperational
Asia-Pacific1297 msOperational
US-Central886 msOperational
Canada1618 msOperational
UK896 msOperational
Southeast Asia1666 msOperational
Australia2863 msOperational
South America2010 msOperational
their status pagetheir claim, not our reading

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

Google Meet response time, by region

US-East
1.4sp95 · 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-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.7s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.1s2026-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.4s
Sep 7Sep 21Oct 6
US-West
1.7sp95 · 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-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 854ms2026-09-12 UTC: p95 867ms2026-09-13 UTC: p95 852ms2026-09-14 UTC: p95 943ms2026-09-15 UTC: p95 1.7s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.4s2026-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.7s
Sep 7Sep 21Oct 6
Europe
815msp95 · 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-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.7s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.8s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 894ms2026-09-17 UTC: p95 906ms2026-09-18 UTC: p95 878ms2026-09-19 UTC: p95 801ms2026-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 815ms
Sep 7Sep 21Oct 6
Asia-Pacific
2.4sp95 · 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-09-07 UTC: p95 1.9s2026-09-08 UTC: p95 1.9s2026-09-09 UTC: p95 2.0s2026-09-10 UTC: p95 2.2s2026-09-11 UTC: p95 2.3s2026-09-12 UTC: p95 2.3s2026-09-13 UTC: p95 2.0s2026-09-14 UTC: p95 2.3s2026-09-15 UTC: p95 2.4s2026-09-16 UTC: p95 2.1s2026-09-17 UTC: p95 2.4s2026-09-18 UTC: p95 2.3s2026-09-19 UTC: p95 2.3s2026-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.4s
Sep 7Sep 21Oct 6
US-Central
1.5sp95 · 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-07 UTC: p95 2.1s2026-09-08 UTC: p95 2.2s2026-09-09 UTC: p95 1.8s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 2.7s2026-09-14 UTC: p95 1.8s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 992ms2026-09-19 UTC: p95 964ms2026-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.5s
Sep 7Sep 21Oct 6
Canada
1.7sp95 · 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-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.2s2026-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.7s
Sep 7Sep 21Oct 6
UK
1.0sp95 · 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-09-07 UTC: p95 461ms2026-09-08 UTC: p95 377ms2026-09-09 UTC: p95 376ms2026-09-10 UTC: p95 349ms2026-09-11 UTC: p95 538ms2026-09-12 UTC: p95 409ms2026-09-13 UTC: p95 341ms2026-09-14 UTC: p95 281ms2026-09-15 UTC: p95 314ms2026-09-16 UTC: p95 354ms2026-09-17 UTC: p95 392ms2026-09-18 UTC: p95 372ms2026-09-19 UTC: p95 327ms2026-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.0s
Sep 7Sep 21Oct 6
Southeast Asia
1.6sp95 · 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-07 UTC: p95 1.9s2026-09-08 UTC: p95 2.0s2026-09-09 UTC: p95 1.9s2026-09-10 UTC: p95 2.2s2026-09-11 UTC: p95 2.6s2026-09-12 UTC: p95 2.4s2026-09-13 UTC: p95 2.3s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 998ms2026-09-16 UTC: p95 1.9s2026-09-17 UTC: p95 2.1s2026-09-18 UTC: p95 2.7s2026-09-19 UTC: p95 2.4s2026-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.6s
Sep 7Sep 21Oct 6
Australia
3.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-09-07 UTC: p95 4.7s2026-09-08 UTC: p95 4.2s2026-09-09 UTC: p95 4.5s2026-09-10 UTC: p95 3.8s2026-09-11 UTC: p95 3.8s2026-09-12 UTC: p95 4.1s2026-09-13 UTC: p95 3.5s2026-09-14 UTC: p95 4.1s2026-09-15 UTC: p95 3.4s2026-09-16 UTC: p95 4.1s2026-09-17 UTC: p95 4.2s2026-09-18 UTC: p95 4.5s2026-09-19 UTC: p95 4.1s2026-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.8s
Sep 7Sep 21Oct 6
South America
3.2sp95 · 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-07 UTC: p95 3.0s2026-09-08 UTC: p95 3.3s2026-09-09 UTC: p95 3.4s2026-09-10 UTC: p95 3.3s2026-09-11 UTC: p95 3.4s2026-09-12 UTC: p95 3.1s2026-09-13 UTC: p95 3.0s2026-09-14 UTC: p95 3.1s2026-09-15 UTC: p95 3.6s2026-09-16 UTC: p95 3.6s2026-09-17 UTC: p95 3.6s2026-09-18 UTC: p95 2.8s2026-09-19 UTC: p95 2.9s2026-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.2s
Sep 7Sep 21Oct 6

Is it Google Meet, 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 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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 1222msstatus code: 200checked: Oct 6, 2026, 9:47 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
      Operationallatency: 1527msstatus code: 200checked: Oct 6, 2026, 9:50 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
      Operationallatency: 886msstatus code: 200checked: Oct 6, 2026, 9:47 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
      Operationallatency: 1618msstatus code: 200checked: Oct 6, 2026, 9:41 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
    Operationallatency: 2010msstatus code: 200checked: Oct 6, 2026, 9:48 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 946msstatus code: 200checked: Oct 6, 2026, 9:51 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
      Operationallatency: 896msstatus code: 200checked: Oct 6, 2026, 9:50 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1297msstatus code: 200checked: Oct 6, 2026, 9:53 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
      Operationallatency: 1666msstatus code: 200checked: Oct 6, 2026, 9:38 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
      Operationallatency: 2863msstatus code: 200checked: Oct 6, 2026, 9:49 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 outages

No outages on record yet for Google Meet.

measured 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 measurements and Google Meet's own claim at the time, side by side.

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

Put this badge in your README

Google Meet uptime measured by RealUptimeLive, from this page's own readings.
[![Google Meet uptime measured by RealUptime](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 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 Google Meet's SLA implies, from our measurement

At or above your target

We measured none of downtime for Google Meet 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 Google Meet'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

primary
https://meet.google.com/
secondary
https://www.google.com/appsstatus/dashboard/
RealUptime is not affiliated with Google Meet; the name identifies what we measured, 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 proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Read the full methodology.