Skip to main content

folkfox

Skip to main content
Skip to content
APP MARKETING

The dashboard says twelve days. The reporting said eight

An advertising format stopped paying for the better part of a fortnight, and the only public record of how long is a page almost nobody watches.

Quick answerGoogle's status dashboard logs its August AdMob incident at twelve days, not the eight days reported. If you sell rewarded video ads, the lesson is that platform silence is a revenue risk you must instrument yourself.
SECTION 01

Rewarded video ads went dark, and the clock kept running#

288 hrs

Longest of the two AdMob incidents Google logged from 20 August 2026, on its own status dashboard

Google Ads Status Dashboard

Somewhere in the third week of August, a small hinge in the mobile advertising machine stopped turning. Players tapped to watch, expecting the extra life or the second hint, and got a large play icon that did nothing. Google's own incident page describes the symptom in flat, unbothered prose: AdMob rewarded ads fail to play video. No drama, no apology, just a fox-quiet notice on a page that most app teams have never opened.

The trade press caught it. PPC Land reported the fault on 29 August, counting eight days and noting bluntly that there is currently no workaround. That number has since been repeated everywhere. It is also, on Google's own record, wrong.

Where the eight days came from#

It matters which format broke. Rewarded video ads are not a garnish on a monetisation stack, they are frequently the load-bearing beam, and they are the one format a player actively asks for. When rewarded video ads stop serving, the studio does not lose a slice of passive inventory. It loses the transaction its whole economy is built on, and it loses it silently.

Nobody fabricated it. PPC Land published while the incident was still open, so eight days was the honest count on the morning it went to press. The trouble is that the incident did not stop when the coverage did. Google's Ads Status Dashboard summary logs two AdMob incidents beginning 20 August 2026, and records their durations as ten days and twenty-one hours, and twelve days.

That is the whole story in one line. The outage outlived its own reporting by half again, and the only place that fact lives is a dashboard with no subscribers, no digest and no obligation to tell you anything at all.

AdMob incidents by duration, as logged by Google
Aug 26 B
288 hrs (12 days)
Aug 26 A
261 hrs (10d 21h)
Jun 26
63 hrs
Apr 26
47 hrs
Mar 26
16 hrs
Dec 25
9 hrs 44 min
Jan 26
3 hrs 14 min
Nov 25
1 hr 24 min
August 2026 was not a bad week. On Google's own numbers it ran roughly four times longer than the worst AdMob incident of the preceding nine months.

Read that shape slowly. Six incidents in nine months, none longer than sixty-three hours, and then two that run for the better part of a fortnight. Whatever broke in August was a different animal from the usual overnight wobble, and the durations are Google's, not ours.

rewarded video ads that quietly stopped paying: an ink-drawn fox pressing an ear to a large silent brass bell, a paper notice face down at its feet
The bell never rang. That was the whole problem.
SECTION 02

A status label is not a service level#

Here is where the trail gets genuinely murky, and where we are going to be careful rather than clever. Reporting on this incident describes it as carrying Google's lowest severity classification. We went to check, twice, and the dashboard returned a different label on different fetches. So we are not going to tell you which tier it carried, because we do not reliably know.

What we can tell you is stranger, and more useful. Google's publisher status dashboard publishes exactly four status labels, and publishes no definition of any of them anywhere on the page. Available, service information, service disruption, service outage: four words doing an enormous amount of unexplained work.

Consider what a publisher actually needed that week. Not a root cause, not an apology: simply a sentence saying rewarded video ads are down on Android and we do not yet know for how long. That sentence existed, on a page, in public. It was just never pushed to anyone whose revenue depended on reading it.

The developer record is quieter still. The Google Mobile Ads SDK release notes for Android carry no entry addressing this fault. The most recent release at the time of writing is 25.4.0, dated 17 June 2026, and its note reads in full: Bug fixes and performance improvements. The fault was server-side, so it left no fingerprint in the documentation a developer would actually read.

Nobody else wrote it down either#

We went looking for corroboration in the places developers complain: issue trackers, forums, the usual undergrowth. We found none from the August window. Every account of this outage traces back through PPC Land to Google's dashboard. That is not a criticism of the reporting, which did its job. It is a description of how thin the public record is when a platform breaks quietly.

u/CaptainEliass
I work in fraud analysis and not app development. Cases pass through me before they get to the dispute team, and while researching more on disputes I saw the changes Google Play recently made. I was interested to see how this change affected developers, and I couldn't find these numbers anywhere so I worked them out.
r/androiddev, 4 September 2026View on Reddit

That thread is about chargeback costs rather than rewarded video, but it catches the same scent exactly. A platform economics change lands, the numbers that matter to developers are not published anywhere, and somebody outside the industry has to sit down and work them out. Substitute outage duration for dispute fees and you have August.

SECTION 03

Why rewarded ads concentrate the damage#

Not every ad format fails the same way. A banner that does not fill is a small, spread-out loss: the banner unit sits in the layout, earns nothing for a moment, and the session carries on regardless. The player never notices and never changes behaviour.

Rewarded video ads are built on the opposite bargain. The whole format, as set out in Google's Android rewarded ads documentation, exists so that a player chooses to watch in return for something inside the game. The player has already agreed to trade attention for something they want. That consent is the product.

A quiet, shared loss

Impressions thin out across the whole install base. Revenue dips, nobody rages, and the fault is invisible to the player.

A loud, concentrated one

The player has already tapped, already agreed, already expects the reward. The failure lands at the exact moment you asked for trust, and it lands on your most engaged users first.

That bargain is why rewarded video ads survived the privacy reckoning that gutted so much targeted inventory. They do not need to know who the player is. They need only the player's consent in the moment, which is why rewarded video ads kept their value through App Tracking Transparency while behavioural formats bled out.

So the damage is doubly concentrated. Your most engaged players are the ones who reach for a rewarded ad unit in the first place, and a broken one hits them precisely when they were most willing to co-operate. The revenue line is the smaller wound. The habit is the deeper one.

United States internet advertising revenue, 2021 to 2025 ($bn)
The market this outage sits inside grew 13.9 per cent in 2025 alone. A fortnight of a broken format is a rounding error to the platform and a quarter to a studio.300bn200bn100bn0bn20212022202320242025US internet ad revenue: 189.3US internet ad revenue: 209.7US internet ad revenue: 225US internet ad revenue: 258.6US internet ad revenue: 294.6
US internet ad revenue
The market this outage sits inside grew 13.9 per cent in 2025 alone. A fortnight of a broken format is a rounding error to the platform and a quarter to a studio.

Those figures come from the IAB and PwC Internet Advertising Revenue Report, which grounds them in a stated method: data reported directly to PwC by companies selling internet advertising, alongside public corporate filings. Worth noting honestly, PwC states it does not audit that information. It remains the sturdiest sizing anyone publishes.

A rewarded video example worth keeping#

Take the plainest rewarded video example there is: a puzzle game offering a hint in exchange for thirty seconds. When it works, the player gets unstuck and stays. When it shows a dead play icon instead, you have not merely lost a CPM. You have taught an engaged player that your reward loop is unreliable, at the one moment they were paying attention.

SECTION 04

Instrument the silence before it costs another fortnight#

The uncomfortable truth of this whole episode is that no platform owes you a phone call. The remedy is not to demand better weather. It is to build your own barometer, and to keep it somewhere you will actually look.

Watch fill, not just revenue

Revenue moves for a dozen reasons and lags by a day. Fill rate and impression counts per rewarded placement move within hours, and they move first.

Alert on the floor, not the trend

A gentle downward trend triggers nothing useful. A hard threshold, breached for two hours, wakes somebody up.

Separate the format

If rewarded, interstitial and banner all roll into one revenue number, a total format failure looks like a soft week.

Poll the dashboard

The status page is public and machine-readable enough to check on a schedule. It is the cheapest monitoring in this list.

Keep a second demand source

Mediation exists precisely so one network's bad fortnight is not your bad fortnight.

None of that is exotic. It is the sort of patient prowl any decent app marketing partner should already run on a client's behalf, and the reason it so often goes undone is that it produces nothing to show in a good month. It earns its keep once a year, in a fortnight exactly like this one.

What to measure on rewarded video ads specifically#

Generic ad monitoring will not catch this. A blended fill rate across every format stayed perfectly respectable through August, because banners and interstitials carried on filling exactly as usual. The collapse was confined to rewarded video ads, and only a metric scoped to rewarded video ads could have seen it on day one.

So scope the alert to the format and to the platform together. Rewarded video ads on Android is the unit of failure here, not advertising revenue in general, and a dashboard that cannot express that distinction will keep reporting a calm average over a burning room. Splitting by operating system costs an afternoon and it is the difference between noticing on Thursday and noticing a fortnight later.

SECTION 05

The dependency you did not price#

Every app that monetises with advertising carries a silent partner it never signed with. You can negotiate a publisher deal, argue a rate card and audit a mediation stack, and you still cannot make a platform tell you when its own plumbing has failed.

The outage outlived its own reporting by half again, and the only place that fact lives is a page with no subscribers.
folkfox

What changes after August is not your vendor list. It is where you put your attention. Treat the platform status page as a monitored input rather than a curiosity, keep your formats separated in reporting, and hold a second demand path in the hedgerow for the fortnight you cannot predict.

There is a commercial reading here too, and it is not gloomy. Studios that instrument rewarded video ads properly end up with something their competitors lack: a defensible account of what a platform failure cost, in money, on dates. That record is leverage in a mediation negotiation and evidence in a board meeting, and it costs a morning to start.

Then do the unglamorous thing and write the incident down. A studio that can say precisely what a twelve-day outage cost it has an argument. One that only knows August was soft has a shrug. Sharp records outfox soft memories every time, and this is the season to start keeping them.

If your app marketing and your paid media reporting still roll into a single revenue line, that is the first knot to untie. We are happy to look at it with you.

Questions

Frequently asked questions#

How long was the AdMob rewarded video outage, really?

Google's own status dashboard logs two AdMob incidents starting 20 August 2026 at ten days and twenty-one hours, and twelve days. The widely reported eight-day figure was accurate on 29 August, when the trade coverage published, but the incident was still open at that point.

What is a normal rewarded video ads cpm?

There is no trustworthy public answer. Every benchmark we could find for rewarded video ads cpm traces to a vendor blog citing another vendor blog, with no sample size, app count or date range disclosed. Treat any single published figure as marketing rather than measurement, and benchmark against your own historic fill and revenue instead.

How do you protect in app advertising revenue from a platform outage?

Monitor fill rate per format rather than total revenue, alert on a hard floor rather than a trend, and keep a second demand source live through mediation. Protecting in app advertising revenue is mostly about detection speed: the loss is rarely preventable, but a two-hour response is a very different quarter from a twelve-day one.

Does Google publish what its status labels mean?

No. The publisher status dashboard displays four labels, available, service information, service disruption and service outage, without publishing criteria for any of them. A tier therefore describes how Google is characterising an incident, not what it did to your revenue.

Should a broken ad format change how I plan releases?

It should change how you read the data around them. If a launch window overlaps a platform incident, your cohort numbers are contaminated and comparing them to a clean month will mislead you. Note the incident against the cohort so nobody draws the wrong lesson six months later.

Is rewarded video still worth building around?

Yes, on the evidence. It remains the format where the player opts in, which is why it survives privacy changes that damage targeted formats. The August incident is an argument for instrumenting it properly, not for abandoning it.

Keep reading

Read more on this topic#

Ready to see what your ad stack is actually doing?

We build the boring monitoring that turns a twelve-day surprise into a two-hour one, and we read the platform paperwork so you do not have to.