Provider churn, the moment it spikes

A provider suddenly gaining or losing far more domains than its own recent norm is an early warning: a bulk migration, an acquisition, an outage, a takedown. We z-score every provider against its own 28-day baseline and flag the outliers as they happen.

Showing the last measurement, from 7 hours ago. Not a live read: the signed data door is at its daily read budget, which resets at midnight UTC. Every number below is real and signed - it is just as of , not now.
Provable Every number here rolls up observations we continuously scan and Ed25519-sign, then anchor on Base - a signature proves attribution and integrity, added trust, not a claim that a number is beyond question. Open a domain's signed record, take a receipt id from it, then paste that id into the verifier: it checks the Ed25519 signature and resolves that window's root from Base. Both checks run in your own browser, against published keys.
dingodns.com4.66σ
75 domains churned in or out (net +2 gained), against a norm near 4/day.
dns  2026-09-02
kirklanddc.com-3.28σ
78 domains churned in or out (net -1 lost), against a norm near 82/day.
dns  2026-09-13 · day still filling
wombatdns.com3.07σ
8 domains churned in or out (net +2 gained), against a norm near 0/day.
dns  2026-09-03

Flagged means the day's churn sits at least 3σ above the provider's own 28-day norm on at least 5 domains. The largest 3 of the last 14 days are shown; the full flagged history and per-provider filtering are on the signed API.

CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 3,587 material changesacross 2,149+ domains · 24h to ~7h ago · a floor, last measured 7h agoROTATION56 domains moved DNS from kirklanddc.com to koaladns.com, 53 moved backa rotation loop, not a migration · 24hEMAIL DRIFT2 domains switched email provider24hNOW638 curated domains not reachablelast probe, steadySITE ERRORS17,718 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 79,409 sites429 rate-limit / 403 bot-block, a posture signal