How long can an Ad Manager reporting delay last?

Google's status dashboard shows it varies. A February 2026 incident began at 22:23 UTC on 23 February and ended at 02:10 UTC on 24 February, with the delay first stated as over 7 hours and later revised to about 4.5 hours. Google does not publish one standard figure that we could find.

Should I re-run an Ad Manager report after a delay?

Yes, if you were affected. For a March 2022 incident Google said you could re-run Historical reports to see the proper values, and that recent Ad Exchange data could be missing or show negative values in the meantime. Re-run the report before you act on the numbers.

How do I check whether a gap is a reporting delay or a real drop?

Look at the Google Ads Status Dashboard for open Ad Manager incidents, then check a source that does not depend on the report. If the earlier hours are normal and only the newest hours are short, a delay is likely, but check the status page and re-run the report later to be sure. Working ad tags rule out one cause only.

Is your Ad Manager report late, or did revenue drop?

If the newest hours in your Ad Manager report look thin while the earlier hours look normal, check for a reporting delay before you call it a revenue drop. Open Google's status dashboard for an open Ad Manager incident, then check the page's ad tags. Neither check proves revenue is fine, so set a time to look again.

A late report and a real drop can look the same in the numbers. They need different responses, so decide how long you will wait before anyone is paged.

What a reporting delay looks like

The data arrives late, so the newest part of the chart is short. Google does not describe what that looks like metric by metric, but the common shape is a dip at the right-hand edge that fills in once the data catches up. A delay changes the report. The site served as usual.

Google's own status dashboard has examples. An incident that began at 22:23 UTC on 23 February 2026 delayed Ad Manager reporting, and Google first described the delay as over 7 hours across all metrics. At 01:31 UTC it revised that to approximately 4.5 hours. The incident closed at 02:10 UTC on 24 February, and Google said the UI reporting data was within expected availability again. Data Transfer files were not affected.

The page does not tell you to re-run anything. A 2022 incident is more specific. Between 25 and 26 March 2022, recent Ad Exchange data in Historical reports could be missing or show negative values, and Google said affected users could re-run Historical reports to see the proper values. It also warned that the missing data could affect campaign pacing.

We could not find a published figure for how late Ad Manager reports normally run, so this post gives none. Your own history is a better guide, and the last section shows how to get it.

How to tell a delay from a drop

Run the checks in this order. Each one takes a couple of minutes.

Open the Google Ads Status Dashboard and look at Google Ad Manager. It lists Ad Manager, Ad Manager DAI and Ad Manager Data Transfer separately, shows open incidents, links to an incident history, and has an Atom feed you can subscribe to. An open Ad Manager reporting incident is the explanation until proven otherwise.
Re-run the report with Hour as a dimension. The Ad Manager API describes Hour as a breakdown by hour of the day in the network's time zone, available for the Historical report type. Google's deprecation notice says the old Reports tool is fully deactivated in Q3 2026, with Interactive reports as the replacement, so check that your report type offers Hour. If hours 0 to 14 are normal and only 15 and later are short, the gap is at the right edge, and that is where a delay shows up.
Compare the shape with the same hours on the same weekday last week. A delay puts the dip at the newest hours only, and it should fill in when you re-run the report later. A real drop starts at one specific hour and is still there on the re-run.
Look at the page. Load a page with the ad unit, add ?google_force_console=1 to the URL to open Google Publisher Console (or run googletag.openConsole() in the browser console), and confirm the slots request and render ads. If the tags fail, you have a real problem and the delay is not your explanation.

Step 4 only rules a cause out. Ads can render while revenue falls: demand can drop out, a floor can change, consent can fail, or fill can weaken. A working page tells you the tags are fine. Revenue needs its own check: the status dashboard and a re-run report.

Check the time zone before you compare hours

Hour in the Ad Manager API follows your network's time zone, while the separate DATE_PT dimension uses Pacific Time. If a script or a spreadsheet mixes the two, hours can end up offset against each other. Pick one time zone for the comparison, say which in the report name, and keep to it.

Why a delay costs more than the numbers

A late report can send people in the wrong direction for an hour. Say the last three hours show revenue far below normal. Someone rolls back a release, and then the data fills in. The rollback was for nothing, and now there is a second change in the log that will confuse the next investigation.

It also breaks anything that reads the report on a schedule. A script or an alert rule that compares "today so far" with last week treats missing hours as lost revenue. The ads were fine. The rule fired because it trusted incomplete data.

The opposite error is worse. If you decide every dip is a delay, a real drop sits there until the afternoon. Put a limit on the wait. If the status dashboard is clear, or the incident has closed and the newest hours are still short on a re-run, treat it as real.

What to do tomorrow

Bookmark the status dashboard and subscribe to its feed in the channel where your team already talks. When someone asks "is it us?", the first link should be Google's own status.
Write down, for one week, the hour at which your report is complete. Look at the day's report at the same time each morning and note how many hours are missing. That gives you your own normal, which beats a number from a blog.
Add one rule to your incident note: before a rollback, check the status page and re-run the report. It costs two minutes.
Where you can, put a delay before an alert. If a rule compares the current hour with a baseline, give the newest hours time to arrive before it fires. Which baseline the rule should use is its own question, answered in what an Ad Manager drop alert should compare against.

What to tell the team while you wait

Say what you know and what you are waiting on. A message like "Ad Manager reporting shows an open incident, the newest hours are short, the tags still load, I will re-run the report at the top of the hour and escalate if it is still short" gives the finance lead and the sales team something to act on. It also keeps them from forwarding a screenshot of a half-empty chart to a buyer.

Write the incident down even when it turns out to be nothing. A line with the start time, the status page entry and the time the data completed builds the history that tells you what a normal delay looks like on your network.

What PubPilot checks

PubPilot sends alerts on Google Ad Manager anomalies by email, Slack and in-app. Separately, it watches ad scripts on the page for missing tags, broken layouts and script failures. The script checks do not depend on the Ad Manager report, so they help rule the page in or out while the report is late.

When it is not a delay

If the status dashboard is clear, or the incident has closed and the newest hours are still short, you have a real problem, whether or not the page serves ads. Start with the checklist in why did ad revenue drop in Google Ad Manager. If one ad unit is at zero while the others serve, the six causes in zero impressions on one ad unit are the next stop.