Google Maps Platform Status Dashboard

This page provides status information on the services that are part of Google Maps Platform. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit https://cloud.google.com/maps-platform/.

For incidents related to Google Cloud Platform and Google Cloud Console, please visit the Cloud Status Dashboard.

Incident affecting Geocoding API, Places API

Elevated level of 5xx error for Geocoding (Reverse Geocoding) and Places API

Incident began at 2025-03-19 09:26 and ended at 2025-03-19 12:56 (all times are US/Pacific).

Date Time Description
19 Mar 2025 12:56 PDT

The issue with Geocoding API, Places API has been resolved for all affected projects as of Wednesday, 2025-03-19 11:44 US/Pacific.

We thank you for your patience while we worked on resolving the issue.

19 Mar 2025 11:47 PDT

Summary: Elevated level of 5xx error for Geocoding (Reverse Geocoding) and Places API

Description: We have experienced an intermittent issue with Geocoding API (Reverse Geocoding) and Places API (legacy) (all methods) at Wednesday, 2025-03-19 during the periods 09:26 - 09:40 and 10:06 -10: 18 US/Pacific.

After further investigation we think that the root cause is networking infrastructure issue. The issue for Google Maps Platform APIs was mitigated by draining the affected cell.

Impacted region: West Europe.

We will continue monitoring and provide an update by Wednesday, 2025-03-19 12:40 US/Pacific with current details.

Diagnosis: 5xx errors

Workaround: Retry

19 Mar 2025 11:11 PDT

Summary: Elevated level of 5xx error for Geocoding (Reverse Geocoding) and Places API

Description: We have experienced an intermittent issue with Geocoding API (Reverse Geocoding) and Places API (legacy) (all methods) at Wednesday, 2025-03-19 during the periods 09:26 - 09:40 and 10:06 -10: 18 US/Pacific.

The root cause was a bad job. Our engineering team mitigated the issue by draining the cell.

We will continue monitoring and provide an update by Wednesday, 2025-03-19 11:40 US/Pacific with current details.

We apologize to all who are affected by the disruption.

Diagnosis: 5xx errors

Workaround: Retry