Google Maps Platform Status Dashboard
For incidents related to Google Cloud Platform and Google Cloud Console, please visit the Cloud Status Dashboard.
Incident affecting Places SDK for Android, Places SDK for iOS, Street View Static API, Places API, Places Library, Maps JavaScript API
Increased latency in Asia region for requests involving reverse-geocode
Incident began at 2023-04-10 19:57 and ended at 2023-04-11 00:05 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 11 Apr 2023 | 00:05 PDT | The issue with reverse geocoding has been resolved for all affected projects as of Tuesday, 2023-04-11 00:04 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 10 Apr 2023 | 23:24 PDT | Summary: Increased latency in Asia region for requests involving reverse-geocode Description: We believe the issue with reverse geocoding is partially resolved. The error ratio and latency went back to normal. Our engineer team is still working to maintain the capacity of our backend services for the root cause resolution. We do not have an ETA for full resolution at this point. We will provide an update by Tuesday, 2023-04-11 02:30 US/Pacific with current details. Diagnosis: None at this time. Workaround: None at this time. |
| 10 Apr 2023 | 22:27 PDT | Summary: Increased latency in Asia region for requests involving reverse-geocode Description: Our engineering team has identified the cause of issue, and keep working to manage the capacity to improve the latency. To clarify which requests are affected:
If you have any questions or needs which are specific to your use of the Google Maps APIs, please create a Maps APIs support case: https://console.cloud.google.com/google/maps-apis/support We will provide more information by Monday, 2023-04-10 23:30 US/Pacific. Diagnosis: None at this time. Workaround: None at this time. |
| 10 Apr 2023 | 21:33 PDT | Summary: Increased latency in Asia region for requests involving reverse-geocode Description: Our engineering team is continuing its investigations. To clarify which requests are affected:
If you have any questions or needs which are specific to your use of the Google Maps APIs, please create a Maps APIs support case: https://console.cloud.google.com/google/maps-apis/support We will provide more information by Monday, 2023-04-10 22:30 US/Pacific. Diagnosis: None at this time. Workaround: None at this time. |
| 10 Apr 2023 | 20:31 PDT | Summary: Increased latency in Asia region for requests involving reverse-geocode Description: An attempt at mitigation reduced latency but also triggered an increase in server errors between 2023-04-10 20:09 and 2023-04-10 20:19 US/Pacific. The measure has been reverted, reducing the error rate and latency back to previous level. Our engineering team is continuing its investigations. If you have any questions or needs which are specific to your use of the Google Maps APIs, please create a Maps APIs support case: https://console.cloud.google.com/google/maps-apis/support We will provide more information by Monday, 2023-04-10 21:35 US/Pacific. Diagnosis: None at this time. Workaround: None at this time. |
| 10 Apr 2023 | 20:08 PDT | Summary: Increased latency in Asia region for requests involving reverse-geocode Description: Google Maps Platform APIs are experiencing increased latency in the Asia region for requests involving reverse-geocoding. Please star the issue here to receive further updates as this is the authoritative source of information about this issue while our engineering team pursues its investigation and applies mitigation measures. If you have any questions or needs which are specific to your use of the Google Maps APIs, please create a Maps APIs support case: https://console.cloud.google.com/google/maps-apis/support We will provide more information by Monday, 2023-04-10 20:35 US/Pacific. Diagnosis: None at this time. Workaround: None at this time. |
- All times are US/Pacific