TOLL

What software pays for, recorded every six hours.

Snapshot
2026-11-01 05:59 UTC
Sweep
daily-2026-10-30 · finished 2026-10-30 13:00 UTC
Listed
28,354

Status

What the collector did and when. Every registry pull, every sweep, every restart and every alert is a row, so a gap in the record always has a stated cause.

this page, as of 2026-11-01 11:28 UTC · method · liveregenerates every five minutes
Last successful registry pull
2026-11-01 05:59 UTC
as of 2026-11-01 05:59 UTC · method · live · pulls run at 17 past every sixth hour UTC; next due 2026-11-01 06:17 UTC, which is past by more than an hour
The scheduled pull has not landed. GitHub may delay or skip a scheduled run; the next one catches up, and the series carries no gap because every snapshot is timestamped.
Last finished daily sweep
daily-2026-11-01
never measured · method · live · planned 32,435, completed 5, 459 minutes; the daily sweep is due at 03:47 UTC
Sweep runs open and unexplained
2
as of 2026-11-01 03:49 UTC · method · live · open, not finished, and carrying no recorded reason; oldest started 2026-11-01 03:49 UTC
A run that stops without being closed leaves its row open. Until a reason is recorded against it, this figure counts it, because a row nobody has explained is the shape a new fault takes.
Rows abandoned before the identifier fix
15
never measured · method · live · recorded, never closed: these runs did not finish and no finish time was invented for them
Until 15 September 2026 a new-listings run took its identifier from the clock, so a second call could never re-enter the first call's row and every restart and every chunk boundary abandoned one. The rows stay open with a reason recorded against them, and this count does not go away: it is the record of the period when the fault existed.
Quality snapshots taken
123
as of 2026-11-01 05:59 UTC · method · live · 2,516,144 rows, never deleted
Registry pulls, all time
246 ok · 2 failed
as of 2026-11-01 05:59 UTC · method · live · Binance since 2026-09-10 19:08 UTC; Coinbase since 2026-09-10 19:08 UTC

Registry pulls, most recent first

One row per registry per run. A pull outside the six-hour schedule is a manual run.passfail

Recent registry pulls with their timing, record counts and outcome
started, UTCregistrysecondsrecords pulledregistry reportedrequestsoutcome
2026-11-01 05:59 UTCBinance51,0101,01011pass
2026-11-01 05:59 UTCCoinbase2028,15628,15629pass
2026-10-13 14:10 UTCBinance499399310pass
2026-10-13 14:08 UTCCoinbase6832,06231,54733pass
2026-10-13 00:39 UTCBinance599399310pass
2026-10-13 00:37 UTCCoinbase7333,53032,76934pass
2026-10-12 15:21 UTCBinance499399310pass
2026-10-12 15:20 UTCCoinbase7133,35632,67934pass
2026-10-12 05:55 UTCBinance499399310pass
2026-10-12 05:54 UTCCoinbase7732,40832,40833pass
2026-10-11 21:57 UTCBinance599399310pass
2026-10-11 21:56 UTCCoinbase6532,26632,26633pass
2026-10-11 12:48 UTCBinance499399310pass
2026-10-11 12:46 UTCCoinbase6632,20332,20333pass
2026-10-11 05:45 UTCBinance599399310pass
2026-10-11 05:44 UTCCoinbase5732,06032,06033pass

Sweeps, most recent first

Daily sweeps cover every listed endpoint; “new” sweeps probe listings first seen at a pull, in chunks of 200, each chunk its own run. Planned is counted when a run first starts, and endpoints listed later in the day join the daily sweep, so completed can exceed planned. A run that is due shows as due; a run that is late shows as a failure of the collector, in the same table.passunobservedmalformedfail

Recent sweeps with their plan, completion and outcome
runkindstarted, UTCfinished, UTCplannedcompletedstopped becauseoutcome
new-after-daily-2026-11-01new2026-11-01 07:13 UTCnot finished11,1092,106—unobserved
daily-2026-11-01daily2026-11-01 03:49 UTCnot finished32,4355—unobserved
daily-2026-10-31daily2026-10-31 08:30 UTCnot finished32,4353,760supersededunobserved
daily-2026-10-30daily2026-10-30 04:19 UTC2026-10-30 13:00 UTC32,43532,435—pass
daily-2026-10-29daily2026-10-29 04:45 UTC2026-10-29 12:42 UTC32,43532,435—pass
daily-2026-10-28daily2026-10-28 05:46 UTC2026-10-28 13:07 UTC32,43532,435—pass
daily-2026-10-27daily2026-10-27 05:43 UTC2026-10-27 12:46 UTC32,43532,435—pass
daily-2026-10-26daily2026-10-26 05:39 UTCnot finished32,43523,220supersededunobserved
daily-2026-10-25daily2026-10-25 05:20 UTCnot finished32,435175supersededunobserved
daily-2026-10-24daily2026-10-24 07:06 UTCnot finished32,43510,227supersededunobserved

Snapshot cadence

Hours between consecutive quality snapshots. The schedule is six; a shorter gap is a manual pull, a longer one a delayed or skipped scheduled run.

Recent quality snapshots and the hours since the previous one
snapshot, UTCendpoints with countershours since previous
2026-11-01 05:59 UTC28,154447.8
2026-10-13 14:08 UTC31,49913.5
2026-10-13 00:37 UTC32,7639.3
2026-10-12 15:20 UTC32,5619.4
2026-10-12 05:54 UTC32,4068.0
2026-10-11 21:56 UTC32,2659.2
2026-10-11 12:46 UTC32,1797.0
2026-10-11 05:44 UTC32,0598.0
2026-10-10 21:42 UTC31,9749.2
2026-10-10 12:29 UTC32,2486.7
2026-10-10 05:49 UTC33,8087.2
2026-10-09 22:37 UTC34,7779.4

Alerts

Every alert the collector raised, collapsed by message, and every crash-loop pause of the sweep worker. What happened is published; the driver text behind it is not.

Alerts and crash-loop pauses, most recent first
last at, UTCwhattimesfirst at, UTC
2026-11-01 10:21 UTCalert: worker exited12026-11-01 10:21 UTC
2026-11-01 08:14 UTCalert: worker exited12026-11-01 08:14 UTC
2026-11-01 05:11 UTCalert: worker exited12026-11-01 05:11 UTC
2026-11-01 00:06 UTCalert: worker exited12026-11-01 00:06 UTC
2026-10-31 15:40 UTCalert: worker exited12026-10-31 15:40 UTC
2026-10-31 14:43 UTCalert: worker exited22026-10-31 09:33 UTC
2026-10-31 14:41 UTCalert: worker exited12026-10-31 14:41 UTC
2026-10-31 14:26 UTCalert: worker exited12026-10-31 14:26 UTC
2026-10-31 13:20 UTCalert: worker exited12026-10-31 13:20 UTC
2026-10-31 13:13 UTCalert: worker exited12026-10-31 13:13 UTC

Worker starts

414 starts of the sweep worker on record, the first at , the latest at . A start is normal after a deploy or a laptop wake; the crash-loop guard counts starts in a ten-minute window and pauses the worker when there are too many, and a pause is listed above.

The latest 60 of 414 starts
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 3 start(s) in the last 10 min
  • · 2 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 2 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 2 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 2 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 4 start(s) in the last 10 min
  • · 3 start(s) in the last 10 min
  • · 2 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 4 start(s) in the last 10 min
  • · 5 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 2 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min
  • · 2 start(s) in the last 10 min
  • · 1 start(s) in the last 10 min

Performance baseline

Lighthouse on an endpoint page already in the cache, mobile emulation, slow 4G, four-times CPU slowdown. Every column names its method, because a reading is not comparable with one taken differently. The 13 September reading was taken before the redesign and its own method was not recorded, so it is not a like-for-like pair with any column beside it. Lighthouse 12.8 was then run twice on the strip-chart recorder and twice again on the posted board that replaced it, once under simulated throttling, its default, and once under applied. The budget is held to the applied readings, which are the measured ones; under simulation the largest contentful paint fails the same budget in both worlds, and all four stand here. The board adds three server-rendered figures and a second font, which is the 29 KiB between the two transfer figures.

Lighthouse baseline figures and their budgets
measure13 Sep, method not recorded14 Sep, recorder, simulated14 Sep, recorder, applied14 Sep, board, simulated14 Sep, board, appliedbudget
Performance score9297989899—
First contentful paint1.2 s1.0 s1.7 s0.9 s1.6 s—
Largest contentful paint1.5 s2.6 s, over1.7 s, under2.4 s, over1.6 s, underunder 1.8 s
Cumulative layout shift00, under0, under0, under0, underunder 0.05
Total blocking time300 ms80 ms120 ms40 ms70 ms—
Transferred237 KiB256 KiB256 KiB285 KiB286 KiB—

The site ships no client script beyond the framework's deferred bundle and one small control that fills the access date in citations. The budgets and the framework decision are recorded on the method page.