Fixed
Status Update
No update yet.
Comments
en...@google.com
Summary: Server errors for Places API requests
Description: Correction: the Server Error increase happened on *Tuesday* 23 June, 2021, between 19:47 and 19:50 US/Pacific.
The errors didn't last after 19:50, and our engineers are working on understanding the root cause for the spike.
We will provide an update by Tuesday, 2021-02-23 21:55 US/Pacific with current details.
Diagnosis: Places API requests (mostly on the Places Search endpoints) saw an increase in errors with HTTP 500 (UNKNOWN_ERROR).
Workaround: No workaround available.
Description: Correction: the Server Error increase happened on *Tuesday* 23 June, 2021, between 19:47 and 19:50 US/Pacific.
The errors didn't last after 19:50, and our engineers are working on understanding the root cause for the spike.
We will provide an update by Tuesday, 2021-02-23 21:55 US/Pacific with current details.
Diagnosis: Places API requests (mostly on the Places Search endpoints) saw an increase in errors with HTTP 500 (UNKNOWN_ERROR).
Workaround: No workaround available.
en...@google.com
Correction: the Server Error increase happened on Tuesday 23 June, 2021, between 19:47 and 19:50 US/Pacific.
The errors didn't last after 19:50, and our engineers are working on understanding the root cause for the spike.
We will provide an update by Tuesday, 2021-02-23 21:55 US/Pacific with current details.
en...@google.com
Summary: Server errors for Places API requests
Google Maps Platform engineers have identified the root cause for the issue, related to high internal traffic sent to Places API endpoints. This traffic has since been throttled to normal levels.
We thank you for your patience while we worked on resolving the issue.
Google Maps Platform engineers have identified the root cause for the issue, related to high internal traffic sent to Places API endpoints. This traffic has since been throttled to normal levels.
We thank you for your patience while we worked on resolving the issue.
en...@google.com
Google Maps Platform engineers have identified the root cause for the issue, related to high internal traffic sent to Places API endpoints. This traffic has since been throttled to normal levels.
We thank you for your patience while we worked on resolving the issue.
Description
Description: The Google Maps Platform Places API experienced an increase in 500 Server Errors on Tuesday 23 February, 2021, between 19:47 and 19:50 US/Pacific.
The errors didn't last after 19:50, and our engineers are working on understanding the root cause for the spike.
We will provide an update by Tuesday, 2021-02-23 21:55 US/Pacific with current details.
Diagnosis: Places API requests (mostly on the Places Search endpoints) saw an increase in errors with HTTP 500 (UNKNOWN_ERROR).
Workaround: No workaround available.