Skip to content

Outage tracker / Google Maps

Is Google Maps down?

I'm having a problem

Vendor reports no incidentWhat Google Maps reports

Google Maps reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:39 UTC.

Google Maps's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

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

As of Nov 5, 2026, 3:42 PM UTC, RealUptime's checks of Google Maps passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:42 PM UTC
US-East701 msChecks passing
US-West175 msChecks passing
Europe269 msChecks passing
Asia-Pacific1136 msChecks passing
US-Central1044 msChecks passing
Canada513 msChecks passing
UK398 msChecks passing
Southeast Asia1817 msChecks passing
Australia1408 msChecks passing
South America1723 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
1.9sp95 · 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-10-07 UTC: p95 589ms2026-10-08 UTC: p95 563ms2026-10-09 UTC: p95 456ms2026-10-10 UTC: p95 483ms2026-10-11 UTC: p95 503ms2026-10-12 UTC: p95 502ms2026-10-13 UTC: p95 719ms2026-10-14 UTC: p95 545ms2026-10-15 UTC: p95 531ms2026-10-16 UTC: p95 538ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 951ms2026-11-04 UTC: p95 778ms2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
US-West
1.4sp95 · 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-10-07 UTC: p95 472ms2026-10-08 UTC: p95 509ms2026-10-09 UTC: p95 445ms2026-10-10 UTC: p95 479ms2026-10-11 UTC: p95 482ms2026-10-12 UTC: p95 470ms2026-10-13 UTC: p95 458ms2026-10-14 UTC: p95 573ms2026-10-15 UTC: p95 531ms2026-10-16 UTC: p95 436ms2026-10-17 UTC: p95 867ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Europe
709msp95 · 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-10-07 UTC: p95 190ms2026-10-08 UTC: p95 250ms2026-10-09 UTC: p95 197ms2026-10-10 UTC: p95 200ms2026-10-11 UTC: p95 289ms2026-10-12 UTC: p95 310ms2026-10-13 UTC: p95 132ms2026-10-14 UTC: p95 178ms2026-10-15 UTC: p95 164ms2026-10-16 UTC: p95 116ms2026-10-17 UTC: p95 575ms2026-10-18 UTC: p95 706ms2026-10-19 UTC: p95 692ms2026-10-20 UTC: p95 540ms2026-10-21 UTC: p95 487ms2026-10-22 UTC: p95 456ms2026-10-23 UTC: p95 627ms2026-10-24 UTC: p95 525ms2026-10-25 UTC: p95 627ms2026-10-26 UTC: p95 971ms2026-10-27 UTC: p95 712ms2026-10-28 UTC: p95 395ms2026-10-29 UTC: p95 395ms2026-10-30 UTC: p95 466ms2026-10-31 UTC: p95 448ms2026-11-01 UTC: p95 477ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 819ms2026-11-04 UTC: p95 877ms2026-11-05 UTC: p95 709ms
Oct 7Oct 21Nov 5
Asia-Pacific
1.2sp95 · 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-10-07 UTC: p95 379ms2026-10-08 UTC: p95 446ms2026-10-09 UTC: p95 462ms2026-10-10 UTC: p95 421ms2026-10-11 UTC: p95 425ms2026-10-12 UTC: p95 401ms2026-10-13 UTC: p95 343ms2026-10-14 UTC: p95 450ms2026-10-15 UTC: p95 437ms2026-10-16 UTC: p95 417ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.8s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
US-Central
1.3sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 365ms2026-10-08 UTC: p95 226ms2026-10-09 UTC: p95 285ms2026-10-10 UTC: p95 201ms2026-10-11 UTC: p95 316ms2026-10-12 UTC: p95 372ms2026-10-13 UTC: p95 307ms2026-10-14 UTC: p95 443ms2026-10-15 UTC: p95 421ms2026-10-16 UTC: p95 354ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 839ms2026-10-25 UTC: p95 854ms2026-10-26 UTC: p95 995ms2026-10-27 UTC: p95 858ms2026-10-28 UTC: p95 999ms2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 884ms2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 902ms2026-11-03 UTC: p95 941ms2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Canada
1.0sp95 · 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-10-07 UTC: p95 710ms2026-10-08 UTC: p95 523ms2026-10-09 UTC: p95 512ms2026-10-10 UTC: p95 544ms2026-10-11 UTC: p95 455ms2026-10-12 UTC: p95 517ms2026-10-13 UTC: p95 497ms2026-10-14 UTC: p95 363ms2026-10-15 UTC: p95 379ms2026-10-16 UTC: p95 432ms2026-10-17 UTC: p95 860ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 752ms2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
UK
651msp95 · 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-10-07 UTC: p95 232ms2026-10-08 UTC: p95 179ms2026-10-09 UTC: p95 150ms2026-10-10 UTC: p95 117ms2026-10-11 UTC: p95 141ms2026-10-12 UTC: p95 141ms2026-10-13 UTC: p95 150ms2026-10-14 UTC: p95 288ms2026-10-15 UTC: p95 71ms2026-10-16 UTC: p95 176ms2026-10-17 UTC: p95 567ms2026-10-18 UTC: p95 791ms2026-10-19 UTC: p95 809ms2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 663ms2026-10-22 UTC: p95 700ms2026-10-23 UTC: p95 890ms2026-10-24 UTC: p95 889ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 993ms2026-10-27 UTC: p95 943ms2026-10-28 UTC: p95 742ms2026-10-29 UTC: p95 680ms2026-10-30 UTC: p95 626ms2026-10-31 UTC: p95 834ms2026-11-01 UTC: p95 860ms2026-11-02 UTC: p95 687ms2026-11-03 UTC: p95 821ms2026-11-04 UTC: p95 748ms2026-11-05 UTC: p95 651ms
Oct 7Oct 21Nov 5
Southeast Asia
3.1sp95 · 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-10-07 UTC: p95 505ms2026-10-08 UTC: p95 527ms2026-10-09 UTC: p95 558ms2026-10-10 UTC: p95 526ms2026-10-11 UTC: p95 524ms2026-10-12 UTC: p95 401ms2026-10-13 UTC: p95 882ms2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 873ms2026-10-16 UTC: p95 802ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 2.2s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 3.2s2026-11-05 UTC: p95 3.1s
Oct 7Oct 21Nov 5
Australia
2.1sp95 · 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-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.0s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 3.2s2026-10-18 UTC: p95 3.1s2026-10-19 UTC: p95 2.9s2026-10-20 UTC: p95 3.5s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.4s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 2.2s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
South America
3.2sp95 · latest
20s10s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 20s. Days with no samples are not plotted, not shown as zero.2026-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 994ms2026-10-12 UTC: p95 997ms2026-10-13 UTC: p95 980ms2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 3.2s2026-10-23 UTC: p95 11.5s2026-10-24 UTC: p95 2.4s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.2s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5

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.

What we measured, function by function

Google Maps answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Google MapsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Map tilesUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Maps JavaScript APIUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Google Maps reports an incident on its status page, and again when it reports it resolved.

Get an email when Google Maps reports an incident

Email me when Google Maps reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Google Maps's own statement from its status page, with our regional reading beside it.

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: 701msstatus code: 200checked: Nov 5, 2026, 3:41 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: 175msstatus code: 200checked: Nov 5, 2026, 3:42 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: 1044msstatus code: 200checked: Nov 5, 2026, 3:37 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: 513msstatus code: 200checked: Nov 5, 2026, 3:41 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: 1723msstatus code: 200checked: Nov 5, 2026, 3:34 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: 269msstatus code: 200checked: Nov 5, 2026, 3:29 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: 398msstatus code: 200checked: Nov 5, 2026, 3:35 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: 1136msstatus code: 200checked: Nov 5, 2026, 3:28 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: 1817msstatus code: 200checked: Nov 5, 2026, 3:36 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: 1408msstatus code: 200checked: Nov 5, 2026, 3:37 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

Incomplete and/or incorrectly localized addresses for some street results, 197h 55mdeclared on their status page2026-10-25
Between 2026-10-22 19:40 and 21:42 US/Pacific, reverse-geocoding requests sent to the Geocoding API resolved to an address in Vietnam, for input coordinates far away from that location., 2h 2mdeclared on their status page2026-10-23
Elevated error rates and latency for Directions, Distance Matrix and Routes APIs, 1h 44mdeclared on their status page2026-10-19
[Maps SDK] Fatal Exception: m140.fqd: GL context is unusable again / glLinkProgram failed "GVI && cannot compute gv size for oob" on Qualcomm Adreno GPUs (maps_core_dynamite v263020506), 22h 31mdeclared on their status page2026-09-28
We've received a report of an issue with Google Maps Platform - Traffic Layer and Live traffic data., 9h 23mdeclared on their status page2026-07-27
Address Validation API rejecting some requests with 403, 1h 33mdeclared on their status page2026-04-07
Current Production Issue - Google Maps Platform, 6hdeclared on their status page2026-03-18
We are investigating a potential issue with Google Maps Platform routing/directions APIs, 4h 21mdeclared on their status page2026-03-11

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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

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" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Google Maps down?", https://realuptime.io/outages/google-maps. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://maps.googleapis.com/maps/api/geocode/json?address=test
secondary
https://maps.google.com/robots.txt
secondary
https://maps.googleapis.com/maps/api/js
secondary
https://mt0.google.com/vt/lyrs=m&x=0&y=0&z=0
secondary
https://www.google.com/maps

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.