Google Maps Platform Status Dashboard

Google Maps Platform Status Dashboard
Incidents
- administrative_area_level_1 short_name fields filled with long-name values. - Missing country field in address / POI response.

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.

Available
Service information
Service disruption
Service outage

Incident affecting Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS

- administrative_area_level_1 short_name fields filled with long-name values. - Missing country field in address / POI response.

Incident began at 2024-06-28 20:59 and ended at 2024-06-29 03:16 (all times are US/Pacific).

Date	Time	Description
29 Jun 2024	03:16 PDT	The issue with Geocoding API and Places API searches (legacy API, New API, JavaScript and Mobile endpoints) has been resolved for all affected requests as of Saturday, 2024-06-29 03:00 US/Pacific. We thank you for your patience while we worked on resolving the issue.
29 Jun 2024	01:41 PDT	Summary: administrative_area_level_1 short_name fields filled with long-name values. Description: We believe the issue with Geocoding API and Places API (all versions and SDKs) is resolved for the most part. Thanks to the data update still being deployed to some datacenters, the ratio of affected responses has dropped significantly and is still reducing. We will provide an update by Saturday, 2024-06-29 04:00 US/Pacific with current details. Diagnosis: administrative_area_level_1 short_name fields are containing full-name responses, mainly affecting US states. ZERO_RESULTS responses in reverse-geocoding queries, possibly Places API searches as well, but NOT Places Autocomplete. Workaround: Temporarily avoid using short names for states or similar administrative entities, whether in searches, filtering parameters, or response fields. Allow for responses to have missing political/admin entity fields.
29 Jun 2024	00:18 PDT	Summary: administrative_area_level_1 short_name fields filled with long-name values. Description: We are experiencing an issue with Geocoding API, Places API, and Places API (New) beginning on Friday, 2024-06-28 15:00 US/Pacific. The symptoms are: `short_name` fields filled with full-name values, in particular for US states. (for instance "California" instead of "CA") We believe this may also have increased `ZERO_RESULTS` responses in reverse-geocoding queries, and potentially in Places API (both the legacy and New versions) for some use-cases. This would NOT affect Places Autocomplete. See also https://issuetracker.google.com/issues/350113838 for a description of symptoms from other customers. Our engineering teams believe they have found the likely root-cause (being a backend data-source discrepancy), and have written a candidate fix. At this stage the fix is expected to take several hours (possibly up to a day) before being fully deployed, as it will require a data schema update and pipeline run to fill/update that data source. We recommend for affected customers to implement workaround measures in the meantime. We will provide an update by Saturday, 2024-06-29 03:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: administrative_area_level_1 short_name fields are containing full-name responses, mainly affecting US states. ZERO_RESULTS responses in reverse-geocoding queries, possibly Places API searches as well, but NOT Places Autocomplete. Workaround: Temporarily avoid using short names for states or similar administrative entities, whether in searches, filtering parameters, or response fields. Allow for responses to have missing political/admin entity fields.
28 Jun 2024	22:57 PDT	Summary: administrative_area_level_1 short_name fields filled with long-name values. Description: We are experiencing an issue with Geocoding API beginning at Friday, 2024-06-28 15:00 US/Pacific. The symptoms are short_name fields filled with long-name values, in particular for US states. See also https://issuetracker.google.com/issues/350113838 for a description of symptoms. We believe this may also have increase ZERO_RESULTS responses in reverse-geocoding queries. Our engineering teams believe they have found the likely root-cause, being a backend data-source discrepancy. At this stage the fix is expected to take several hours and possibly up to a day, as it will require a data schema update and pipeline run to fill/update that data source. We recommend for affected customers to implement workaround measures in the meantime. We will provide an update by Saturday, 2024-06-29 01:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: - administrative_area_level_1 short_name fields are containing full-name responses, mainly affecting US states. ZERO_RESULTS responses in reverse-geocoding queries Workaround: - Temporarily avoid using short names for states or similar administrative entities, whether in searches, filtering parameters, or response fields.
28 Jun 2024	22:08 PDT	Summary: administrative_area_level_1 short_name fields filled with long-name values. Description: We are experiencing an issue with Geocoding API beginning at Friday, 2024-06-28 15:00 US/Pacific. The symptoms are short_name fields filled with long-name values, in particular for US states. See also https://issuetracker.google.com/issues/350113838 for a description of symptoms. We believe this may also have increase ZERO_RESULTS responses in reverse-geocoding queries. Our engineering teams continue to investigate the issue. We will provide an update by Friday, 2024-06-28 23:59 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: - administrative_area_level_1 short_name fields are containing full-name responses, mainly affecting US states. ZERO_RESULTS responses in reverse-geocoding queries Workaround: Avoid using short names for states or similar administrative entities, whether in searches, filters, or response fields.
28 Jun 2024	21:16 PDT	Summary: administrative_area_level_1 short_name fields filled with long-name values. Description: We are experiencing an issue with Geocoding API beginning at Friday, 2024-06-28 15:00 US/Pacific. The symptoms are short_name fields filled with long-name values, in particular for US states. See also https://issuetracker.google.com/issues/350113838 for a description of symptoms. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2024-06-28 22:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: administrative_area_level_1 short_name fields are containing full-name responses Workaround: None at this time.
28 Jun 2024	21:01 PDT	Summary: administrative_area_level_1 short_name fields filled with long-name values. Description: We are experiencing an issue with Geocoding API beginning at Friday, 2024-06-28 15:00 US/Pacific. The symptoms are short_name fields filled with long-name values, in particular for US states. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2024-06-28 21:25 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: administrative_area_level_1 short_name fields are containing full-name responses Workaround: None at this time.
28 Jun 2024	20:59 PDT	Summary: administrative_area_level_1 short_name fields filled with long-name values. Description: We are experiencing an {IF INTERMITTENT, intermittent} issue with Geocoding API beginning at Friday, 2024-06-28 15:00 US/Pacific. The symptoms are short_name fields filled with long-name values, in particular for US states. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2024-06-28 21:25 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: administrative_area_level_1 short_name fields are containing full-name responses Workaround: None at this time.

All times are US/Pacific