Newsroom speed · updated hourly
How fast we are
When an AI lab, vendor, or regulator publishes something, how long until our verified story is live? This page publishes the answer every week, including the weeks we were slow.
- Median, this week
- 17 min11 stories · detected → story live
- 95th percentile, this week
- 1.8 hprior 7-week median avg: 10 min
- Stories per day
- 38.9272 in the last 7 days
- Recognized primary-source publisher
- 19%source image present: 100%
Week by week
This week against the last 7 weeks
Bars show the weekly median (half of that week’s stories were live faster than this). The line shows the 95th percentile (all but the slowest one in twenty). Both measure minutes from our first detection to publication on this website. They exclude time before discovery. The last bar is the current, still-incomplete week.
Lead-to-publish latency
| Week starting (UTC) | Stories | Median | 95th percentile |
|---|---|---|---|
| 395 | 26 min | 22.8 h | |
| 280 | 8 min | 3.7 h | |
| 332 | 8 min | 3.2 h | |
| 692 | 7 min | 4.5 h | |
| 751 | 5 min | 56 min | |
| 272 | 8 min | 58 min | |
| 298 | 10 min | 2.9 h | |
| (this week) | 11 | 17 min | 1.8 h |
The table above holds the same numbers as the chart, for screen readers and copy-paste.
Rolling window
The last 24 hours
- All leads, median
- 19 min46 stories
- All leads, p95
- 11.2 hslowest one in twenty
- First-party leads, median
- 3 min1 stories from labs, vendors, regulators
- First-party leads, p95
- 3 minthe number we hold ourselves to
“First-party” means the lead came straight from a lab, vendor, or regulator we read directly (their newsroom, blog, release notes, status page, model registry, or official X account), not from an aggregator or wire search. The same figures appear in our public automation status under latency.firstParty and latency.weekly.
Method
How it is measured, and why it matters
- The clock starts when our source poller first records a lead. Polling cadence varies by source. This measurement does not include the delay between the original announcement and our discovery, and it cannot establish whether we were first to report a story.
- Verification happens in between: the source is read in full, AI centrality is checked, and any image must come from the source page.
- The clock stops when the story is live on this site: the moment a new article is published, or the moment a canonical update is committed for a development we had already covered. Distribution to X, LinkedIn, newsletters, or search engines is not included; those are separate, slower channels.
01Percentiles, not averages
The median (p50) says what a typical story experienced. The 95th percentile (p95) exposes the slow tail: an editor queue backed up, a source blocking our fetch, or an image that took time to verify. Averages hide that tail; we publish it.
02Provenance & images
Recognized primary-source publisher is the share of stories whose recorded source host matches our first-party source registry. Known reporting outlets and unclassified hosts are excluded. This classifies provenance; it does not independently verify every claim. Source image present is the share carrying a source-provided image. It measures media presence, not independent image accuracy. We do not generate news thumbnails.
03Why it matters
Most people first hear about an AI development from a summary of a summary. Every hour between an announcement and a verified, plainly written explanation is an hour in which speculation fills the gap. Publishing our own latency, including bad weeks, is how we keep ourselves honest about the trade-off between speed and verification, and it lets anyone check whether “fast” came at the cost of “verified”.
Limits. Weeks with few stories produce noisy percentiles; the current week is incomplete until Sunday 23:59 UTC. Stories originating from social posts are attributed to the linked first-party page, not the post. Numbers are recomputed at most hourly from the live archive; the JSON above is the exact data behind this page. Report a discrepancy.