Google Maps Platform Outage History

Started Oct 25, 2026, 12:00 PM UTC· resolved Nov 02, 2026, 05:54 PM UTC

1. monitoring Oct 26, 2026, 10:01 AM UTC

   Summary: Incomplete and/or incorrectly localized addresses for some street results Description: Starting October 25, 2026 at around 05:00 PT, some requests to the Geocoding API (all platforms), Places API Legacy & New (all platforms) and Address Validation API may return incomplete or incorrectly formatted address information for street-level results. Affected responses may be missing address components such as city, region, postal code or country. They may also return street names in an unexpected language or with incorrect address formatting, and may be flagged as partial matches. Results may vary between requests. Unexpectedly empty responses may be returned for street searches and queries. Our engineering team has identified the root-cause and is working on a mitigation. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

2. monitoring Oct 26, 2026, 10:58 AM UTC

   Summary: Incomplete and/or incorrectly localized addresses for some street results Description: We are experiencing an issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS beginning at Sunday, 2026-10-25 05:00 PDT. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2026-10-26 05:00 PDT with current details. We apologize to all who are affected by the disruption. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

3. monitoring Oct 26, 2026, 11:53 AM UTC

   Summary: Incomplete and/or incorrectly localized addresses for some street results Description: Mitigation work is currently underway by our engineering team. We will provide more information by Monday, 2026-10-26 08:00 PDT. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

4. monitoring Oct 26, 2026, 02:57 PM UTC

   Summary: Incomplete and/or incorrectly localized addresses for some street results Description: Our Engineering Team has identified the root cause of the issue and mitigation work is underway. The issue was triggered by a recent map data update that omitted certain regional and administrative relationships for street addresses. Engineering has stopped further updates from this pipeline and is rolling back the change while regenerating corrected datasets in parallel. Because the data restoration requires multi-stage processing and verification across our serving systems, the mitigation is expected to take several hours to fully complete. We will provide more information by Monday, 2026-10-26 10:00 PDT. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

5. monitoring Oct 26, 2026, 04:34 PM UTC

   Summary: Incomplete and/or incorrectly localized addresses for some street results Description: Our Engineering Team has identified the root cause of the issue and mitigation work is underway. The issue was triggered by a recent map data update that omitted certain regional and administrative relationships for street addresses. Engineering has stopped further updates from this pipeline and is rolling back the change while regenerating corrected datasets in parallel. Because the data restoration requires multi-stage processing and verification across our serving systems, the mitigation is expected to take several hours to fully complete. We will provide more information by Monday, 2026-10-26 11:00 PDT. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

6. monitoring Oct 26, 2026, 06:07 PM UTC

   Summary: Incomplete and/or incorrectly localized addresses for some street results Description: Our Engineering Team has identified the root cause of the corrupted data issue and mitigation work to roll back the change and regenerate corrected datasets is in progress. The data restoration requires multi-stage processing and verification across our serving systems. The mitigation is expected to take several hours to fully complete. We will provide more information by Monday, 2026-10-26 13:30 PDT. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

7. monitoring Oct 26, 2026, 08:09 PM UTC

   Summary: Incomplete and/or incorrectly localized addresses for some street results Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Monday, 2026-10-26 14:40 PDT. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

8. monitoring Oct 26, 2026, 09:56 PM UTC

   Summary: Incomplete and/or incorrectly localized addresses for some street results Description: The mitigation work to roll back to the corrected dataset in our data respositories was completed. Those changes will take additional time now to be picked up by our indexing and serving systems. While we are already seeing a drop in degraded results where response has missing address components, the fix will take additional time to fully propagate to all services. We will provide more information by Monday, 2026-10-26 16:45 PDT. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

9. monitoring Oct 27, 2026, 12:13 AM UTC

   Summary: Incomplete and/or incorrectly localized addresses for some street results Description: The resolution of the issue is still underway. We're seeing rate of degraded results such as missing address components and wrong localization return to pre-outage levels for Geocoding and Places API. We are continuing to track the progress of the data propagation across services and will provide an update by Monday, 2026-10-26 19:00:00 PDT. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

10. monitoring Oct 27, 2026, 01:51 AM UTC

    Summary: Incomplete and/or incorrectly localized addresses for some street results Description: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is partially resolved. We do not have an ETA for full resolution at this point. We will provide an update by Monday, 2026-10-26 23:00 PDT with current details. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

11. monitoring Oct 27, 2026, 04:53 AM UTC

    Summary: Incomplete and/or incorrectly localized addresses for some street results Description: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is now mostly resolved. Our engineering team continues to closely monitor the services to address any remaining edge cases. We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2026-10-27 11:00 PDT with current details. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

12. monitoring Oct 27, 2026, 02:27 PM UTC

    Summary: Incomplete and/or incorrectly localized addresses for some street results Description: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is mostly resolved globally. However, we still observe a small number of impacted features, primarily in the geographical regions of Taiwan, Brazil, Vietnam, Colombia and Singapore. We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2026-10-27 10:00 PDT with current details. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

13. monitoring Oct 27, 2026, 04:58 PM UTC

    Summary: Incomplete and/or incorrectly localized addresses for some street results Description: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is resolved. Recovery has completed across previously affected regions, including Taiwan, Brazil, Vietnam, Colombia, and Singapore. Our engineering team is verifying data restoration for a small remaining subset of road features before closing this incident. We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2026-10-27 11:00 PDT with current details. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

14. monitoring Oct 27, 2026, 07:07 PM UTC

    Summary: Incomplete and/or incorrectly localized addresses for some street results Description: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is resolved for the vast majority of traffic. Recovery has completed across previously affected regions, including Taiwan, Brazil, Vietnam, Colombia, and Singapore. Our engineering team is completing final data restoration and verification for a small remaining subset of road features before closing this incident. We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2026-10-27 14:00 PDT with current details. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time. Diagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results Workaround: None at this time.

15. monitoring Oct 28, 2026, 09:10 PM UTC

    Summary: Incomplete and/or incorrectly localized addresses for some street results Description: Our engineering team has completed the rollback of the remaining affected road features, and updated map data has propagated across our production serving systems. We are performing final verification of our automated data pipelines before resolving this incident. We will provide an update by Thursday, 2026-10-29 12:00 PDT. Diagnosis: Customers using Directions API, Routes API, Distance Matrix API, and Navigation SDK may have experienced degraded route quality, suboptimal detours, or missing road segments in multiple regions, including Taiwan, Brazil, Vietnam, Colombia, and Singapore. Workaround: None at this time.

16. monitoring Oct 29, 2026, 07:27 PM UTC

    Summary: Incomplete and/or incorrectly localized addresses for some street results Description: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is partially resolved. While we believe user impact has been resolved, internal processes and procedures remain paused while Google applies the fixes that will allow their resumption. We do not have an ETA for full resolution at this point. We will provide an update by Thursday, 2026-10-29 19:00 PDT with current details. Diagnosis: Customers using Directions API, Routes API, Distance Matrix API, and Navigation SDK may have experienced degraded route quality, suboptimal detours, or missing road segments in multiple regions, including Taiwan, Brazil, Vietnam, Colombia, and Singapore. Workaround: None at this time.

17. monitoring Oct 30, 2026, 03:40 AM UTC

    Summary: Incomplete and/or incorrectly localized addresses for some street results Description: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is resolved. Our engineering team is completing final data restoration and verification before closing this incident. We will provide an update by Friday, 2026-10-30 15:00 PDT with current details. Diagnosis: No ongoing symptoms detected. Workaround: None at this time.

18. monitoring Oct 30, 2026, 09:44 PM UTC

    Summary: Incomplete and/or incorrectly localized addresses for some street results Description: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is resolved. Our engineering team is completing final data restoration and verification before closing this incident. We will provide an update by Friday, 2026-10-30 16:30 PDT with current details. Diagnosis: No ongoing symptoms detected. Workaround: None at this time.

19. monitoring Oct 30, 2026, 11:21 PM UTC

    Summary: Incomplete and/or incorrectly localized addresses for some street results Description: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is resolved. Our engineering team is completing final data restoration and verification before closing this incident. We will provide an update by Monday, 2026-11-02 10:30 PDT with current details. Diagnosis: No ongoing symptoms detected. Workaround: None at this time.

20. resolved Nov 02, 2026, 05:54 PM UTC

    The issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS has been resolved for all affected users as of Friday, 2026-10-30 15:45 PDT. We will publish an analysis of this incident once we have completed our internal investigation. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Oct 23, 2026, 02:40 AM UTC· resolved Oct 23, 2026, 04:42 AM UTC

1. resolved Oct 25, 2026, 02:39 PM UTC

   Google Engineering mitigated this issue with a rollback in the reverse geocoding serving stack.

2. resolved Nov 02, 2026, 08:04 PM UTC

   An Incident Report for the service degradation affecting the Geocoding API on October 22, 2026 is now available. For a detailed analysis of the event, including the root cause and our prevention measures, please view the published Incident Report on the Public Issue Tracker here: https://issuetracker.google.com/issues/576897533

Read the full incident report →

Started Oct 19, 2026, 06:56 PM UTC· resolved Oct 19, 2026, 08:40 PM UTC

1. resolved Oct 20, 2026, 04:40 AM UTC

   Elevated error rates and latency for Directions, Distance Matrix and Routes APIs. The issue has been resolved for all affected projects as of Monday, 2026-10-19 13:40 PDT.

Read the full incident report →

Started Sep 28, 2026, 04:52 PM UTC· resolved Sep 29, 2026, 03:23 PM UTC

1. monitoring Sep 28, 2026, 06:56 PM UTC

   Summary: [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) Description: We are also posting this incident to the Google Maps Platform Status Dashboard (https://status.cloud.google.com/maps-platform/ ) while the fix rolls out. Based on our telemetry, this issue affects up to 0.15% of Maps SDK map loads in impacted apps, though the rate varies significantly depending on each app's device GPU distribution (Qualcomm Adreno 6xx/7xx). Diagnosis: A shader linking error crashes the host app as soon as a Google Map is loaded. Workaround: None at this time.

2. monitoring Sep 29, 2026, 08:21 AM UTC

   Summary: [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) Description: Our engineering team has identified the root cause of the crash spike. It was triggered by an unexpected interaction between a recent Android WebView configuration update and the Maps SDK on devices with Qualcomm Adreno 6xx/7xx GPUs. We have successfully initiated a server-side rollback of this WebView configuration. The safe configuration is currently deploying globally. Because Android WebView fetches configuration updates in the background, affected devices will recover automatically as they sync the updated configuration over the network. We are actively monitoring the rollout of this mitigation and will provide another update once it has further progressed. Diagnosis: A shader linking error crashes the host app as soon as a Google Map is loaded. Workaround: For end users who are currently experiencing persistent crashes and require immediate relief, clearing the host app's storage will force a fresh fetch of the safe configuration and break the crash loop. Please note that clearing the app cache alone is ineffective; it requires clearing the app storage (which will reset local app data).

3. monitoring Sep 29, 2026, 11:42 AM UTC

   Summary: [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) Description: The server-side rollback of the Android WebView configuration has reached 100% global deployment. We are currently monitoring telemetry to verify the impact as affected devices begin to sync the safe configuration over the network. Because Android WebView fetches these updates in the background, client recovery is expected to occur gradually over the coming hours and days. We will keep this incident open and provide another update once we can confirm a reduction in crash volumes across the ecosystem. Diagnosis: A shader linking error crashes the host app as soon as a Google Map is loaded. Workaround: For end users who are currently experiencing persistent crashes and require immediate relief, clearing the host app's storage will force a fresh fetch of the safe configuration and break the crash loop. Please note that clearing the app cache alone is ineffective; it requires clearing the app storage (which will reset local app data).

4. resolved Sep 29, 2026, 03:23 PM UTC

   The issue with Maps SDK for Android, Navigation SDK has been resolved for all affected users as of Tuesday, 2026-09-29 00:00 PDT. However due to caching of feature flags we expect to continue to see sparse crash reports for a few days. We will publish an analysis of this incident once we have completed our internal investigation. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Jul 27, 2026, 05:38 AM UTC· resolved Jul 27, 2026, 03:01 PM UTC

1. investigating Jul 27, 2026, 09:36 AM UTC

   We are experiencing an issue with APIs that can display live traffic data (Traffic Layer) or use live traffic data (such as Directions, Distance Matrix, Routes, Routes Preferred, Roads Management Insights) beginning at Sunday, 2026-07-26 22:38 PDT. Please follow updates from https://issuetracker.google.com/issues/539397397. Symptoms: Traffic Layer unavailable or largely degraded, live traffic information unavailable for direction calculations. No error rate increase or latency increase. Our engineering team continues to investigate the issue and has a mitigation underway. We apologize to all who are affected by the disruption.

2. investigating Jul 27, 2026, 10:55 AM UTC

   The mitigation is underway. We have no ETA to communicate at this stage and will provide a status update as soon as possible.

3. resolved Jul 27, 2026, 05:28 PM UTC

   Issue is fully mitigated as of 2026-07-27 08:01 PDT

Read the full incident report →

Started Apr 07, 2026, 07:04 PM UTC· resolved Apr 07, 2026, 08:37 PM UTC

1. resolved Apr 07, 2026, 10:58 PM UTC

   Address Validation API rejecting some requests with 403.

Read the full incident report →

Started Mar 18, 2026, 03:13 PM UTC· resolved Mar 18, 2026, 09:13 PM UTC

1. resolved Mar 18, 2026, 06:49 PM UTC

   We are experiencing an elevated level of 5xx errors and elevated latency for Google Maps Platform, Geocoding API (Reverse Geocoding), Places/Places(New) NearbySearch beginning at Wednesday, 2026-03-18 08:13 PDT.

Read the full incident report →

Started Mar 11, 2026, 11:51 AM UTC· resolved Mar 11, 2026, 04:11 PM UTC

1. monitoring Mar 11, 2026, 01:04 PM UTC

   Summary: We are investigating a potential issue with Google Maps Platform Routes API Description: We are experiencing an issue with Google Maps Platform, Routes API beginning at Wednesday, 2026-03-11 04:51 PDT. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-03-11 06:35 PDT with current details. We apologize to all who are affected by the disruption. Diagnosis: Elevated latency and error rates Workaround: Retry failing requests; emit requests away from sources in the JAPAC region; use other routing API

2. monitoring Mar 11, 2026, 01:24 PM UTC

   Summary: We are investigating a potential issue with Google Maps Platform routing/directions APIs Description: Mitigation work is still underway by our engineering team. Current data indicates that up to 2% of requests in JAPAC are affected by this issue. The mitigation started at 2026-03-11 06:15:00 PDT. We will provide more information by Wednesday, 2026-03-11 08:00 PDT. Diagnosis: Elevated latency and error rates Workaround: Retry failing requests; emit requests away from sources in the JAPAC region

3. monitoring Mar 11, 2026, 02:58 PM UTC

   Summary: We are investigating a potential issue with Google Maps Platform routing/directions APIs Description: We believe the issue with Google Maps Platform, Distance Matrix API, Routes API, Directions API is almost entirely resolved since 07:15 PT. We do not have an ETA for full resolution at this point. We will provide an update by Wednesday, 2026-03-11 10:00 PDT with current details. Diagnosis: Elevated latency and error rates Workaround: Retry failing requests; emit requests away from sources in the JAPAC region

4. resolved Mar 11, 2026, 04:11 PM UTC

   The issue with Google Maps Platform, Distance Matrix API, Routes API, Directions API has been resolved for all affected projects. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Feb 25, 2026, 10:00 AM UTC· resolved Feb 26, 2026, 10:07 PM UTC

1. monitoring Feb 25, 2026, 11:51 PM UTC

   Summary: Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API Description: We believe the issue with Google Maps Platform, Geocoding API, Places API, Places API (New), Roads API is partially resolved. We do not have an ETA for full resolution at this point. We will provide an update by Wednesday, 2026-02-25 16:50 PST with current details. Diagnosis: 5xx errors and elevated p90, p99 latency Workaround: Retry a failed request

2. monitoring Feb 26, 2026, 01:16 AM UTC

   Summary: Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API Description: We believe the issue with Google Maps Platform, Geocoding API, Places API, Places API (New), Roads API is partially resolved. Full resolution is expected to complete by Thursday, 2026-02-26 09:00 PST. Google Engineers have drained some affected datacenters, but there is another which is still in the process of being mitigated. The level of 5xx errors is reduced, but some customers may still experience elevated latency due to non-optimal routing. Impacted region: North America. We will provide an update by Wednesday, 2026-02-25 20:00 PST with current details. Diagnosis: 5xx errors and elevated p90, p99 latency Workaround: Retry a failed request

3. monitoring Feb 26, 2026, 04:00 AM UTC

   Summary: Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API Description: The affected datacenters are still drained, and error rates are stabilized across services. Google Engineers are investigating the root cause for this incident. Will will provide an update by Wednesday, 2026-02-25 22:00 PST with current details. Diagnosis: 5xx errors and elevated p90, p99 latency Workaround: Retry a failed request

4. monitoring Feb 26, 2026, 06:01 AM UTC

   Summary: Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API Description: Mitigation work is still underway by our engineering team. The affected datacenters are still drained, and error rates are stabilized across services. The mitigation is expected to complete by Thursday, 2026-02-26 09:00 PST. We will provide more information by Thursday, 2026-02-26 05:00 PST. Diagnosis: 5xx errors and elevated p90, p99 latency Workaround: Retry a failed request

5. monitoring Feb 26, 2026, 11:16 AM UTC

   Summary: Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API Description: We believe the issue with Google Maps Platform, Geocoding API, Places API, Places API (New), Roads API is resolved for the most part. We will provide a final update by Thursday, 2026-02-26 10:00 PST. Diagnosis: 5xx errors and elevated p90, p99 latency Workaround: Retry a failed request

6. monitoring Feb 26, 2026, 06:46 PM UTC

   Summary: Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API Description: We are observing another spike of 5xx errors started at 2026-02-26 ~08:00 PST. The investigation into the most recent occurrence is ongoing, and Google Engineers have initiated the process of undraining the affected data centers. We do not have an ETA for full resolution at this point. We will provide an update by Thursday, 2026-02-26 14:00 PST with current details. Diagnosis: 5xx errors and elevated p90, p99 latency Workaround: Retry a failed request

7. resolved Feb 26, 2026, 10:07 PM UTC

   The issue with Google Maps Platform, Geocoding API, Places API, Places API (New), Roads API has been resolved for all affected projects as of Thursday, 2026-02-26 13:26 PST. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Feb 22, 2026, 08:53 AM UTC· resolved Feb 22, 2026, 07:00 PM UTC

1. monitoring Feb 22, 2026, 11:45 AM UTC

   Summary: Elevated error rate on Places API Description: We are experiencing an issue with Google Maps Platform, Places API beginning at Sunday, 2026-02-22 00:53 PST. Our engineering team continues to investigate the issue. We will provide an update by Sunday, 2026-02-22 04:15 PST with current details. We apologize to all who are affected by the disruption. Diagnosis: Increase in 500 errors Workaround: None at this time.

2. monitoring Feb 22, 2026, 01:00 PM UTC

   Summary: Elevated error rate on Places API Description: Error rates have subsided, as mitigation work is still underway by our engineering team. We will provide more information by Sunday, 2026-02-22 09:00 PST. Diagnosis: Increase in 500 errors Workaround: None at this time.

3. resolved Feb 22, 2026, 07:00 PM UTC

   The issue with Google Maps Places API has been resolved for all affected users as of Sunday, 2026-02-22 10:40 PST. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Feb 08, 2026, 04:39 AM UTC· resolved Feb 08, 2026, 10:05 PM UTC

1. monitoring Feb 08, 2026, 11:46 AM UTC

   Summary: Potential issue with Google Maps Platform Maps SDK on Android Description: We are investigating a potential issue with Maps SDK for Android, Maps SDK for iOS, Navigation SDK. We will provide more information by Sunday, 2026-02-08 04:15 PST. Diagnosis: Slower app startup and/or maps using a stale rendering configuration. Workaround: None at this time.

2. monitoring Feb 08, 2026, 12:08 PM UTC

   Summary: Potential issue with Google Maps Platform Maps SDK on Android Description: While our engineering team continues to investigate the issue, it appears that the symptoms are correct but the number of affected clients should be very limited due to fall-back mechanisms already in place. Mostly expect applications that have not been opened for at least several days (or longer) to experience delays opening or loading a map. A refinement of affected scope: While signals indicate Android is the most affected, there is a small increase in the signals for iOS as well as Navigation SDK (iOS and Android). We will provide an update by Sunday, 2026-02-08 04:15 PST with current details. We apologize to all who are affected by the disruption. Diagnosis: Slower app startup and/or maps using a stale rendering configuration. Workaround: None at this time.

3. monitoring Feb 08, 2026, 12:17 PM UTC

   Summary: Potential issue with Google Maps Platform Maps SDK on Android Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Sunday, 2026-02-08 04:45 PST. Diagnosis: Slower app startup and/or maps using a stale rendering configuration. Workaround: None at this time.

4. monitoring Feb 08, 2026, 12:46 PM UTC

   Summary: Potential issue with Google Maps Platform Maps SDK on Android Description: Our engineering team has determined the attempted mitigation failed to deploy. Work continues to deploy the mitigation, at which point we will confirm if the mitigation is effective and provide an ETA until mitigation is complete. Since client-side preventive measures are effectively limiting impact, we will provide an update by Sunday, 2026-02-08 06:00 PST with current details. Diagnosis: Slower app startup and/or maps using a stale rendering configuration. Workaround: None at this time.

5. monitoring Feb 08, 2026, 02:06 PM UTC

   Summary: Potential issue with Google Maps Platform Maps SDK on Android Description: Our engineering team has continued to face difficulty deploying the mitigation and expects deployment to take significantly longer. We are working with other internal teams to find more options to accelerate deployment. We will provide an update by Sunday, 2026-02-08 09:00 PST with current details. Diagnosis: Slower app startup and/or maps using a stale rendering configuration. Workaround: None at this time.

6. monitoring Feb 08, 2026, 05:04 PM UTC

   Summary: Potential issue with Google Maps Platform Maps SDK on Android Description: We believe the issue with Maps SDK for Android, Maps SDK for iOS, Navigation SDK is fully mitigated with the deployment of an older working version. We thank you for your patience while we worked to resolve the problem. Diagnosis: Slower app startup and/or maps using a stale rendering configuration. Workaround: None at this time.

7. resolved Feb 08, 2026, 10:05 PM UTC

   We experienced an issue with Maps SDK for Android, Maps SDK for iOS, Navigation SDK beginning at Saturday, 2026-02-07 20:39 PST. The issue has been resolved for all affected users as of Sunday, 2026-02-08 08:49 PST. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Feb 05, 2026, 08:44 PM UTC· resolved Feb 06, 2026, 03:31 AM UTC

1. investigating Feb 06, 2026, 02:42 AM UTC

   Summary: Map tiles of South Korea not shown for users in some locations Description: Our engineering team continues to investigate the issue. For users in the impacted locations, so far we confirm the issue occurs on Maps JavaScript API, Maps SDK for Android, Navigation SDK for Android. The issue does not happen for Static Maps API. We will provide an update by Thursday, 2026-02-05 19:15 PST with current details. Diagnosis: Map tiles of South Korea for zoom levels 7 and higher not shown for users in some locations including South Korea Workaround: None at this time.

2. investigating Feb 06, 2026, 03:10 AM UTC

   Summary: Map tiles of South Korea not shown for users in some locations Description: We believe the issue with Google Maps Platform, Maps JavaScript API, Maps SDK for Android, Navigation SDK, Maps SDK for iOS is mitigated as of 19:05 US/Pacific. We will monitor the situation before we close this incident. We will provide an update by Thursday, 2026-02-05 20:00 PST with current details. Diagnosis: Map tiles of South Korea for zoom levels 7 and higher not shown for users in some locations including South Korea Workaround: None at this time.

3. resolved Feb 06, 2026, 03:31 AM UTC

   The issue with Google Maps Platform, Maps JavaScript API, Maps SDK for Android, Navigation SDK, Maps SDK for iOS has been resolved for all affected users as of Thursday, 2026-02-05 19:05 PST. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Dec 03, 2025, 07:47 PM UTC· resolved Dec 03, 2025, 09:34 PM UTC

1. monitoring Dec 03, 2025, 09:40 PM UTC

   Summary: We are investigating an issue with Google Maps Platform, Geocoding API Description: We are experiencing an issue with Google Maps Platform, Geocoding API, Routes API beginning at Wednesday, 2025-12-03 12:16 PST. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2025-12-03 13:45 PST with current details. We apologize to all who are affected by the disruption. Diagnosis: 5xx errors Workaround: Retry failed request

2. resolved Dec 03, 2025, 09:43 PM UTC

   The issue with Google Maps Platform, Geocoding API, Routes API has been resolved for all affected projects as of Wednesday, 2025-12-03 13:34 PST. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Nov 13, 2025, 06:27 PM UTC· resolved Nov 13, 2025, 07:57 PM UTC

1. resolved Nov 13, 2025, 09:56 PM UTC

   Requests for photos of places from the Maps JavaScript API took minutes to return, timing-out before they could be displayed. Similar symptoms occurred at a much lower rate for web service API requests made to the Places API Photo endpoints. Note: This is an after-the-fact report for an already-mitigated incident. Symptoms: Request time-outs and HTTP 500 responses.

Read the full incident report →

Started Nov 03, 2025, 02:16 AM UTC· resolved Nov 04, 2025, 02:50 AM UTC

1. investigating Nov 03, 2025, 04:29 AM UTC

   Summary: Increased 5xx error rate for Distance Matrix API Description: We are experiencing an issue with Distance Matrix API beginning at Sunday, 2025-11-02 18:16 PST. Our engineering team continues to investigate the issue. We will provide an update by Sunday, 2025-11-02 21:00 PST with current details. We apologize to all who are affected by the disruption. Diagnosis: Increased 5xx error rate for Distance Matrix API Workaround: None at this time

2. investigating Nov 03, 2025, 04:58 AM UTC

   Summary: Increased 5xx error rate for Distance Matrix API Description: We have applied a mitigation measure and confirmed it is effective. We will monitor the situation. We will provide an update by Sunday, 2025-11-02 23:00 PST with current details. Diagnosis: Increased 5xx error rate for Distance Matrix API Workaround: None at this time

3. investigating Nov 03, 2025, 07:00 AM UTC

   Summary: Increased 5xx error rate for Distance Matrix API Description: We believe the issue with Distance Matrix API is mitigated. We continue to monitor the situation and will provide an update by Monday, 2025-11-03 16:00 PST with current details. Diagnosis: Increased 5xx error rate for Distance Matrix API Workaround: None at this time

4. investigating Nov 04, 2025, 12:02 AM UTC

   Summary: Increased 5xx error rate for Distance Matrix API Description: We believe the issue with Distance Matrix API is mitigated. We continue to monitor the situation and will provide an update by Monday, 2025-11-03 19:00 PST with current details. Diagnosis: Increased 5xx error rate for Distance Matrix API Workaround: None at this time

5. resolved Nov 04, 2025, 02:50 AM UTC

   After extended monitoring, we confirmed that the mitigation measures addressed the issue. The last measure was applied on Sunday, 2025-11-02 20:33 PST. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →