Skip to content

Outage tracker / Google Maps

Is Google Maps down?

I'm having a problem

Checks passingchecked moments ago

Our checks of Google Maps pass from all 10 regions we check.

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

Front-door and live API checks

Our checks of Google Maps did not fail from two or more distant regions in the 64 days we have checked it (since Aug 8, 2026). This does not show Google Maps works for users.

our check readinglive · checked Oct 11, 2026, 9:33 PM UTC
US-East510 msChecks passing
US-West328 msChecks passing
Europe92 msChecks passing
Asia-Pacific131 msChecks passing
US-Central151 msChecks passing
Canada243 msChecks passing
UK34 msChecks passing
Southeast Asia543 msChecks passing
Australia598 msChecks passing
South America433 msChecks passing
their status pagetheir claim, not our reading

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

Google Maps response time, by region

US-East
496msp95 · 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-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 433ms2026-09-24 UTC: p95 492ms2026-09-25 UTC: p95 570ms2026-09-26 UTC: p95 610ms2026-09-27 UTC: p95 320ms2026-09-28 UTC: p95 346ms2026-09-29 UTC: p95 346ms2026-09-30 UTC: p95 373ms2026-10-01 UTC: p95 548ms2026-10-02 UTC: p95 415ms2026-10-03 UTC: p95 543ms2026-10-04 UTC: p95 492ms2026-10-05 UTC: p95 580ms2026-10-06 UTC: p95 586ms2026-10-07 UTC: p95 589ms2026-10-08 UTC: p95 563ms2026-10-09 UTC: p95 456ms2026-10-10 UTC: p95 483ms2026-10-11 UTC: p95 496ms
Sep 12Sep 26Oct 11
US-West
501msp95 · 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-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 372ms2026-09-24 UTC: p95 301ms2026-09-25 UTC: p95 437ms2026-09-26 UTC: p95 411ms2026-09-27 UTC: p95 180ms2026-09-28 UTC: p95 320ms2026-09-29 UTC: p95 323ms2026-09-30 UTC: p95 437ms2026-10-01 UTC: p95 528ms2026-10-02 UTC: p95 488ms2026-10-03 UTC: p95 339ms2026-10-04 UTC: p95 508ms2026-10-05 UTC: p95 608ms2026-10-06 UTC: p95 426ms2026-10-07 UTC: p95 472ms2026-10-08 UTC: p95 509ms2026-10-09 UTC: p95 445ms2026-10-10 UTC: p95 479ms2026-10-11 UTC: p95 501ms
Sep 12Sep 26Oct 11
Europe
316msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-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 236ms2026-09-24 UTC: p95 250ms2026-09-25 UTC: p95 329ms2026-09-26 UTC: p95 273ms2026-09-27 UTC: p95 275ms2026-09-28 UTC: p95 288ms2026-09-29 UTC: p95 230ms2026-09-30 UTC: p95 184ms2026-10-01 UTC: p95 150ms2026-10-02 UTC: p95 164ms2026-10-03 UTC: p95 180ms2026-10-04 UTC: p95 260ms2026-10-05 UTC: p95 165ms2026-10-06 UTC: p95 177ms2026-10-07 UTC: p95 190ms2026-10-08 UTC: p95 250ms2026-10-09 UTC: p95 197ms2026-10-10 UTC: p95 200ms2026-10-11 UTC: p95 316ms
Sep 12Sep 26Oct 11
Asia-Pacific
425msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-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 554ms2026-09-24 UTC: p95 324ms2026-09-25 UTC: p95 351ms2026-09-26 UTC: p95 718ms2026-09-27 UTC: p95 821ms2026-09-28 UTC: p95 623ms2026-09-29 UTC: p95 585ms2026-09-30 UTC: p95 627ms2026-10-01 UTC: p95 462ms2026-10-02 UTC: p95 428ms2026-10-03 UTC: p95 456ms2026-10-04 UTC: p95 489ms2026-10-05 UTC: p95 352ms2026-10-06 UTC: p95 368ms2026-10-07 UTC: p95 379ms2026-10-08 UTC: p95 446ms2026-10-09 UTC: p95 462ms2026-10-10 UTC: p95 421ms2026-10-11 UTC: p95 425ms
Sep 12Sep 26Oct 11
US-Central
310msp95 · 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-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 488ms2026-09-24 UTC: p95 629ms2026-09-25 UTC: p95 310ms2026-09-26 UTC: p95 412ms2026-09-27 UTC: p95 577ms2026-09-28 UTC: p95 606ms2026-09-29 UTC: p95 236ms2026-09-30 UTC: p95 473ms2026-10-01 UTC: p95 371ms2026-10-02 UTC: p95 286ms2026-10-03 UTC: p95 239ms2026-10-04 UTC: p95 307ms2026-10-05 UTC: p95 245ms2026-10-06 UTC: p95 276ms2026-10-07 UTC: p95 365ms2026-10-08 UTC: p95 226ms2026-10-09 UTC: p95 285ms2026-10-10 UTC: p95 201ms2026-10-11 UTC: p95 310ms
Sep 12Sep 26Oct 11
Canada
456msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-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 299ms2026-09-24 UTC: p95 320ms2026-09-25 UTC: p95 568ms2026-09-26 UTC: p95 531ms2026-09-27 UTC: p95 497ms2026-09-28 UTC: p95 338ms2026-09-29 UTC: p95 389ms2026-09-30 UTC: p95 364ms2026-10-01 UTC: p95 458ms2026-10-02 UTC: p95 336ms2026-10-03 UTC: p95 293ms2026-10-04 UTC: p95 505ms2026-10-05 UTC: p95 800ms2026-10-06 UTC: p95 770ms2026-10-07 UTC: p95 710ms2026-10-08 UTC: p95 523ms2026-10-09 UTC: p95 512ms2026-10-10 UTC: p95 544ms2026-10-11 UTC: p95 456ms
Sep 12Sep 26Oct 11
UK
133msp95 · 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-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 129ms2026-09-24 UTC: p95 130ms2026-09-25 UTC: p95 137ms2026-09-26 UTC: p95 336ms2026-09-27 UTC: p95 447ms2026-09-28 UTC: p95 421ms2026-09-29 UTC: p95 467ms2026-09-30 UTC: p95 550ms2026-10-01 UTC: p95 198ms2026-10-02 UTC: p95 233ms2026-10-03 UTC: p95 221ms2026-10-04 UTC: p95 169ms2026-10-05 UTC: p95 144ms2026-10-06 UTC: p95 154ms2026-10-07 UTC: p95 232ms2026-10-08 UTC: p95 179ms2026-10-09 UTC: p95 150ms2026-10-10 UTC: p95 117ms2026-10-11 UTC: p95 133ms
Sep 12Sep 26Oct 11
Southeast Asia
509msp95 · 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-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.1s2026-09-24 UTC: p95 690ms2026-09-25 UTC: p95 960ms2026-09-26 UTC: p95 704ms2026-09-27 UTC: p95 830ms2026-09-28 UTC: p95 766ms2026-09-29 UTC: p95 660ms2026-09-30 UTC: p95 528ms2026-10-01 UTC: p95 488ms2026-10-02 UTC: p95 449ms2026-10-03 UTC: p95 527ms2026-10-04 UTC: p95 516ms2026-10-05 UTC: p95 530ms2026-10-06 UTC: p95 480ms2026-10-07 UTC: p95 505ms2026-10-08 UTC: p95 527ms2026-10-09 UTC: p95 558ms2026-10-10 UTC: p95 526ms2026-10-11 UTC: p95 509ms
Sep 12Sep 26Oct 11
Australia
1.0sp95 · 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-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.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 944ms2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 944ms2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 961ms2026-10-09 UTC: p95 864ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.0s
Sep 12Sep 26Oct 11
South America
1.0sp95 · 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-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 795ms2026-09-24 UTC: p95 806ms2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 926ms2026-09-28 UTC: p95 820ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 857ms2026-10-01 UTC: p95 700ms2026-10-02 UTC: p95 796ms2026-10-03 UTC: p95 886ms2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 964ms2026-10-06 UTC: p95 663ms2026-10-07 UTC: p95 837ms2026-10-08 UTC: p95 724ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 908ms2026-10-11 UTC: p95 1.0s
Sep 12Sep 26Oct 11

Check your own site while you wait on Google Maps

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.

Get an email when our checks of Google Maps fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Google Maps fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Google Maps's official status.

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
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 510msstatus code: 200checked: Oct 11, 2026, 9:29 PM 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
      Checks passinglatency: 328msstatus code: 200checked: Oct 11, 2026, 9:27 PM 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
      Checks passinglatency: 151msstatus code: 200checked: Oct 11, 2026, 9:33 PM 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
      Checks passinglatency: 243msstatus code: 200checked: Oct 11, 2026, 9:25 PM 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
    Checks passinglatency: 433msstatus code: 200checked: Oct 11, 2026, 9:20 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 92msstatus code: 200checked: Oct 11, 2026, 9:31 PM 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
      Checks passinglatency: 34msstatus code: 200checked: Oct 11, 2026, 9:25 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 131msstatus code: 200checked: Oct 11, 2026, 9:29 PM 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
      Checks passinglatency: 543msstatus code: 200checked: Oct 11, 2026, 9:22 PM 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
      Checks passinglatency: 598msstatus code: 200checked: Oct 11, 2026, 9:22 PM 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 started counting reports for Google Maps on September 24, 2026.

Recent probe events

No probe events on record yet for Google Maps.

check 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 check readings and Google Maps's own claim at the time, side by side.

Full check history for Google Maps: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Put this badge in your README

Google Maps uptime by RealUptime's checksLive, from this page's own readings.
[![Google Maps uptime by RealUptime's checks](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 by RealUptime's checks"></a>

The badge shows the share of our checks that passed 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 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.

How our checks compare with Google Maps's stated SLA

At or above your target

Our checks of Google Maps failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: maps.googleapis.com

RealUptime is not affiliated with Google Maps; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.