Latency

How long it takes for something that happened to appear here, per path, measured continuously. The target is different for each path and the reason is printed beside it — a single figure across all of them was wrong, and wrong in the direction that flatters nobody: it was measured on the fastest path and then applied to the slowest, where it cannot be met by construction.

Path and why it costs what it costs	Target	Median	p90	Rows	Excluded	Verdict
Bitcoin whales A Bitcoin block is announced about a second after it is mined, and the block itself — nearly two megabytes of it — then has to be fetched and read before anyone can say what moved inside it. That fetch is inside this number and is never taken back out: timing the announcement and calling it the event would be reporting a rumour. This is how Bitcoin works rather than a fault of ours.	≤35s	31.8s	50.0s	2,000	249 / 0	within targetp90 is over it
Stories From the moment a source published to the moment the story was live here, measured against the source’s own timestamp.	≤10 min	7.6 min	18.4 min	330	253 unmeasurable 126 were published before this wire recorded source timestamps (2026-08-12); 70 arrived on a feed that stated no time; 57 carried a source clock ahead of our own publish. The exclusion is an artefact of when the field was added, not a slow path being left out — but it does mean this median describes the wire as it runs now, and we have no measurement of the days before 2026-08-12.	within target 199 of 330 inside

What “excluded” means

Two kinds of measurement are counted and then left out of the averages, and the counts are in the table above so you can see how many. Neither is a slow reading quietly dropped:

The source’s clock was ahead of ours. A Bitcoin block carries the time its miner claims, which is routinely a little ahead of real time. Counting those made this wire look like it was reporting transfers two and a half minutes before they happened, which measures two clocks rather than one wire.
The first readings after a reconnection. When we lose a connection and pick it up again we are handed what we missed, all at once. Timing those describes the interruption, not the speed of the wire — one of them once read 1,145 seconds for something that took 24.

How this is measured — the full method, including both exclusions in detail and why the verdict is taken on the median.

The verdict is on the median. Where the p90 is over the bar it says so, and that is the number worth arguing about: half of everything is faster than a median by definition, and the slow tail is what somebody actually waited for. The story row’s exclusions are posts carrying no source timestamp to measure from — on-chain stories, the Market Wrap, desk columns and anything published before the field existed — not slow ones dropped.

Daily median, last 30 days

2 of 30 days carry measurements. The live meter is a rolling window of the last 2,000 events — about two days — so the empty bars are days this record does not reach, not days nothing happened. They are drawn rather than dropped: a chart that hid them would imply a month of measurements we do not have.

When it was slower than this

2026-10-07 · The wire wrote no ledger row for 38 minutes (stage 'budget') · 38 min — the post-mortem
2026-10-06 · The wire wrote no ledger row for 47 minutes (stage 'budget') · 47 min — the post-mortem
2026-10-06 · The wire wrote no ledger row for 107 minutes (stage 'budget') · 1h 47m — the post-mortem
2026-10-06 · The wire wrote no ledger row for 44 minutes (stage 'budget') · 44 min — the post-mortem
2026-10-03 · The wire wrote no ledger row for 46 minutes (stage 'budget') · 46 min — the post-mortem
2026-10-03 · The wire wrote no ledger row for 39 minutes (stage 'budget') · 39 min — the post-mortem
2026-10-02 · The wire wrote no ledger row for 65 minutes (stage 'budget') · 65 min — the post-mortem
2026-09-29 · The wire wrote no ledger row for 57 minutes (stage 'budget') · 57 min — the post-mortem
2026-09-28 · The wire wrote no ledger row for 31 minutes (stage 'budget') · 31 min — the post-mortem
2026-09-28 · The wire wrote no ledger row for 37 minutes (stage 'budget') · 37 min — the post-mortem
2026-09-28 · The wire wrote no ledger row for 39 minutes (stage 'budget') · 39 min — the post-mortem
2026-09-28 · The wire wrote no ledger row for 44 minutes (stage 'budget') · 44 min — the post-mortem
2026-09-25 · The wire wrote no ledger row for 31 minutes (stage 'budget') · 31 min — the post-mortem
2026-09-24 · The wire wrote no ledger row for 31 minutes (stage 'budget') · 31 min — the post-mortem
2026-09-22 · The wire wrote no ledger row for 48 minutes (stage 'budget') · 48 min — the post-mortem
2026-09-21 · The wire wrote no ledger row for 37 minutes (stage 'budget') · 37 min — the post-mortem
2026-09-20 · The wire wrote no ledger row for 67 minutes (stage 'budget') · 67 min — the post-mortem
2026-09-12 · A disk cleanup deleted two folders the publisher needed, and it stopped starting · 7h 05m — the post-mortem
2026-09-08 · The wire wrote no ledger row for 402 minutes (stage 'budget') · 6h 42m — the post-mortem
2026-09-07 · The wire wrote no ledger row for 31 minutes (stage 'budget') · 31 min — the post-mortem
2026-09-04 · The wire wrote no ledger row for 43 minutes (stage 'budget') · 43 min — the post-mortem
2026-09-03 · The wire wrote no ledger row for 54 minutes (stage 'budget') · 54 min — the post-mortem
2026-09-01 · Publishing ran at half speed for 49 minutes · 49 min — the post-mortem
2026-09-01 · We published a wrong gold price for 35 minutes · 35 min — the post-mortem
2026-08-30 · Publishing ran at half speed for 33 minutes · 33 min — the post-mortem
2026-08-28 · The price record had a 46-hour hole and nothing said so · 46h 16m — the post-mortem
2026-08-28 · Publishing ran at half speed for 43 minutes · 43 min — the post-mortem
2026-08-26 · Publishing ran at half speed for 78 minutes · 78 min — the post-mortem
2026-08-19 · The wire published nothing for 21 hours · 21h 04m — the post-mortem
2026-08-17 · Large Bitcoin transfers went unreported for an hour · 63 min — the post-mortem
2026-08-17 · The wire wrote the news and published none of it · 33 min — the post-mortem
2026-08-13 · The wire stopped publishing for seven hours and nothing recovered it · 7h 16m — the post-mortem

Uptime and incidents · Accuracy · the on-chain ledger these are measured on