Google Maps Platform Console

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 Navigation SDK

Errors starting guidance on the Navigation SDK

Incident began at 2025-06-08 02:57 and ended at 2025-06-08 05:54 (all times are US/Pacific).

Date Time Description
8 Jun 2025 05:54 PDT

The issue with Navigation SDK has been resolved for all affected users as of Sunday, 2025-06-08 05:42 PDT.

We thank you for your patience while we worked on resolving the issue.
8 Jun 2025 04:59 PDT

Summary: Errors starting guidance on the Navigation SDK

Description: Mitigation work is still underway by our engineering team.

Current data indicates that at peak 4% of requests are intermittently affected by this issue globally.

We will provide more information by Sunday, 2025-06-08 05:55 PDT.

Diagnosis: Errors starting the guidance on the Navigation SDK

Workaround: None at this time. Users should retry when it fails.
8 Jun 2025 04:28 PDT

Summary: Errors starting guidance on the Navigation SDK

Description: We are experiencing an issue with Navigation SDK beginning at Sunday, 2025-06-08 02:57 PDT. This issue would cause errors starting the guidance (up to 4% of failures globally).

Our engineering team is mitigating the issue, and the error rate is back to normal levels since 03:37:00 PDT.

We will provide an update by Sunday, 2025-06-08 04:55 PDT with current details.

We apologize to all who are affected by the disruption.

Diagnosis: Errors starting the guidance on the Navigation SDK

Workaround: None at this time. Users should retry when it fails.