Skip to content

Outage tracker / Google Meet

Is Google Meet down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Google Meet from all 4 regions we check.

Reachability verified

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

our independent probeslive · checked Sep 3, 2026, 1:27 AM UTC
US-East1151 msOperational
US-West706 msOperational
Europe700 msOperational
Asia-Pacific2065 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
968msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 726ms2026-08-21 UTC: p95 791ms2026-08-22 UTC: p95 688ms2026-08-23 UTC: p95 1.2s2026-08-24 UTC: p95 1.4s2026-08-25 UTC: p95 1.1s2026-08-26 UTC: p95 1.6s2026-08-27 UTC: p95 983ms2026-08-28 UTC: p95 1.3s2026-08-29 UTC: p95 1.3s2026-08-30 UTC: p95 1.3s2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 1.3s2026-09-02 UTC: p95 1.1s2026-09-03 UTC: p95 968ms
Aug 5Aug 19Sep 3
US-West
1.6sp95 · 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-08-20 UTC: p95 930ms2026-08-21 UTC: p95 1.1s2026-08-22 UTC: p95 917ms2026-08-23 UTC: p95 1.3s2026-08-24 UTC: p95 1.2s2026-08-25 UTC: p95 1.1s2026-08-26 UTC: p95 1.5s2026-08-27 UTC: p95 1.6s2026-08-28 UTC: p95 1.4s2026-08-29 UTC: p95 1.6s2026-08-30 UTC: p95 1.3s2026-08-31 UTC: p95 1.4s2026-09-01 UTC: p95 1.3s2026-09-02 UTC: p95 1.4s2026-09-03 UTC: p95 1.6s
Aug 5Aug 19Sep 3
Europe
1.3sp95 · 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-08-20 UTC: p95 480ms2026-08-21 UTC: p95 553ms2026-08-22 UTC: p95 574ms2026-08-23 UTC: p95 1.0s2026-08-24 UTC: p95 1.2s2026-08-25 UTC: p95 1.1s2026-08-26 UTC: p95 977ms2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 819ms2026-08-29 UTC: p95 808ms2026-08-30 UTC: p95 1.0s2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 1.2s2026-09-02 UTC: p95 1.0s2026-09-03 UTC: p95 1.3s
Aug 5Aug 19Sep 3
Asia-Pacific
2.1sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 1.9s2026-08-21 UTC: p95 1.7s2026-08-22 UTC: p95 1.5s2026-08-23 UTC: p95 2.0s2026-08-24 UTC: p95 2.1s2026-08-25 UTC: p95 2.1s2026-08-26 UTC: p95 1.8s2026-08-27 UTC: p95 1.7s2026-08-28 UTC: p95 1.5s2026-08-29 UTC: p95 2.0s2026-08-30 UTC: p95 1.9s2026-08-31 UTC: p95 1.7s2026-09-01 UTC: p95 2.0s2026-09-02 UTC: p95 2.3s2026-09-03 UTC: p95 2.1s
Aug 5Aug 19Sep 3

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

  • US-East
    Operationallatency: 1151msstatus code: 200checked: Sep 3, 2026, 1:04 AM 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: 706msstatus code: 200checked: Sep 3, 2026, 1:01 AM 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.
  • Europe
    Operationallatency: 700msstatus code: 200checked: Sep 3, 2026, 1:27 AM 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.
  • Asia-Pacific
    Operationallatency: 2065msstatus code: 200checked: Sep 3, 2026, 1:05 AM 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.
  • US-Central
    Not monitored from this regionGoogle Meet is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionGoogle Meet is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionGoogle Meet is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionGoogle Meet is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionGoogle Meet is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionGoogle Meet is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

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.

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

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Google Meet, and again when they can reach it again. That is our own measurement from ten regions, not Google Meet's status page. No account, no card.

Delivery channel

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

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 337h 29m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 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 4 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. Google Meet operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.