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

Incident affecting AdSense

Incident began at 2019-05-02 19:00 and ended at 2019-05-29 20:33 (times are in Coordinated Universal Time (UTC)).

Date Time Description
May 29, 2019 8:33 PM UTC The problem with AdSense should be resolved for the vast majority of affected users. We will continue to work towards restoring service for the remaining affected users, but no further updates will be added to this dashboard.

The issue from May 1, 2019, the recording of duplicate events such as clicks, conversions, queries, has been resolved. All reports for April 30 and May 1 have been corrected. Due to an internal migration, corrected AdSense data will be available in reports by the end of Q2.

May 6, 2019 7:32 PM UTC AdSense 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 underlying issue has been fully resolved and data for all report types is now available to all users. Reports for April 30th and May 1st might include duplicate entries due to the outage. Duplicate entries are currently being removed and the cleaned up data will be made available as soon as possible.

May 2, 2019 7:00 PM UTC We're investigating reports of an issue with AdSense. We will provide more information shortly. The affected users are able to access AdSense, but may not have access to the most recent data.

A number of duplicate events were recorded across the whole AdSense platform. Engineering is aware of the issue and is working on fixing the issue and removing the duplicate data. Duplicate data is currently not being recorded but reports will likely have incorrect data for April 30th and May 1st until the duplicate entries will be removed. Additionally, Reporting data for May 1st and 2nd may be inaccurate or unavailable while we resolve this issue.