[{"id":"A5nfwjNzwZbDazvxqgqC","number":"13145249071841957351","begin":"2026-10-25T12:00:00+00:00","created":"2026-10-26T10:01:14+00:00","end":"2026-11-02T17:54:59+00:00","modified":"2026-11-02T17:55:02+00:00","external_desc":"Incomplete and/or incorrectly localized addresses for some street results","updates":[{"created":"2026-11-02T17:54:59+00:00","modified":"2026-11-02T17:55:03+00:00","when":"2026-11-02T17:54:59+00:00","text":"The issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS has been resolved for all affected users as of Friday, 2026-10-30 15:45 PDT.\nWe will publish an analysis of this incident once we have completed our internal investigation.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},{"created":"2026-10-30T23:21:56+00:00","modified":"2026-11-02T17:55:02+00:00","when":"2026-10-30T23:21:56+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is resolved. Our engineering team is completing final data restoration and verification before closing this incident.\nWe will provide an update by Monday, 2026-11-02 10:30 PDT with current details.\nDiagnosis: No ongoing symptoms detected.\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-30T21:44:57+00:00","modified":"2026-10-30T23:21:56+00:00","when":"2026-10-30T21:44:57+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is resolved. Our engineering team is completing final data restoration and verification before closing this incident.\nWe will provide an update by Friday, 2026-10-30 16:30 PDT with current details.\nDiagnosis: No ongoing symptoms detected.\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-30T03:40:09+00:00","modified":"2026-10-30T21:44:57+00:00","when":"2026-10-30T03:40:09+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is resolved. Our engineering team is completing final data restoration and verification before closing this incident.\nWe will provide an update by Friday, 2026-10-30 15:00 PDT with current details.\nDiagnosis: No ongoing symptoms detected.\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-29T19:27:51+00:00","modified":"2026-10-30T03:40:09+00:00","when":"2026-10-29T19:27:51+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is partially resolved. While we believe user impact has been resolved, internal processes and procedures remain paused while Google applies the fixes that will allow their resumption.\nWe do not have an ETA for full resolution at this point.\nWe will provide an update by Thursday, 2026-10-29 19:00 PDT with current details.\nDiagnosis: Customers using Directions API, Routes API, Distance Matrix API, and Navigation SDK may have experienced degraded route quality, suboptimal detours, or missing road segments in multiple regions, including Taiwan, Brazil, Vietnam, Colombia, and Singapore.\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-28T21:10:48+00:00","modified":"2026-10-29T19:27:51+00:00","when":"2026-10-28T21:10:48+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: Our engineering team has completed the rollback of the remaining affected road features, and updated map data has propagated across our production serving systems. We are performing final verification of our automated data pipelines before resolving this incident.\nWe will provide an update by Thursday, 2026-10-29 12:00 PDT.\nDiagnosis: Customers using Directions API, Routes API, Distance Matrix API, and Navigation SDK may have experienced degraded route quality, suboptimal detours, or missing road segments in multiple regions, including Taiwan, Brazil, Vietnam, Colombia, and Singapore.\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-27T19:07:23+00:00","modified":"2026-10-28T21:10:48+00:00","when":"2026-10-27T19:07:23+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is resolved for the vast majority of traffic.\nRecovery has completed across previously affected regions, including Taiwan, Brazil, Vietnam, Colombia, and Singapore. Our engineering team is completing final data restoration and verification for a small remaining subset of road features before closing this incident.\nWe do not have an ETA for full resolution at this point.\nWe will provide an update by Tuesday, 2026-10-27 14:00 PDT with current details.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-27T16:58:47+00:00","modified":"2026-10-27T19:07:23+00:00","when":"2026-10-27T16:58:47+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is resolved.\nRecovery has completed across previously affected regions, including Taiwan, Brazil, Vietnam, Colombia, and Singapore. Our engineering team is verifying data restoration for a small remaining subset of road features before closing this incident.\nWe do not have an ETA for full resolution at this point.\nWe will provide an update by Tuesday, 2026-10-27 11:00 PDT with current details.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-27T14:27:39+00:00","modified":"2026-10-27T16:58:47+00:00","when":"2026-10-27T14:27:39+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is mostly resolved globally. However, we still observe a small number of impacted features, primarily in the geographical regions of Taiwan, Brazil, Vietnam, Colombia and Singapore.\nWe do not have an ETA for full resolution at this point.\nWe will provide an update by Tuesday, 2026-10-27 10:00 PDT with current details.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-27T04:53:00+00:00","modified":"2026-10-27T14:27:39+00:00","when":"2026-10-27T04:53:00+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is now mostly resolved. Our engineering team continues to closely monitor the services to address any remaining edge cases.\nWe do not have an ETA for full resolution at this point.\nWe will provide an update by Tuesday, 2026-10-27 11:00 PDT with current details.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-27T01:51:31+00:00","modified":"2026-10-27T04:53:00+00:00","when":"2026-10-27T01:51:31+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: We believe the issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS is partially resolved.\nWe do not have an ETA for full resolution at this point.\nWe will provide an update by Monday, 2026-10-26 23:00 PDT with current details.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-27T00:13:30+00:00","modified":"2026-10-27T01:51:31+00:00","when":"2026-10-27T00:13:30+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: The resolution of the issue is still underway. We're seeing rate of degraded results such as missing address components and wrong localization return to pre-outage levels for Geocoding and Places API.\nWe are continuing to track the progress of the data propagation across services and will provide an update by Monday, 2026-10-26 19:00:00 PDT.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-26T21:56:40+00:00","modified":"2026-10-27T00:13:30+00:00","when":"2026-10-26T21:56:40+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: The mitigation work to roll back to the corrected dataset in our data respositories was completed. Those changes will take additional time now to be picked up by our indexing and serving systems. While we are already seeing a drop in degraded results where response has missing address components, the fix will take additional time to fully propagate to all services.\nWe will provide more information by Monday, 2026-10-26 16:45 PDT.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-26T20:09:37+00:00","modified":"2026-10-26T21:56:40+00:00","when":"2026-10-26T20:09:37+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: Mitigation work is currently underway by our engineering team.\nWe do not have an ETA for mitigation at this point.\nWe will provide more information by Monday, 2026-10-26 14:40 PDT.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-26T18:07:31+00:00","modified":"2026-10-26T20:09:37+00:00","when":"2026-10-26T18:07:31+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: Our Engineering Team has identified the root cause of the corrupted data issue and mitigation work to roll back the change and regenerate corrected datasets is in progress. The data restoration requires multi-stage processing and verification across our serving systems. The mitigation is expected to take several hours to fully complete.\nWe will provide more information by Monday, 2026-10-26 13:30 PDT.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-26T16:34:14+00:00","modified":"2026-10-26T18:07:31+00:00","when":"2026-10-26T16:34:14+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: Our Engineering Team has identified the root cause of the issue and mitigation work is underway. The issue was triggered by a recent map data update that omitted certain regional and administrative relationships for street addresses.\nEngineering has stopped further updates from this pipeline and is rolling back the change while regenerating corrected datasets in parallel. Because the data restoration requires multi-stage processing and verification across our serving systems, the mitigation is expected to take several hours to fully complete.\nWe will provide more information by Monday, 2026-10-26 11:00 PDT.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-26T14:57:11+00:00","modified":"2026-10-26T16:34:14+00:00","when":"2026-10-26T14:57:11+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: Our Engineering Team has identified the root cause of the issue and mitigation work is underway. The issue was triggered by a recent map data update that omitted certain regional and administrative relationships for street addresses.\nEngineering has stopped further updates from this pipeline and is rolling back the change while regenerating corrected datasets in parallel. Because the data restoration requires multi-stage processing and verification across our serving systems, the mitigation is expected to take several hours to fully complete.\nWe will provide more information by Monday, 2026-10-26 10:00 PDT.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-26T11:53:00+00:00","modified":"2026-10-26T14:57:11+00:00","when":"2026-10-26T11:53:00+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: Mitigation work is currently underway by our engineering team.\nWe will provide more information by Monday, 2026-10-26 08:00 PDT.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-26T10:58:29+00:00","modified":"2026-10-26T11:53:00+00:00","when":"2026-10-26T10:58:29+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: We are experiencing an issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS beginning at Sunday, 2026-10-25 05:00 PDT.\nOur engineering team continues to investigate the issue.\nWe will provide an update by Monday, 2026-10-26 05:00 PDT with current details.\nWe apologize to all who are affected by the disruption.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-10-26T10:01:14+00:00","modified":"2026-10-26T10:58:29+00:00","when":"2026-10-26T10:01:14+00:00","text":"Summary: Incomplete and/or incorrectly localized addresses for some street results\nDescription: Starting October 25, 2026 at around 05:00 PT, some requests to the Geocoding API (all platforms), Places API Legacy \u0026 New (all platforms) and Address Validation API may return incomplete or incorrectly formatted address information for street-level results.\nAffected responses may be missing address components such as city, region, postal code or country. They may also return street names in an unexpected language or with incorrect address formatting, and may be flagged as partial matches. Results may vary between requests. Unexpectedly empty responses may be returned for street searches and queries.\nOur engineering team has identified the root-cause and is working on a mitigation.\nDiagnosis: Missing address components, missing or wrong localization, incorrect formatting, missing results\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"}],"most_recent_update":{"created":"2026-11-02T17:54:59+00:00","modified":"2026-11-02T17:55:03+00:00","when":"2026-11-02T17:54:59+00:00","text":"The issue with Address Validation API, Geocoding API, Places API, Places API (New), Places Library, Maps JavaScript API, Places SDK for Android, Places SDK for iOS has been resolved for all affected users as of Friday, 2026-10-30 15:45 PDT.\nWe will publish an analysis of this incident once we have completed our internal investigation.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},"status_impact":"SERVICE_INFORMATION","severity":"low","service_key":"zall","service_name":"Multiple Products","affected_products":[{"title":"Address Validation API","id":"XELnvMgmjXmZsXhBLSpL"},{"title":"Geocoding API","id":"Md1Gfbo1WAea6wKUCQru"},{"title":"Places API","id":"i3CZYPyLB1zevsm2AV6M"},{"title":"Places API (New)","id":"W2kkyoCUEUmRNER3R894"},{"title":"Places Library, Maps JavaScript API","id":"tqznBiyNULdKR3imczoa"},{"title":"Places SDK for Android","id":"5GgCkqeeTj7d2VoJA87A"},{"title":"Places SDK for iOS","id":"6NNdYVtHfTocyEZG3G5p"}],"uri":"incidents/A5nfwjNzwZbDazvxqgqC"},{"id":"t54vwBLDEYUKMXfK3Gk8","number":"8379444698480460046","begin":"2026-10-23T02:40:00+00:00","created":"2026-10-25T14:39:38+00:00","end":"2026-10-23T04:42:00+00:00","modified":"2026-11-02T20:04:19+00:00","external_desc":"Between 2026-10-22 19:40 and 21:42 US/Pacific, reverse-geocoding requests sent to the Geocoding API resolved to an address in Vietnam, for input coordinates far away from that location.","updates":[{"created":"2026-11-02T20:04:19+00:00","modified":"2026-11-02T20:04:19+00:00","when":"2026-11-02T20:04:19+00:00","text":"An Incident Report for the service degradation affecting the Geocoding API on October 22, 2026 is now available.\nFor a detailed analysis of the event, including the root cause and our prevention measures, please view the published Incident Report on the Public Issue Tracker here: https://issuetracker.google.com/issues/576897533","status":"AVAILABLE"},{"created":"2026-10-25T14:39:38+00:00","modified":"2026-11-02T20:04:19+00:00","when":"2026-10-25T14:39:38+00:00","text":"Google Engineering mitigated this issue with a rollback in the reverse geocoding serving stack.","status":"SERVICE_OUTAGE"}],"most_recent_update":{"created":"2026-11-02T20:04:19+00:00","modified":"2026-11-02T20:04:19+00:00","when":"2026-11-02T20:04:19+00:00","text":"An Incident Report for the service degradation affecting the Geocoding API on October 22, 2026 is now available.\nFor a detailed analysis of the event, including the root cause and our prevention measures, please view the published Incident Report on the Public Issue Tracker here: https://issuetracker.google.com/issues/576897533","status":"AVAILABLE"},"status_impact":"SERVICE_OUTAGE","severity":"high","service_key":"Md1Gfbo1WAea6wKUCQru","service_name":"Geocoding API","affected_products":[{"title":"Geocoding API","id":"Md1Gfbo1WAea6wKUCQru"}],"uri":"incidents/t54vwBLDEYUKMXfK3Gk8"},{"id":"C2RYudPs9FjEckoYsGko","number":"8662474962869341974","begin":"2026-10-19T18:56:00+00:00","created":"2026-10-20T04:40:53+00:00","end":"2026-10-19T20:40:00+00:00","modified":"2026-10-20T04:41:14+00:00","external_desc":"Elevated error rates and latency for Directions, Distance Matrix and Routes APIs","updates":[{"created":"2026-10-20T04:40:53+00:00","modified":"2026-10-20T04:41:14+00:00","when":"2026-10-20T04:40:53+00:00","text":"Elevated error rates and latency for Directions, Distance Matrix and Routes APIs. The issue has been resolved for all affected projects as of Monday, 2026-10-19 13:40 PDT.","status":"AVAILABLE"}],"most_recent_update":{"created":"2026-10-20T04:40:53+00:00","modified":"2026-10-20T04:41:14+00:00","when":"2026-10-20T04:40:53+00:00","text":"Elevated error rates and latency for Directions, Distance Matrix and Routes APIs. The issue has been resolved for all affected projects as of Monday, 2026-10-19 13:40 PDT.","status":"AVAILABLE"},"status_impact":"SERVICE_DISRUPTION","severity":"medium","service_key":"zall","service_name":"Multiple Products","affected_products":[{"title":"Directions API","id":"V7GFGzcHYt4r9szd5peD"},{"title":"Distance Matrix API","id":"GAgAA4csVGvQwM8pUMjZ"},{"title":"Routes API","id":"XGF8wXLekbikJa5jn3zP"}],"uri":"incidents/C2RYudPs9FjEckoYsGko"},{"id":"gWH42rsb2Df516Fmoyad","number":"11556382132098618179","begin":"2026-09-28T16:52:46+00:00","created":"2026-09-28T18:56:48+00:00","end":"2026-09-29T15:23:57+00:00","modified":"2026-09-29T15:23:59+00:00","external_desc":"[Maps SDK] Fatal Exception: m140.fqd: GL context is unusable again / glLinkProgram failed \"GVI \u0026\u0026 cannot compute gv size for oob\" on Qualcomm Adreno GPUs (maps_core_dynamite v263020506)","updates":[{"created":"2026-09-29T15:23:57+00:00","modified":"2026-09-29T15:24:00+00:00","when":"2026-09-29T15:23:57+00:00","text":"The issue with Maps SDK for Android, Navigation SDK has been resolved for all affected users as of Tuesday, 2026-09-29 00:00 PDT.\nHowever due to caching of feature flags we expect to continue to see sparse crash reports for a few days.\nWe will publish an analysis of this incident once we have completed our internal investigation.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},{"created":"2026-09-29T11:42:48+00:00","modified":"2026-09-29T15:23:59+00:00","when":"2026-09-29T11:42:48+00:00","text":"Summary: [Maps SDK] Fatal Exception: m140.fqd: GL context is unusable again / glLinkProgram failed \"GVI \u0026\u0026 cannot compute gv size for oob\" on Qualcomm Adreno GPUs (maps_core_dynamite v263020506)\nDescription: The server-side rollback of the Android WebView configuration has reached 100% global deployment.\nWe are currently monitoring telemetry to verify the impact as affected devices begin to sync the safe configuration over the network. Because Android WebView fetches these updates in the background, client recovery is expected to occur gradually over the coming hours and days.\nWe will keep this incident open and provide another update once we can confirm a reduction in crash volumes across the ecosystem.\nDiagnosis: A shader linking error crashes the host app as soon as a Google Map is loaded.\nWorkaround: For end users who are currently experiencing persistent crashes and require immediate relief, clearing the host app's storage will force a fresh fetch of the safe configuration and break the crash loop. Please note that clearing the app cache alone is ineffective; it requires clearing the app storage (which will reset local app data).","status":"SERVICE_INFORMATION"},{"created":"2026-09-29T08:21:30+00:00","modified":"2026-09-29T11:42:50+00:00","when":"2026-09-29T08:21:30+00:00","text":"Summary: [Maps SDK] Fatal Exception: m140.fqd: GL context is unusable again / glLinkProgram failed \"GVI \u0026\u0026 cannot compute gv size for oob\" on Qualcomm Adreno GPUs (maps_core_dynamite v263020506)\nDescription: Our engineering team has identified the root cause of the crash spike. It was triggered by an unexpected interaction between a recent Android WebView configuration update and the Maps SDK on devices with Qualcomm Adreno 6xx/7xx GPUs.\nWe have successfully initiated a server-side rollback of this WebView configuration. The safe configuration is currently deploying globally.\nBecause Android WebView fetches configuration updates in the background, affected devices will recover automatically as they sync the updated configuration over the network. We are actively monitoring the rollout of this mitigation and will provide another update once it has further progressed.\nDiagnosis: A shader linking error crashes the host app as soon as a Google Map is loaded.\nWorkaround: For end users who are currently experiencing persistent crashes and require immediate relief, clearing the host app's storage will force a fresh fetch of the safe configuration and break the crash loop. Please note that clearing the app cache alone is ineffective; it requires clearing the app storage (which will reset local app data).","status":"SERVICE_INFORMATION"},{"created":"2026-09-28T18:56:47+00:00","modified":"2026-09-29T08:21:30+00:00","when":"2026-09-28T18:56:47+00:00","text":"Summary: [Maps SDK] Fatal Exception: m140.fqd: GL context is unusable again / glLinkProgram failed \"GVI \u0026\u0026 cannot compute gv size for oob\" on Qualcomm Adreno GPUs (maps_core_dynamite v263020506)\nDescription: We are also posting this incident to the Google Maps Platform Status Dashboard (https://status.cloud.google.com/maps-platform/\n) while the fix rolls out.\nBased on our telemetry, this issue affects up to 0.15% of Maps SDK map loads in impacted apps, though the rate varies significantly depending on each app's device GPU distribution (Qualcomm Adreno 6xx/7xx).\nDiagnosis: A shader linking error crashes the host app as soon as a Google Map is loaded.\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"}],"most_recent_update":{"created":"2026-09-29T15:23:57+00:00","modified":"2026-09-29T15:24:00+00:00","when":"2026-09-29T15:23:57+00:00","text":"The issue with Maps SDK for Android, Navigation SDK has been resolved for all affected users as of Tuesday, 2026-09-29 00:00 PDT.\nHowever due to caching of feature flags we expect to continue to see sparse crash reports for a few days.\nWe will publish an analysis of this incident once we have completed our internal investigation.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},"status_impact":"SERVICE_INFORMATION","severity":"low","service_key":"zall","service_name":"Multiple Products","affected_products":[{"title":"Maps SDK for Android","id":"4p9T1FeeVrfzqkUnqP8t"},{"title":"Navigation SDK","id":"Z3uUQHbkWBZ1UZtKppME"}],"uri":"incidents/gWH42rsb2Df516Fmoyad"},{"id":"ujeMmtLLyYxik9k4zQcG","number":"12179562365708147273","begin":"2026-07-27T05:38:00+00:00","created":"2026-07-27T09:36:17+00:00","end":"2026-07-27T15:01:00+00:00","modified":"2026-07-27T17:28:35+00:00","external_desc":"We've received a report of an issue with Google Maps Platform - Traffic Layer and Live traffic data.","updates":[{"created":"2026-07-27T17:28:35+00:00","modified":"2026-07-27T17:28:35+00:00","when":"2026-07-27T17:28:35+00:00","text":"Issue is fully mitigated as of 2026-07-27 08:01 PDT","status":"AVAILABLE"},{"created":"2026-07-27T10:55:12+00:00","modified":"2026-07-27T17:28:35+00:00","when":"2026-07-27T10:55:12+00:00","text":"The mitigation is underway. We have no ETA to communicate at this stage and will provide a status update as soon as possible.","status":"SERVICE_DISRUPTION"},{"created":"2026-07-27T09:36:17+00:00","modified":"2026-07-27T12:30:49+00:00","when":"2026-07-27T09:36:17+00:00","text":"We are experiencing an issue with APIs that can display live traffic data (Traffic Layer) or use live traffic data (such as Directions, Distance Matrix, Routes, Routes Preferred, Roads Management Insights) beginning at Sunday, 2026-07-26 22:38 PDT.\nPlease follow updates from https://issuetracker.google.com/issues/539397397.\nSymptoms: Traffic Layer unavailable or largely degraded, live traffic information unavailable for direction calculations. No error rate increase or latency increase.\nOur engineering team continues to investigate the issue and has a mitigation underway.\nWe apologize to all who are affected by the disruption.","status":"SERVICE_DISRUPTION"}],"most_recent_update":{"created":"2026-07-27T17:28:35+00:00","modified":"2026-07-27T17:28:35+00:00","when":"2026-07-27T17:28:35+00:00","text":"Issue is fully mitigated as of 2026-07-27 08:01 PDT","status":"AVAILABLE"},"status_impact":"SERVICE_DISRUPTION","severity":"medium","service_key":"zall","service_name":"Multiple Products","affected_products":[{"title":"Directions API","id":"V7GFGzcHYt4r9szd5peD"},{"title":"Maps Embed API","id":"3cRuNnCdBP8ofMM4Ho8r"},{"title":"Maps JavaScript API","id":"PnvdvT8GxTTHKMDKG7kq"},{"title":"Maps SDK for Android","id":"4p9T1FeeVrfzqkUnqP8t"},{"title":"Maps SDK for iOS","id":"TCuQ3Mg685pUdMATFvm3"},{"title":"Maps Static API","id":"ysbfEWqtisjwS2zF5Rm3"},{"title":"Navigation SDK","id":"Z3uUQHbkWBZ1UZtKppME"},{"title":"Roads Management Insights","id":"zx6McnMLuKZagwtTPS5n"},{"title":"Route Optimization API","id":"m5eTnijaHgFg5wrdat2Y"},{"title":"Routes API","id":"XGF8wXLekbikJa5jn3zP"}],"uri":"incidents/ujeMmtLLyYxik9k4zQcG"},{"id":"B8hcGas8CqpGk3MjGuwR","number":"2132492369132241977","begin":"2026-04-07T19:04:00+00:00","created":"2026-04-07T22:58:56+00:00","end":"2026-04-07T20:37:00+00:00","modified":"2026-04-07T23:01:05+00:00","external_desc":"Address Validation API rejecting some requests with 403","updates":[{"created":"2026-04-07T22:58:56+00:00","modified":"2026-04-07T23:01:05+00:00","when":"2026-04-07T22:58:56+00:00","text":"Address Validation API rejecting some requests with 403.","status":"AVAILABLE"}],"most_recent_update":{"created":"2026-04-07T22:58:56+00:00","modified":"2026-04-07T23:01:05+00:00","when":"2026-04-07T22:58:56+00:00","text":"Address Validation API rejecting some requests with 403.","status":"AVAILABLE"},"status_impact":"SERVICE_DISRUPTION","severity":"medium","service_key":"XELnvMgmjXmZsXhBLSpL","service_name":"Address Validation API","affected_products":[{"title":"Address Validation API","id":"XELnvMgmjXmZsXhBLSpL"}],"uri":"incidents/B8hcGas8CqpGk3MjGuwR"},{"id":"4XuSFJLUTgJuU5WL4wLe","number":"1394546894396155045","begin":"2026-03-18T15:13:00+00:00","created":"2026-03-18T18:49:52+00:00","end":"2026-03-18T21:13:00+00:00","modified":"2026-03-18T21:28:55+00:00","external_desc":"Current Production Issue - Google Maps Platform","updates":[{"created":"2026-03-18T18:49:52+00:00","modified":"2026-03-18T21:28:55+00:00","when":"2026-03-18T18:49:52+00:00","text":"We are experiencing an elevated level of 5xx errors and elevated latency for Google Maps Platform, Geocoding API (Reverse Geocoding), Places/Places(New) NearbySearch beginning at Wednesday, 2026-03-18 08:13 PDT.","status":"AVAILABLE"}],"most_recent_update":{"created":"2026-03-18T18:49:52+00:00","modified":"2026-03-18T21:28:55+00:00","when":"2026-03-18T18:49:52+00:00","text":"We are experiencing an elevated level of 5xx errors and elevated latency for Google Maps Platform, Geocoding API (Reverse Geocoding), Places/Places(New) NearbySearch beginning at Wednesday, 2026-03-18 08:13 PDT.","status":"AVAILABLE"},"status_impact":"SERVICE_DISRUPTION","severity":"medium","service_key":"zall","service_name":"Multiple Products","affected_products":[{"title":"Directions API","id":"V7GFGzcHYt4r9szd5peD"},{"title":"Distance Matrix API","id":"GAgAA4csVGvQwM8pUMjZ"},{"title":"Geocoding API","id":"Md1Gfbo1WAea6wKUCQru"},{"title":"Places API","id":"i3CZYPyLB1zevsm2AV6M"},{"title":"Places API (New)","id":"W2kkyoCUEUmRNER3R894"}],"uri":"incidents/4XuSFJLUTgJuU5WL4wLe"},{"id":"8KmM6cYopmd6ByrxfRBR","number":"490810494172755270","begin":"2026-03-11T11:51:08+00:00","created":"2026-03-11T13:04:58+00:00","end":"2026-03-11T16:11:45+00:00","modified":"2026-03-11T16:11:49+00:00","external_desc":"We are investigating a potential issue with Google Maps Platform routing/directions APIs","updates":[{"created":"2026-03-11T16:11:45+00:00","modified":"2026-03-11T16:11:50+00:00","when":"2026-03-11T16:11:45+00:00","text":"The issue with Google Maps Platform, Distance Matrix API, Routes API, Directions API has been resolved for all affected projects.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},{"created":"2026-03-11T14:58:15+00:00","modified":"2026-03-11T16:11:49+00:00","when":"2026-03-11T14:58:15+00:00","text":"Summary: We are investigating a potential issue with Google Maps Platform routing/directions APIs\nDescription: We believe the issue with Google Maps Platform, Distance Matrix API, Routes API, Directions API is almost entirely resolved since 07:15 PT.\nWe do not have an ETA for full resolution at this point.\nWe will provide an update by Wednesday, 2026-03-11 10:00 PDT with current details.\nDiagnosis: Elevated latency and error rates\nWorkaround: Retry failing requests; emit requests away from sources in the JAPAC region","status":"SERVICE_INFORMATION"},{"created":"2026-03-11T13:24:30+00:00","modified":"2026-03-11T14:58:15+00:00","when":"2026-03-11T13:24:30+00:00","text":"Summary: We are investigating a potential issue with Google Maps Platform routing/directions APIs\nDescription: Mitigation work is still underway by our engineering team.\nCurrent data indicates that up to 2% of requests in JAPAC are affected by this issue.\nThe mitigation started at 2026-03-11 06:15:00 PDT.\nWe will provide more information by Wednesday, 2026-03-11 08:00 PDT.\nDiagnosis: Elevated latency and error rates\nWorkaround: Retry failing requests; emit requests away from sources in the JAPAC region","status":"SERVICE_INFORMATION"},{"created":"2026-03-11T13:04:55+00:00","modified":"2026-03-11T13:24:34+00:00","when":"2026-03-11T13:04:55+00:00","text":"Summary: We are investigating a potential issue with Google Maps Platform Routes API\nDescription: We are experiencing an issue with Google Maps Platform, Routes API beginning at Wednesday, 2026-03-11 04:51 PDT.\nOur engineering team continues to investigate the issue.\nWe will provide an update by Wednesday, 2026-03-11 06:35 PDT with current details.\nWe apologize to all who are affected by the disruption.\nDiagnosis: Elevated latency and error rates\nWorkaround: Retry failing requests; emit requests away from sources in the JAPAC region; use other routing API","status":"SERVICE_INFORMATION"}],"most_recent_update":{"created":"2026-03-11T16:11:45+00:00","modified":"2026-03-11T16:11:50+00:00","when":"2026-03-11T16:11:45+00:00","text":"The issue with Google Maps Platform, Distance Matrix API, Routes API, Directions API has been resolved for all affected projects.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},"status_impact":"SERVICE_INFORMATION","severity":"low","service_key":"zall","service_name":"Multiple Products","affected_products":[{"title":"Directions API","id":"V7GFGzcHYt4r9szd5peD"},{"title":"Distance Matrix API","id":"GAgAA4csVGvQwM8pUMjZ"},{"title":"Routes API","id":"XGF8wXLekbikJa5jn3zP"}],"uri":"incidents/8KmM6cYopmd6ByrxfRBR"},{"id":"163VbP2njo8deNYScb4v","number":"15467164364025958114","begin":"2026-02-25T10:00:00+00:00","created":"2026-02-25T23:51:44+00:00","end":"2026-02-26T22:07:09+00:00","modified":"2026-02-26T22:07:13+00:00","external_desc":"Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API","updates":[{"created":"2026-02-26T22:07:09+00:00","modified":"2026-02-26T22:07:14+00:00","when":"2026-02-26T22:07:09+00:00","text":"The issue with Google Maps Platform, Geocoding API, Places API, Places API (New), Roads API has been resolved for all affected projects as of Thursday, 2026-02-26 13:26 PST.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},{"created":"2026-02-26T18:46:14+00:00","modified":"2026-02-26T22:07:13+00:00","when":"2026-02-26T18:46:14+00:00","text":"Summary: Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API\nDescription: We are observing another spike of 5xx errors started at 2026-02-26 ~08:00 PST. The investigation into the most recent occurrence is ongoing, and Google Engineers have initiated the process of undraining the affected data centers.\nWe do not have an ETA for full resolution at this point.\nWe will provide an update by Thursday, 2026-02-26 14:00 PST with current details.\nDiagnosis: 5xx errors and elevated p90, p99 latency\nWorkaround: Retry a failed request","status":"SERVICE_INFORMATION"},{"created":"2026-02-26T11:16:10+00:00","modified":"2026-02-26T18:46:14+00:00","when":"2026-02-26T11:16:10+00:00","text":"Summary: Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API\nDescription: We believe the issue with Google Maps Platform, Geocoding API, Places API, Places API (New), Roads API is resolved for the most part.\nWe will provide a final update by Thursday, 2026-02-26 10:00 PST.\nDiagnosis: 5xx errors and elevated p90, p99 latency\nWorkaround: Retry a failed request","status":"SERVICE_INFORMATION"},{"created":"2026-02-26T06:01:03+00:00","modified":"2026-02-26T11:16:10+00:00","when":"2026-02-26T06:01:03+00:00","text":"Summary: Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API\nDescription: Mitigation work is still underway by our engineering team. The affected datacenters are still drained, and error rates are stabilized across services.\nThe mitigation is expected to complete by Thursday, 2026-02-26 09:00 PST.\nWe will provide more information by Thursday, 2026-02-26 05:00 PST.\nDiagnosis: 5xx errors and elevated p90, p99 latency\nWorkaround: Retry a failed request","status":"SERVICE_INFORMATION"},{"created":"2026-02-26T04:00:26+00:00","modified":"2026-02-26T06:01:03+00:00","when":"2026-02-26T04:00:26+00:00","text":"Summary: Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API\nDescription: The affected datacenters are still drained, and error rates are stabilized across services.\nGoogle Engineers are investigating the root cause for this incident.\nWill will provide an update by Wednesday, 2026-02-25 22:00 PST with current details.\nDiagnosis: 5xx errors and elevated p90, p99 latency\nWorkaround: Retry a failed request","status":"SERVICE_INFORMATION"},{"created":"2026-02-26T01:16:15+00:00","modified":"2026-02-26T04:00:26+00:00","when":"2026-02-26T01:16:15+00:00","text":"Summary: Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API\nDescription: We believe the issue with Google Maps Platform, Geocoding API, Places API, Places API (New), Roads API is partially resolved.\nFull resolution is expected to complete by Thursday, 2026-02-26 09:00 PST.\nGoogle Engineers have drained some affected datacenters, but there is another which is still in the process of being mitigated. The level of 5xx errors is reduced, but some customers may still experience elevated latency due to non-optimal routing.\nImpacted region: North America.\nWe will provide an update by Wednesday, 2026-02-25 20:00 PST with current details.\nDiagnosis: 5xx errors and elevated p90, p99 latency\nWorkaround: Retry a failed request","status":"SERVICE_INFORMATION"},{"created":"2026-02-25T23:51:44+00:00","modified":"2026-02-26T01:16:15+00:00","when":"2026-02-25T23:51:44+00:00","text":"Summary: Elevated latency and 5xx error rate for Google Maps Platform, Geocoding API, Places API. Roads API\nDescription: We believe the issue with Google Maps Platform, Geocoding API, Places API, Places API (New), Roads API is partially resolved.\nWe do not have an ETA for full resolution at this point.\nWe will provide an update by Wednesday, 2026-02-25 16:50 PST with current details.\nDiagnosis: 5xx errors and elevated p90, p99 latency\nWorkaround: Retry a failed request","status":"SERVICE_INFORMATION"}],"most_recent_update":{"created":"2026-02-26T22:07:09+00:00","modified":"2026-02-26T22:07:14+00:00","when":"2026-02-26T22:07:09+00:00","text":"The issue with Google Maps Platform, Geocoding API, Places API, Places API (New), Roads API has been resolved for all affected projects as of Thursday, 2026-02-26 13:26 PST.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},"status_impact":"SERVICE_INFORMATION","severity":"low","service_key":"zall","service_name":"Multiple Products","affected_products":[{"title":"Geocoding API","id":"Md1Gfbo1WAea6wKUCQru"},{"title":"Places API","id":"i3CZYPyLB1zevsm2AV6M"},{"title":"Places API (New)","id":"W2kkyoCUEUmRNER3R894"},{"title":"Roads API","id":"UJEsvSMiBDvuxqMxK2Dg"}],"uri":"incidents/163VbP2njo8deNYScb4v"},{"id":"FcNKg8cR28xzpDNe1cGM","number":"820013836199620047","begin":"2026-02-22T08:53:56+00:00","created":"2026-02-22T11:45:30+00:00","end":"2026-02-22T19:00:33+00:00","modified":"2026-02-22T19:00:36+00:00","external_desc":"Elevated error rate on Places API","updates":[{"created":"2026-02-22T19:00:33+00:00","modified":"2026-02-22T19:00:37+00:00","when":"2026-02-22T19:00:33+00:00","text":"The issue with Google Maps Places API has been resolved for all affected users as of Sunday, 2026-02-22 10:40 PST.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},{"created":"2026-02-22T13:00:28+00:00","modified":"2026-02-22T19:00:36+00:00","when":"2026-02-22T13:00:28+00:00","text":"Summary: Elevated error rate on Places API\nDescription: Error rates have subsided, as mitigation work is still underway by our engineering team.\nWe will provide more information by Sunday, 2026-02-22 09:00 PST.\nDiagnosis: Increase in 500 errors\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-02-22T11:45:26+00:00","modified":"2026-02-22T13:00:31+00:00","when":"2026-02-22T11:45:26+00:00","text":"Summary: Elevated error rate on Places API\nDescription: We are experiencing an issue with Google Maps Platform, Places API beginning at Sunday, 2026-02-22 00:53 PST.\nOur engineering team continues to investigate the issue.\nWe will provide an update by Sunday, 2026-02-22 04:15 PST with current details.\nWe apologize to all who are affected by the disruption.\nDiagnosis: Increase in 500 errors\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"}],"most_recent_update":{"created":"2026-02-22T19:00:33+00:00","modified":"2026-02-22T19:00:37+00:00","when":"2026-02-22T19:00:33+00:00","text":"The issue with Google Maps Places API has been resolved for all affected users as of Sunday, 2026-02-22 10:40 PST.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},"status_impact":"SERVICE_INFORMATION","severity":"low","service_key":"i3CZYPyLB1zevsm2AV6M","service_name":"Places API","affected_products":[{"title":"Places API","id":"i3CZYPyLB1zevsm2AV6M"}],"uri":"incidents/FcNKg8cR28xzpDNe1cGM"},{"id":"oMp6wfmScbB8pvKC7Wgj","number":"11547522823909174730","begin":"2026-02-08T04:39:59+00:00","created":"2026-02-08T11:46:45+00:00","end":"2026-02-08T22:05:12+00:00","modified":"2026-02-08T22:05:15+00:00","external_desc":"Potential issue with Google Maps Platform Maps SDK on Android","updates":[{"created":"2026-02-08T22:05:12+00:00","modified":"2026-02-08T22:05:17+00:00","when":"2026-02-08T22:05:12+00:00","text":"We experienced an issue with Maps SDK for Android, Maps SDK for iOS, Navigation SDK beginning at Saturday, 2026-02-07 20:39 PST.\nThe issue has been resolved for all affected users as of Sunday, 2026-02-08 08:49 PST.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},{"created":"2026-02-08T17:04:56+00:00","modified":"2026-02-08T22:05:15+00:00","when":"2026-02-08T17:04:56+00:00","text":"Summary: Potential issue with Google Maps Platform Maps SDK on Android\nDescription: We believe the issue with Maps SDK for Android, Maps SDK for iOS, Navigation SDK is fully mitigated with the deployment of an older working version.\nWe thank you for your patience while we worked to resolve the problem.\nDiagnosis: Slower app startup and/or maps using a stale rendering configuration.\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-02-08T14:06:07+00:00","modified":"2026-02-08T17:04:56+00:00","when":"2026-02-08T14:06:07+00:00","text":"Summary: Potential issue with Google Maps Platform Maps SDK on Android\nDescription: Our engineering team has continued to face difficulty deploying the mitigation and expects deployment to take significantly longer. We are working with other internal teams to find more options to accelerate deployment.\nWe will provide an update by Sunday, 2026-02-08 09:00 PST with current details.\nDiagnosis: Slower app startup and/or maps using a stale rendering configuration.\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-02-08T12:46:14+00:00","modified":"2026-02-08T14:06:07+00:00","when":"2026-02-08T12:46:14+00:00","text":"Summary: Potential issue with Google Maps Platform Maps SDK on Android\nDescription: Our engineering team has determined the attempted mitigation failed to deploy. Work continues to deploy the mitigation, at which point we will confirm if the mitigation is effective and provide an ETA until mitigation is complete.\nSince client-side preventive measures are effectively limiting impact, we will provide an update by Sunday, 2026-02-08 06:00 PST with current details.\nDiagnosis: Slower app startup and/or maps using a stale rendering configuration.\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-02-08T12:17:56+00:00","modified":"2026-02-08T12:46:14+00:00","when":"2026-02-08T12:17:56+00:00","text":"Summary: Potential issue with Google Maps Platform Maps SDK on Android\nDescription: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point.\nWe will provide more information by Sunday, 2026-02-08 04:45 PST.\nDiagnosis: Slower app startup and/or maps using a stale rendering configuration.\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-02-08T12:08:07+00:00","modified":"2026-02-08T12:17:56+00:00","when":"2026-02-08T12:08:07+00:00","text":"Summary: Potential issue with Google Maps Platform Maps SDK on Android\nDescription: While our engineering team continues to investigate the issue, it appears that the symptoms are correct but the number of affected clients should be very limited due to fall-back mechanisms already in place. Mostly expect applications that have not been opened for at least several days (or longer) to experience delays opening or loading a map.\nA refinement of affected scope: While signals indicate Android is the most affected, there is a small increase in the signals for iOS as well as Navigation SDK (iOS and Android).\nWe will provide an update by Sunday, 2026-02-08 04:15 PST with current details.\nWe apologize to all who are affected by the disruption.\nDiagnosis: Slower app startup and/or maps using a stale rendering configuration.\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"},{"created":"2026-02-08T11:46:39+00:00","modified":"2026-02-08T12:08:07+00:00","when":"2026-02-08T11:46:39+00:00","text":"Summary: Potential issue with Google Maps Platform Maps SDK on Android\nDescription: We are investigating a potential issue with Maps SDK for Android, Maps SDK for iOS, Navigation SDK.\nWe will provide more information by Sunday, 2026-02-08 04:15 PST.\nDiagnosis: Slower app startup and/or maps using a stale rendering configuration.\nWorkaround: None at this time.","status":"SERVICE_INFORMATION"}],"most_recent_update":{"created":"2026-02-08T22:05:12+00:00","modified":"2026-02-08T22:05:17+00:00","when":"2026-02-08T22:05:12+00:00","text":"We experienced an issue with Maps SDK for Android, Maps SDK for iOS, Navigation SDK beginning at Saturday, 2026-02-07 20:39 PST.\nThe issue has been resolved for all affected users as of Sunday, 2026-02-08 08:49 PST.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},"status_impact":"SERVICE_INFORMATION","severity":"low","service_key":"zall","service_name":"Multiple Products","affected_products":[{"title":"Maps SDK for Android","id":"4p9T1FeeVrfzqkUnqP8t"},{"title":"Maps SDK for iOS","id":"TCuQ3Mg685pUdMATFvm3"},{"title":"Navigation SDK","id":"Z3uUQHbkWBZ1UZtKppME"}],"uri":"incidents/oMp6wfmScbB8pvKC7Wgj"},{"id":"nEFBVwmCVuViEfgMC2JB","number":"6318808939705622996","begin":"2026-02-05T20:44:25+00:00","created":"2026-02-06T02:42:44+00:00","end":"2026-02-06T03:31:59+00:00","modified":"2026-02-06T03:32:01+00:00","external_desc":"Map tiles of South Korea not shown for users in some locations","updates":[{"created":"2026-02-06T03:31:59+00:00","modified":"2026-02-06T03:32:02+00:00","when":"2026-02-06T03:31:59+00:00","text":"The issue with Google Maps Platform, Maps JavaScript API, Maps SDK for Android, Navigation SDK, Maps SDK for iOS has been resolved for all affected users as of Thursday, 2026-02-05 19:05 PST.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},{"created":"2026-02-06T03:10:13+00:00","modified":"2026-02-06T03:32:01+00:00","when":"2026-02-06T03:10:13+00:00","text":"Summary: Map tiles of South Korea not shown for users in some locations\nDescription: We believe the issue with Google Maps Platform, Maps JavaScript API, Maps SDK for Android, Navigation SDK, Maps SDK for iOS is mitigated as of 19:05 US/Pacific.\nWe will monitor the situation before we close this incident.\nWe will provide an update by Thursday, 2026-02-05 20:00 PST with current details.\nDiagnosis: Map tiles of South Korea for zoom levels 7 and higher not shown for users in some locations including South Korea\nWorkaround: None at this time.","status":"SERVICE_DISRUPTION"},{"created":"2026-02-06T02:42:42+00:00","modified":"2026-02-06T03:10:16+00:00","when":"2026-02-06T02:42:42+00:00","text":"Summary: Map tiles of South Korea not shown for users in some locations\nDescription: Our engineering team continues to investigate the issue.\nFor users in the impacted locations, so far we confirm the issue occurs on Maps JavaScript API, Maps SDK for Android, Navigation SDK for Android.\nThe issue does not happen for Static Maps API.\nWe will provide an update by Thursday, 2026-02-05 19:15 PST with current details.\nDiagnosis: Map tiles of South Korea for zoom levels 7 and higher not shown for users in some locations including South Korea\nWorkaround: None at this time.","status":"SERVICE_DISRUPTION"}],"most_recent_update":{"created":"2026-02-06T03:31:59+00:00","modified":"2026-02-06T03:32:02+00:00","when":"2026-02-06T03:31:59+00:00","text":"The issue with Google Maps Platform, Maps JavaScript API, Maps SDK for Android, Navigation SDK, Maps SDK for iOS has been resolved for all affected users as of Thursday, 2026-02-05 19:05 PST.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},"status_impact":"SERVICE_DISRUPTION","severity":"medium","service_key":"zall","service_name":"Multiple Products","affected_products":[{"title":"Maps JavaScript API","id":"PnvdvT8GxTTHKMDKG7kq"},{"title":"Maps SDK for Android","id":"4p9T1FeeVrfzqkUnqP8t"},{"title":"Maps SDK for iOS","id":"TCuQ3Mg685pUdMATFvm3"},{"title":"Navigation SDK","id":"Z3uUQHbkWBZ1UZtKppME"}],"uri":"incidents/nEFBVwmCVuViEfgMC2JB"},{"id":"bG1nVat961psqzVe7tB9","number":"17226869972734311091","begin":"2025-12-03T19:47:00+00:00","created":"2025-12-03T21:40:04+00:00","end":"2025-12-03T21:34:00+00:00","modified":"2025-12-03T22:13:15+00:00","external_desc":"We are investigating an issue with Google Maps Platform, Geocoding API","updates":[{"created":"2025-12-03T21:43:13+00:00","modified":"2025-12-03T22:13:15+00:00","when":"2025-12-03T21:43:13+00:00","text":"The issue with Google Maps Platform, Geocoding API, Routes API has been resolved for all affected projects as of Wednesday, 2025-12-03 13:34 PST.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},{"created":"2025-12-03T21:40:03+00:00","modified":"2025-12-03T21:43:15+00:00","when":"2025-12-03T21:40:03+00:00","text":"Summary: We are investigating an issue with Google Maps Platform, Geocoding API\nDescription: We are experiencing an issue with Google Maps Platform, Geocoding API, Routes API beginning at Wednesday, 2025-12-03 12:16 PST.\nOur engineering team continues to investigate the issue.\nWe will provide an update by Wednesday, 2025-12-03 13:45 PST with current details.\nWe apologize to all who are affected by the disruption.\nDiagnosis: 5xx errors\nWorkaround: Retry failed request","status":"SERVICE_INFORMATION"}],"most_recent_update":{"created":"2025-12-03T21:43:13+00:00","modified":"2025-12-03T22:13:15+00:00","when":"2025-12-03T21:43:13+00:00","text":"The issue with Google Maps Platform, Geocoding API, Routes API has been resolved for all affected projects as of Wednesday, 2025-12-03 13:34 PST.\nWe thank you for your patience while we worked on resolving the issue.","status":"AVAILABLE"},"status_impact":"SERVICE_DISRUPTION","severity":"medium","service_key":"zall","service_name":"Multiple Products","affected_products":[{"title":"Address Validation API","id":"XELnvMgmjXmZsXhBLSpL"},{"title":"Directions API","id":"V7GFGzcHYt4r9szd5peD"},{"title":"Distance Matrix API","id":"GAgAA4csVGvQwM8pUMjZ"},{"title":"Geocoding API","id":"Md1Gfbo1WAea6wKUCQru"},{"title":"Maps Static API","id":"ysbfEWqtisjwS2zF5Rm3"},{"title":"Routes API","id":"XGF8wXLekbikJa5jn3zP"},{"title":"Street View Static API","id":"E2TgzLfvdQfjwf5ouMvv"}],"uri":"incidents/bG1nVat961psqzVe7tB9"}]