Why a zone can pause itself automatically, that it resumes on its own and is not a penalty, and how to read your zone's change history.
Every zone is watched for sudden, unusual spikes in impression volume — the kind of pattern that comes from a bot flood or a misbehaving traffic source, not from real people. If a zone's rate spikes far past what its normal traffic looks like, serving on that zone pauses automatically for a short cooldown while the surge passes.
This is a safety mechanism, not a penalty and not a strike against your account. It protects you as much as the advertiser: it stops a flood from piling up impressions that would later be disputed and clawed back. You don't need to do anything — the pause resumes on its own when the cooldown ends.
You'll see it in your zone's change history as:
Serving paused automatically — an unusual traffic pattern on this zone. Nothing to do; it resumes on its own.
and, a short while later:
Serving resumed — the automatic pause has ended.
Impressions that would have served during the pause don't earn — the same as any other filtered traffic (they show up under the Rate protection category on your reporting). Nothing that served before the pause is affected, and your earnings on normal traffic continue unchanged once serving resumes.
If a zone pauses often, it's worth looking at where its traffic comes from — a repeated pause usually points at a source that's sending automated or duplicated requests. If it looks wrong, contact us with the zone and the date and we'll walk through it.
Each zone has a change history — a plain, dated log of things that happened to the zone itself:
It deliberately does not show impressions, clicks, or revenue — those live in your reporting. As the page itself notes: this log records changes to the zone itself and automatic serving pauses — not earnings. See your reporting for impressions and revenue.
The history is the record you'd reach for to answer "what happened to this zone, and when?" — for example, to confirm that a dip lined up with an automatic pause rather than a change you made.
From a zone's history page you can download the log as a CSV for your own records. The export covers a date window — by default the last 7 days, and you can request up to 31 days at a time. It includes the full log for that window, not just the page you're looking at.
For how billing, counting, and filtering fit together end to end, see How we count & filter traffic and Filtered traffic on your zones.