Google Ads Status Dashboard

This page provides status information on the services that are part of Google Ads. 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://ads.google.com/.

Incident affecting Google Ad Manager

Incident began at 2026-08-04 09:26 and ended at 2026-08-04 19:00 (times are in Coordinated Universal Time (UTC)).

Date Time Description
Aug 4, 2026 7:19 PM UTC The problem with Google Ad Manager has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. The affected users are able to access Google Ad Manager, but are seeing error messages, high latency, and/or other unexpected behavior.

The engineering team has confirmed that the issue is fully resolved. System availability has returned to normal levels, and error rates have subsided.
Aug 4, 2026 5:25 PM UTC Google Ad Manager service has already been restored for some users, and we expect a resolution for all users in the near future. Please note this time frame is an estimate and may change. The affected users are able to access Google Ad Manager, but are seeing error messages, high latency, and/or other unexpected behavior.

The engineering team identified the root cause, and mitigation steps have been successfully applied to route traffic away from the affected area.

As service availability is improving, you may simply retry any previously failed operations.
Aug 4, 2026 9:32 AM UTC We're investigating reports of an issue with Google Ad Manager. We will provide more information shortly. The affected users are able to access Google Ad Manager, but are seeing error messages, high latency, and/or other unexpected behavior.

Affected users are experiencing extreme UI slowness, reporting delays, and forecasting failures within Google Ad Manager, as well as failures when querying the SOAP API.

There is no complete workaround at this time. However, reloading the page or rerunning the task may succeed on a subsequent attempt.