The Seismograph
A seismograph does not predict earthquakes. It writes the background so that when something shakes, there is a record of what moved. This page does the same for AI answers: the DABYTE panel (16 frozen questions, 3 engines, 3 runs per question) is measured continuously, and around engine or model updates we take an extra wave before and one after. The diff between the two is published here — who moved, by how much, and on which engines.
No event waves published yet. The first release is planned for September 15, 2026, when Cloudflare's new AI-crawling defaults take effect. Two separate changes land that day. On new domains onboarding to Cloudflare, Training and Agent bots are blocked by default on pages that display ads, while Search stays allowed. And multi-purpose crawlers are judged by all of their roles at once under the most restrictive rule, so Googlebot, Applebot and BingBot get blocked for anyone who blocks Training — including through the legacy "Block AI bots" toggle, which Cloudflare's docs mark as deprecating the same day. Owners can opt out in Security settings up to September 15. (Cloudflare, 1 July 2026.) The expected iOS 27 release falls in the same window. The weekly background series is already running; the baseline waves land September 5‑7.
Rules the numbers obey
- Every figure is a share of runs in which an engine named the brand, 3 runs per question. Measured, not vendor-verified.
- A move counts only past the noise bar: at least 5 points of delta AND at least two engines agreeing on the direction. Smaller moves are shown collapsed, never hidden.
- Deltas are never computed across two panel versions. A version boundary is a break in the line, not a movement.
- Nobody can pay to enter, move inside, or leave any published table.
Machine access
Event index: /api/seismo/events.json · one file per event:
/api/seismo/<event>.json · full history with per-point panel version:
/api/history.json (series_full). Free, no key, CC BY 4.0.