Skip to content

Outage tracker / Google Maps

Is Google Maps down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Google Maps from all 10 regions we check.

As of Sep 23, 2026, 9:09 AM UTC, Google Maps answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Google Maps (since Aug 8, 2026).

our independent probeslive · checked Sep 23, 2026, 9:09 AM UTC
US-East95 msOperational
US-West257 msOperational
Europe193 msOperational
Asia-Pacific104 msOperational
US-Central417 msOperational
Canada114 msOperational
UK100 msOperational
Southeast Asia852 msOperational
Australia1100 msOperational
South America330 msOperational
their status pagetheir claim, not our reading

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

Google Maps response time, by region

US-East
448msp95 · 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-08-25 UTC: p95 486ms2026-08-26 UTC: p95 860ms2026-08-27 UTC: p95 506ms2026-08-28 UTC: p95 524ms2026-08-29 UTC: p95 389ms2026-08-30 UTC: p95 272ms2026-08-31 UTC: p95 215ms2026-09-01 UTC: p95 558ms2026-09-02 UTC: p95 398ms2026-09-03 UTC: p95 468ms2026-09-04 UTC: p95 453ms2026-09-05 UTC: p95 362ms2026-09-06 UTC: p95 626ms2026-09-07 UTC: p95 631ms2026-09-08 UTC: p95 609ms2026-09-09 UTC: p95 649ms2026-09-10 UTC: p95 680ms2026-09-11 UTC: p95 603ms2026-09-12 UTC: p95 579ms2026-09-13 UTC: p95 641ms2026-09-14 UTC: p95 551ms2026-09-15 UTC: p95 183ms2026-09-16 UTC: p95 290ms2026-09-17 UTC: p95 264ms2026-09-18 UTC: p95 302ms2026-09-19 UTC: p95 376ms2026-09-20 UTC: p95 406ms2026-09-21 UTC: p95 302ms2026-09-22 UTC: p95 354ms2026-09-23 UTC: p95 448ms
Aug 25Sep 8Sep 23
US-West
460msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 568ms2026-08-26 UTC: p95 401ms2026-08-27 UTC: p95 353ms2026-08-28 UTC: p95 411ms2026-08-29 UTC: p95 411ms2026-08-30 UTC: p95 267ms2026-08-31 UTC: p95 318ms2026-09-01 UTC: p95 389ms2026-09-02 UTC: p95 409ms2026-09-03 UTC: p95 316ms2026-09-04 UTC: p95 647ms2026-09-05 UTC: p95 579ms2026-09-06 UTC: p95 650ms2026-09-07 UTC: p95 644ms2026-09-08 UTC: p95 415ms2026-09-09 UTC: p95 208ms2026-09-10 UTC: p95 153ms2026-09-11 UTC: p95 180ms2026-09-12 UTC: p95 153ms2026-09-13 UTC: p95 208ms2026-09-14 UTC: p95 140ms2026-09-15 UTC: p95 459ms2026-09-16 UTC: p95 473ms2026-09-17 UTC: p95 437ms2026-09-18 UTC: p95 435ms2026-09-19 UTC: p95 440ms2026-09-20 UTC: p95 383ms2026-09-21 UTC: p95 407ms2026-09-22 UTC: p95 504ms2026-09-23 UTC: p95 460ms
Aug 25Sep 8Sep 23
Europe
262msp95 · 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-08-25 UTC: p95 424ms2026-08-26 UTC: p95 374ms2026-08-27 UTC: p95 381ms2026-08-28 UTC: p95 304ms2026-08-29 UTC: p95 280ms2026-08-30 UTC: p95 247ms2026-08-31 UTC: p95 349ms2026-09-01 UTC: p95 263ms2026-09-02 UTC: p95 375ms2026-09-03 UTC: p95 429ms2026-09-04 UTC: p95 384ms2026-09-05 UTC: p95 331ms2026-09-06 UTC: p95 387ms2026-09-07 UTC: p95 390ms2026-09-08 UTC: p95 355ms2026-09-09 UTC: p95 490ms2026-09-10 UTC: p95 760ms2026-09-11 UTC: p95 619ms2026-09-12 UTC: p95 491ms2026-09-13 UTC: p95 468ms2026-09-14 UTC: p95 393ms2026-09-15 UTC: p95 270ms2026-09-16 UTC: p95 294ms2026-09-17 UTC: p95 312ms2026-09-18 UTC: p95 300ms2026-09-19 UTC: p95 311ms2026-09-20 UTC: p95 304ms2026-09-21 UTC: p95 345ms2026-09-22 UTC: p95 298ms2026-09-23 UTC: p95 262ms
Aug 25Sep 8Sep 23
Asia-Pacific
694msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 554ms2026-08-26 UTC: p95 779ms2026-08-27 UTC: p95 572ms2026-08-28 UTC: p95 674ms2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 1.1s2026-08-31 UTC: p95 797ms2026-09-01 UTC: p95 688ms2026-09-02 UTC: p95 969ms2026-09-03 UTC: p95 703ms2026-09-04 UTC: p95 303ms2026-09-05 UTC: p95 375ms2026-09-06 UTC: p95 455ms2026-09-07 UTC: p95 489ms2026-09-08 UTC: p95 379ms2026-09-09 UTC: p95 486ms2026-09-10 UTC: p95 530ms2026-09-11 UTC: p95 558ms2026-09-12 UTC: p95 558ms2026-09-13 UTC: p95 512ms2026-09-14 UTC: p95 515ms2026-09-15 UTC: p95 395ms2026-09-16 UTC: p95 636ms2026-09-17 UTC: p95 788ms2026-09-18 UTC: p95 805ms2026-09-19 UTC: p95 766ms2026-09-20 UTC: p95 832ms2026-09-21 UTC: p95 744ms2026-09-22 UTC: p95 802ms2026-09-23 UTC: p95 694ms
Aug 25Sep 8Sep 23
US-Central
539msp95 · 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-03 UTC: p95 456ms2026-09-04 UTC: p95 386ms2026-09-05 UTC: p95 428ms2026-09-06 UTC: p95 464ms2026-09-07 UTC: p95 773ms2026-09-08 UTC: p95 818ms2026-09-09 UTC: p95 544ms2026-09-10 UTC: p95 248ms2026-09-11 UTC: p95 266ms2026-09-12 UTC: p95 632ms2026-09-13 UTC: p95 737ms2026-09-14 UTC: p95 541ms2026-09-15 UTC: p95 577ms2026-09-16 UTC: p95 804ms2026-09-17 UTC: p95 612ms2026-09-18 UTC: p95 503ms2026-09-19 UTC: p95 433ms2026-09-20 UTC: p95 435ms2026-09-21 UTC: p95 467ms2026-09-22 UTC: p95 472ms2026-09-23 UTC: p95 539ms
Aug 25Sep 8Sep 23
Canada
312msp95 · latest
500ms250ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 440ms2026-09-04 UTC: p95 383ms2026-09-05 UTC: p95 377ms2026-09-06 UTC: p95 364ms2026-09-07 UTC: p95 344ms2026-09-08 UTC: p95 287ms2026-09-09 UTC: p95 293ms2026-09-10 UTC: p95 313ms2026-09-11 UTC: p95 375ms2026-09-12 UTC: p95 411ms2026-09-13 UTC: p95 439ms2026-09-14 UTC: p95 395ms2026-09-15 UTC: p95 377ms2026-09-16 UTC: p95 288ms2026-09-17 UTC: p95 230ms2026-09-18 UTC: p95 233ms2026-09-19 UTC: p95 365ms2026-09-20 UTC: p95 391ms2026-09-21 UTC: p95 257ms2026-09-22 UTC: p95 271ms2026-09-23 UTC: p95 312ms
Aug 25Sep 8Sep 23
UK
118msp95 · 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-03 UTC: p95 319ms2026-09-04 UTC: p95 663ms2026-09-05 UTC: p95 663ms2026-09-06 UTC: p95 263ms2026-09-07 UTC: p95 264ms2026-09-08 UTC: p95 213ms2026-09-09 UTC: p95 243ms2026-09-10 UTC: p95 128ms2026-09-11 UTC: p95 117ms2026-09-12 UTC: p95 113ms2026-09-13 UTC: p95 84ms2026-09-14 UTC: p95 70ms2026-09-15 UTC: p95 83ms2026-09-16 UTC: p95 102ms2026-09-17 UTC: p95 150ms2026-09-18 UTC: p95 112ms2026-09-19 UTC: p95 72ms2026-09-20 UTC: p95 86ms2026-09-21 UTC: p95 94ms2026-09-22 UTC: p95 132ms2026-09-23 UTC: p95 118ms
Aug 25Sep 8Sep 23
Southeast Asia
1.2sp95 · 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-03 UTC: p95 683ms2026-09-04 UTC: p95 564ms2026-09-05 UTC: p95 333ms2026-09-06 UTC: p95 844ms2026-09-07 UTC: p95 874ms2026-09-08 UTC: p95 823ms2026-09-09 UTC: p95 867ms2026-09-10 UTC: p95 589ms2026-09-11 UTC: p95 722ms2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 991ms2026-09-14 UTC: p95 826ms2026-09-15 UTC: p95 681ms2026-09-16 UTC: p95 810ms2026-09-17 UTC: p95 706ms2026-09-18 UTC: p95 987ms2026-09-19 UTC: p95 846ms2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.2s
Aug 25Sep 8Sep 23
Australia
1.2sp95 · 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-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 1.4s2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.7s2026-09-09 UTC: p95 1.8s2026-09-10 UTC: p95 1.8s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.2s
Aug 25Sep 8Sep 23
South America
591msp95 · 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-03 UTC: p95 826ms2026-09-04 UTC: p95 909ms2026-09-05 UTC: p95 928ms2026-09-06 UTC: p95 987ms2026-09-07 UTC: p95 775ms2026-09-08 UTC: p95 944ms2026-09-09 UTC: p95 680ms2026-09-10 UTC: p95 858ms2026-09-11 UTC: p95 957ms2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 761ms2026-09-14 UTC: p95 557ms2026-09-15 UTC: p95 919ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 646ms2026-09-18 UTC: p95 526ms2026-09-19 UTC: p95 607ms2026-09-20 UTC: p95 552ms2026-09-21 UTC: p95 550ms2026-09-22 UTC: p95 562ms2026-09-23 UTC: p95 591ms
Aug 25Sep 8Sep 23

Is it Google Maps, 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 Maps -- it cannot diagnose Google Maps'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: 95msstatus code: 200checked: Sep 23, 2026, 9:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Google Maps normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 257msstatus code: 200checked: Sep 23, 2026, 9:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Google Maps normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 417msstatus code: 200checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Google Maps normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 114msstatus code: 200checked: Sep 23, 2026, 9:01 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Google Maps normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 330msstatus code: 200checked: Sep 23, 2026, 9:06 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Google Maps normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 193msstatus code: 200checked: Sep 23, 2026, 9:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Google Maps normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 100msstatus code: 200checked: Sep 23, 2026, 8:54 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Google Maps 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: 104msstatus code: 200checked: Sep 23, 2026, 9:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Google Maps normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 852msstatus code: 200checked: Sep 23, 2026, 8:57 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Google Maps normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1100msstatus code: 200checked: Sep 23, 2026, 8:53 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Google Maps 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 Maps, 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 Maps yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Google Maps.

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

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

Full availability history for Google Maps: 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 Maps, and again when they can reach it again. That is our own measurement from ten regions, not Google Maps'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 Maps uptime measured by RealUptimeLive, from this page's own readings.
[![Google Maps uptime measured by RealUptime](https://realuptime.io/outages/google-maps/badge.svg?days=30)](https://realuptime.io/outages/google-maps)
<a href="https://realuptime.io/outages/google-maps"><img src="https://realuptime.io/outages/google-maps/badge.svg?days=30" alt="Google Maps 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 Maps's SLA implies, from our measurement

At or above your target

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