A defect that stops AdMob rewarded ads from playing video on Android has run for more than a week, and the mitigation Google deployed on August 28, 2026 still leaves some publishers without a working format.

Google logged an incident affecting AdMob at 21:19 UTC on Thursday, August 20, 2026, and posted the first public note five minutes later. The symptom described on the Google Ads Status Dashboard is narrow and specific: rewarded ads fail to play video on Android applications and display a large play icon in place of the creative. As of the most recent update, timestamped 17:16 UTC on Friday, August 28, 2026, the incident remains open.

That places the elapsed duration at roughly 188 hours, or seven days and twenty hours, between the recorded start of the fault and the latest engineering note. Three status entries cover that window. Each one repeats the same closing line: there is currently no workaround.

What the dashboard records

The initial entry, published at 21:24 UTC on August 20, contained no diagnosis. Google stated it was investigating reports of an issue with AdMob and would provide more information shortly. Affected users retained access to the AdMob interface itself, the notice said, but encountered error messages, high latency, and other unexpected behaviour.

A second entry followed at 01:10 UTC on Saturday, August 22, roughly twenty-eight hours later. The wording shifted slightly. Service had already been restored for some users, according to the dashboard, and a resolution for all users was expected in the near future, with the caveat that the time frame was an estimate subject to change. On the underlying defect, the update said only that engineering was continuing to work on the mitigation.

Then the log went quiet. The next entry did not arrive until 17:16 UTC on August 28, an interval of approximately 160 hours without any public revision to the incident record. That third update carried the first substantive technical claim of the sequence. According to the Google Ads Status Dashboard, "Engineering has identified the root cause and deployed a mitigation covering most users, while work continues to address the remaining impact."

The phrase "most users" is doing considerable work in that sentence. It concedes that a subset of AdMob publishers remained affected at the time of writing, without quantifying the share, naming the affected regions, identifying which app categories or SDK versions carried the fault, or offering any estimate of when the residual impact would clear.

A severity classification worth noting

Google's status dashboard uses four states: available, service information, service disruption, and service outage. All three entries in this incident carry the service information marker, the lowest of the three non-nominal tiers. The classification is not incidental. Service information sits below service disruption in Google's own taxonomy, which means an eight-day failure of a revenue-generating ad format was never escalated past the mildest category the dashboard offers.

The gap between that label and the practical consequence is where the story sits. Rewarded video is not a peripheral format. It is a transactional unit in which a user consents to watch a complete video in exchange for an in-app benefit, and the publisher is paid on completion. When the video does not play and a static play icon appears instead, the transaction does not complete. No completion means no reward delivered to the user, and, in the mechanics that govern the format, no impression monetised at the rate that made the placement worth building.

Why the format carries weight

Rewarded inventory has moved from experimental line item to core monetisation over the past two years. Singular's 2026 ROI Index described rewarded and incentive-driven environments as appearing prominently across gaming and growth leaderboards and no longer functioning as experimental budget lines, attributing the shift to stronger retention filtering, improved fraud controls, and more disciplined optimisation.

The demand side has been building around the format in parallel. Magnite secured exclusive global rights to monetise Roblox's rewarded video inventory in January 2026, covering 151 million daily active users. Kantar research commissioned by AppLovin and published in February 2026 found that 71 percent of mobile gamers who bought a product after seeing a mobile game advertisement did so on the same day. Google itself has spent the period expanding AdMob's controls over the format, introducing high-engagement settings for interstitial and rewarded units in February 2025 and adding bidding partners including InMobi, ironSource, and Unity to AdMob mediation in July 2025.

For a mobile game publisher running rewarded video as the primary revenue stream, a defect that prevents the video from rendering is not a degraded experience. It is the removal of the product.

Eight days without a workaround

The repeated declaration that no workaround exists is the operationally significant detail in the record. In most platform incidents, a workaround gives affected parties something to do: a fallback endpoint, a rollback to a prior library version, a temporary configuration change. Its absence across all three entries means publishers had no documented remediation path available to them for the full duration.

The structural reason is the SDK. In-app advertising is delivered through code compiled into the application binary, and the rendering behaviour of a rewarded unit is governed by the Google Mobile Ads SDK rather than by any setting a publisher can toggle in a web console. A publisher who identifies that rewarded video has stopped rendering cannot patch the rendering path without a new app release, and a new app release cannot fix a defect whose root cause sits inside a dependency the publisher does not control.

That dependency is currently in transition. Google designated the rewritten Google Mobile Ads Next-Gen SDK as the preferred kit for Android on July 6, 2026, formally classifying the previous SDK as legacy and starting a deprecation clock that runs to a sunset date of June 30, 2028. The Next-Gen SDK entered beta on January 22, 2026, built in Kotlin, with Google citing banner ad requests completing up to 27 percent faster and a 17 percent reduction in device footprint. Nothing in the status dashboard entries identifies which SDK generation the rewarded video defect affects, or whether both are implicated.

The revenue line behind the incident

AdMob sits inside Alphabet's Google Network segment, alongside AdSense and Google Ad Manager. That segment has been contracting. Network revenue fell 4 percent year over year to 6.97 billion dollars in the first quarter of 2026, and slipped a further 1 percent to 7.3 billion dollars in the second quarter, reported on July 22, 2026, while Search advertising rose 17 percent to 63.3 billion dollars over the same period.

The divergence gives the incident its financial context. Publishers monetising through AdMob are already operating inside the one Alphabet advertising line that is shrinking, and rewarded video is among the formats that has held up commercially while display inventory has come under pressure from reduced open-web traffic. An extended failure in that specific format lands on the segment least able to absorb it.

A pattern of infrastructure incidents

The August incident is not isolated. Google's advertising infrastructure experienced cascading failures beginning January 13, 2026, when Ad Manager and AdSense publishers reported eCPM declines ranging from 50 percent to 90 percent, driven by a systemic decline in Ad Exchange match rates that Google acknowledged at 01:44 UTC on January 15. Google Analytics 4 suffered a complete platform outage on July 17, 2025. In August 2024, a Google Ads incident that began on July 30 exposed Merchant Center product data across advertiser accounts. A data centre serving issue disrupted search results in multiple locales on October 3, 2025.

What distinguishes the AdMob case is not severity but duration and disclosure cadence. The January 2026 Ad Exchange incident produced steeper immediate revenue damage but resolved within days. This one has produced three dashboard entries in eight days, one of them separated from the previous by more than six days, on a defect that remained unresolved for a portion of the affected base at the point of the most recent note.

What is not in the record

The dashboard supplies no impression volume, no revenue impact estimate, no geographic breakdown, and no count or percentage of affected publishers. It does not state whether the defect affects mediated demand from third-party networks routed through AdMob or only Google-served rewarded creatives. It does not indicate whether iOS applications were examined and cleared, or simply not mentioned. It does not say whether affected impressions were billed.

That last omission matters for reconciliation. A rewarded unit that renders a play icon without playing video may still register as a served impression depending on where in the delivery chain the failure occurs, which would produce reporting figures that diverge from realised user completions. Nothing in the published record confirms or excludes that outcome.

Google has continued shipping publisher-facing changes to the same product family through the incident window, having consolidated its advertising developer documentation into a single hub on April 6, 2026 and cut granular Google Ads data retention to 37 months effective June 1, 2026. The AdMob incident record, by contrast, has yielded one technical sentence in eight days.

Timeline

Summary

Who: Google, operator of the AdMob mobile advertising platform, and the Android application publishers who monetise inventory through AdMob rewarded video units. Alphabet reports AdMob revenue inside the Google Network segment alongside AdSense and Google Ad Manager.

What: An incident in which AdMob rewarded ads fail to play video on Android applications, displaying a large play icon in place of the creative. Three entries on the Google Ads Status Dashboard record the fault, each stating that no workaround exists. The most recent entry says engineering identified the root cause and deployed a mitigation covering most users, with work continuing on remaining impact.

When: The incident began at 21:19 UTC on August 20, 2026. Updates followed at 21:24 UTC on August 20, 01:10 UTC on August 22, and 17:16 UTC on August 28, leaving an interval of roughly 160 hours between the second and third entries and an elapsed duration of about 188 hours to the latest note.

Where: Android applications serving AdMob rewarded video. The dashboard entries specify no geographic scope, no affected regions, and no publisher count, and make no reference to iOS.

Why: The failure occurs in a format whose value depends on video completion, since a rewarded impression only converts when a user watches the video through to the point at which the in-app benefit is granted. Because rendering behaviour is controlled by the Google Mobile Ads SDK rather than by a publisher-side setting, no console-level remediation was available, which is consistent with the repeated statement that no workaround exists.