User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
meet.google.com · Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests meet.google.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 336 ms · 4 min ago.
All clear
Google Meet: no active incidents Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 145 ms | 0 |
| 11:45 | 0 | 0.0 | 321 ms | 0 |
| 12:00 | 0 | 0.0 | 561 ms | 0 |
| 12:15 | 0 | 0.0 | 215 ms | 0 |
| 12:30 | 0 | 0.0 | 276 ms | 0 |
| 12:45 | 0 | 0.0 | 225 ms | 0 |
| 13:00 | 0 | 0.0 | 263 ms | 0 |
| 13:15 | 0 | 0.0 | 397 ms | 0 |
| 13:30 | 0 | 0.0 | 191 ms | 0 |
| 13:45 | 0 | 0.0 | 276 ms | 0 |
| 14:00 | 0 | 0.0 | 794 ms | 0 |
| 14:15 | 0 | 0.0 | 222 ms | 0 |
| 14:30 | 0 | 0.0 | 367 ms | 0 |
| 14:45 | 0 | 0.0 | 283 ms | 0 |
| 15:00 | 0 | 0.0 | 406 ms | 0 |
| 15:15 | 0 | 0.0 | 243 ms | 0 |
| 15:30 | 0 | 0.0 | 313 ms | 0 |
| 15:45 | 0 | 0.0 | 437 ms | 0 |
| 16:00 | 0 | 0.0 | 292 ms | 0 |
| 16:15 | 0 | 0.0 | 181 ms | 0 |
| 16:30 | 0 | 0.0 | 452 ms | 0 |
| 16:45 | 0 | 0.0 | 364 ms | 0 |
| 17:00 | 0 | 0.0 | 223 ms | 0 |
| 17:15 | 0 | 0.0 | 383 ms | 0 |
| 17:30 | 0 | 0.0 | 391 ms | 0 |
| 17:45 | 0 | 0.0 | 936 ms | 0 |
| 18:00 | 0 | 0.0 | 772 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status badge · JSON
No outages on record for Google Meet yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Google Meet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Runs on: Google
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.