The AdMob status incidents on Google’s Ads Status Dashboard number two, not one, and a third ad-serving incident sits open alongside them at Google Ad Manager. All three are logged as starting on August 20, 2026, and all three remain Active as of the dashboard’s August 29 refresh at 12:35 UTC, with no end timestamp on any of them. The one publishers read about, a rewarded-video failure on AdMob, is not even the oldest of the three.
Three Incidents Opened on the Same Day, Not One
PPC Land put the elapsed time on the covered incident at roughly 188 hours, measured from its August 20, 21:19 UTC start to its last update on August 28 at 17:16 UTC. Measured instead against the dashboard’s own August 29 refresh, the same incident has been open 207 hours 16 minutes; the two figures measure to different clocks, not different incidents.
That incident, rewarded video failing to play on Android, is not alone. A second AdMob incident, which PPC Land’s report does not cover, started 3 hours 53 minutes earlier, at 17:26 UTC. It hits interstitial and rewarded formats, not rewarded alone, on Android and iOS, not Android alone, and it has gone roughly 63 hours since its last update against 19 hours 18 minutes for the incident that made the news. A third, worded almost identically, sits open on Google Ad Manager, a separate product, with a logged start of August 20 at 05:34 UTC and no public update in the record earlier than August 27 at 08:35 UTC.
Three incidents, one start date, one symptom family: close buttons and reward playback both breaking in the same window. Google has not linked the three in its status text, and the record shows no common cause, only the shared start date, symptom family and severity label.
| Measure | Value |
|---|---|
| Incident 1 (rewarded video) open since start | 207 hours 16 minutes (8 days 15h 16m) |
| Incident 2 (close buttons, AdMob) open since start | 211 hours 9 minutes (8 days 19h 9m) |
| Incident 3 (close buttons, Ad Manager) open since logged start | 223 hours 1 minute (9 days 7h 1m) |
| Incident 1: gap between update 2 and update 3 | 160 hours 6 minutes (Aug 22 01:10 → Aug 28 17:16) |
| Incident 1: time since its last update | 19 hours 18 minutes |
| Incident 2: time since its last update | 63 hours 1 minute |
| Incident 3: time since its last update | 51 hours 58 minutes |
What Severity Level Is Google’s AdMob Rewarded-Video Incident?
Google’s Ads Status Dashboard lists the AdMob rewarded-video incident, plus two further incidents opened the same day, under severity low, service information, the mildest incident state the dashboard defines; the fourth state in its legend, Available, means no incident at all. That tier sits below service disruption and service outage, and none of the three carries an end timestamp as of the August 29 dashboard check.
A Severity Label Below the Radar
The dashboard’s legend runs four states in order: Available, Service information, Service disruption, Service outage. All three incidents sit in the second tier from the bottom. Each incident’s most recent update describes affected users as still able to access the product while “seeing error messages, high latency, and/or other unexpected behavior.” PPC Land makes a related point about the covered incident: the service-information marker “sits below service disruption in Google’s own taxonomy,” so a failure of a paying ad format was never escalated past the mildest category the dashboard offers.
That label is not a description of severity as a publisher would feel it; it is the tier least likely to trip a status-page monitor built to watch for red. A team polling for a disruption or outage banner, the two states above this one, would have seen nothing to alert on across all three incidents for more than a week. The label held through the most recent public update on the covered incident, on August 28:
“AdMob rewarded ads fail to play video and instead show a large play icon on Android apps. Engineering has identified the root cause and deployed a mitigation covering most users, while work continues to address the remaining impact. There is currently no workaround.”
— Google Ads Status Dashboard, August 28
A mitigation covering most users is not a resolution; the same update says only that Google expects a resolution for all users in the near future.
Why Neither Symptom Shows Up in Ad Reporting
A rewarded video that never plays does not produce a failed impression. The request goes out, the static play icon Google describes appears instead, and the reward is simply never granted, so the loss has no row of its own in ad reporting. A close button that never renders behaves the same way: no ad error, only a user stuck on an interstitial, an outcome that lands in session length, not ad-serving logs.
Both gaps sit outside ad reporting, and the status page that would have named the cause carried all three incidents at its mildest incident tier. What is left is a client-side check: a custom event fired when the reward is actually granted, compared against the event fired when the rewarded ad was requested or shown. The GA4 event name generator and validator covers the naming half of that problem: it generates and validates the GA4 event names for a reward-granted event and a reward-requested event.
That comparison is a ratio the publisher already owns, not a figure Google publishes, and across August 20 through 29 it is the only local evidence of how big the gap is. A metric that is recorded and a metric that pays out are not always the same number, either: YouTube runs a similar split between the view count a media kit displays and the narrower count its Partner Program pays on.
Source: Google Ads Status Dashboard; PPC Land, “Google AdMob bug halts rewarded video on Android apps for eight days”