Status
Status
Our public latency commitment: how long PubTrust takes to reach a verdict, measured across the whole network and published with the sample counts behind it — and whether our event pipeline is keeping up.
Is ingest keeping up?
Event ingest
DelayedNewest minute rollup: 2026-09-15 13:13 UTC, 2 h 34 min old.
How fast is a decision?
| Window | Samples | p50 | p95 | p99 |
|---|---|---|---|---|
| Last 24 hours | 82 | 33.8 ms | Not enough data yet (82 of 100) | Not enough data yet (82 of 1,000) |
| Last 7 days | 583 | 28.8 ms | 193 ms | Not enough data yet (583 of 1,000) |
Latency computed 2026-09-15 13:13:33 UTC (recomputed hourly). Page generated 2026-09-15 15:47:53 UTC; regenerated at most once a minute.
How are these figures produced?
- Source. Decision time is measured in the tag, per decision: from the moment a detection layer first observes an ad — a bid arriving, a creative appearing in a slot, a patched browser API being called — to the moment it reaches a verdict, including the tag’s own parsing and debounce. It travels on the violation beacon and is stored as
decisionMs; values that are negative or longer than ten minutes are discarded at ingest. - Scope. Network-wide: every Site of every organisation together. No per-customer figure is published, and nothing on this page identifies a customer, a Site or an advertiser.
- Windows. Rolling 24 hours and 7 days. Figures are precomputed hourly; if the hourly computation is more than 3 hours old or unavailable, they are computed directly from raw events when the page is generated.
- Percentiles. Continuous percentiles over every qualifying event in the window. A percentile is shown only when the window holds at least 20 samples for p50, 100 for p95 and 1,000 for p99; below that it reads “not enough data yet” rather than showing a number we could not defend.
- What is included. Decision time is carried on violation beacons, so these figures describe decisions that matched a policy — in Monitor as well as Block, across all detection layers. Clean decisions do not currently report a decision time and are not included.
- Ingest freshness. The age of the most recent one-minute traffic rollup. Operational means it is at most 10 minutes old; otherwise the page shows Delayed with the actual age. Rollups are only written when traffic arrives, so a quiet network also reads as delayed.