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.
- Last successful registry pull
- 2026-09-15 16:57 UTC
- Last finished daily sweep
- daily-2026-09-15
- Completed exceeds planned by 185: planned is counted once when the first chunk starts, and endpoints listed by a pull during the day join the same sweep, so the difference is the day's new listings that were swept.
- Sweep runs left open
- 10
- A new-listings run is closed only when its last chunk clears the queue, so a run that filled its chunk stays open on purpose. These did not: the worker stopped part-way and restarted, which opens a fresh run rather than resuming the old one, and the abandoned row stays. The endpoints they had not reached were swept by the run that followed, so the record has no hole; the rows do.
- Quality snapshots taken
- 28
- Registry pulls, all time
- 56 ok · 2 failed
Registry pulls, most recent first
One row per registry per run. A pull outside the six-hour schedule is a manual run.passfail
| started, UTC | registry | seconds | records pulled | registry reported | requests | outcome |
|---|---|---|---|---|---|---|
| 2026-09-15 16:58 UTC | Binance | 5 | 980 | 980 | 10 | pass |
| 2026-09-15 16:57 UTC | Coinbase | 19 | 16,043 | 16,043 | 17 | pass |
| 2026-09-15 11:43 UTC | Binance | 4 | 980 | 980 | 10 | pass |
| 2026-09-15 11:42 UTC | Coinbase | 22 | 15,853 | 15,853 | 16 | pass |
| 2026-09-15 04:53 UTC | Binance | 5 | 980 | 980 | 10 | pass |
| 2026-09-15 04:52 UTC | Coinbase | 23 | 15,577 | 15,577 | 16 | pass |
| 2026-09-14 21:49 UTC | Binance | 4 | 980 | 980 | 10 | pass |
| 2026-09-14 21:48 UTC | Coinbase | 23 | 15,798 | 15,400 | 17 | pass |
| 2026-09-14 12:44 UTC | Binance | 4 | 980 | 980 | 10 | pass |
| 2026-09-14 12:43 UTC | Coinbase | 25 | 15,382 | 15,382 | 16 | pass |
| 2026-09-14 04:54 UTC | Binance | 3 | 980 | 980 | 10 | pass |
| 2026-09-14 04:54 UTC | Coinbase | 23 | 15,385 | 15,385 | 16 | pass |
| 2026-09-13 20:49 UTC | Binance | 4 | 980 | 980 | 10 | pass |
| 2026-09-13 20:48 UTC | Coinbase | 19 | 15,352 | 15,352 | 16 | pass |
| 2026-09-13 16:15 UTC | Binance | 4 | 980 | 980 | 10 | pass |
| 2026-09-13 16:15 UTC | Coinbase | 22 | 15,189 | 15,189 | 16 | pass |
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
| run | kind | started, UTC | finished, UTC | planned | completed | stopped because | outcome |
|---|---|---|---|---|---|---|---|
| new-2026-09-15T17-01-37-864Z | new | 2026-09-15 17:01 UTC | 2026-09-15 17:02 UTC | 81 | 81 | — | pass |
| new-2026-09-15T16-58-41-653Z | new | 2026-09-15 16:58 UTC | stopped at the 200 chunk, continued by the next run | 281 | 200 | — | pass |
| new-2026-09-15T11-46-48-266Z | new | 2026-09-15 11:46 UTC | 2026-09-15 11:48 UTC | 85 | 85 | — | pass |
| new-2026-09-15T11-44-05-153Z | new | 2026-09-15 11:44 UTC | stopped at the 200 chunk, continued by the next run | 285 | 200 | — | pass |
| new-2026-09-15T04-54-30-491Z | new | 2026-09-15 04:54 UTC | 2026-09-15 04:56 UTC | 191 | 191 | — | pass |
| daily-2026-09-15 | daily | 2026-09-15 03:47 UTC | 2026-09-15 07:10 UTC | 15,523 | 15,708 | — | pass |
| new-2026-09-14T21-49-38-378Z | new | 2026-09-14 21:49 UTC | 2026-09-14 21:52 UTC | 196 | 196 | — | pass |
| new-2026-09-14T12-45-19-314Z | new | 2026-09-14 12:45 UTC | 2026-09-14 12:45 UTC | 41 | 41 | — | pass |
| new-2026-09-14T04-56-17-031Z | new | 2026-09-14 04:56 UTC | 2026-09-14 04:57 UTC | 77 | 77 | — | pass |
| daily-2026-09-14 | daily | 2026-09-14 03:47 UTC | 2026-09-14 06:36 UTC | 15,476 | 15,522 | — | pass |
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.
| snapshot, UTC | endpoints with counters | hours since previous |
|---|---|---|
| 2026-09-15 16:57 UTC | 16,039 | 5.3 |
| 2026-09-15 11:42 UTC | 15,849 | 6.8 |
| 2026-09-15 04:52 UTC | 15,573 | 7.1 |
| 2026-09-14 21:48 UTC | 15,395 | 9.1 |
| 2026-09-14 12:43 UTC | 15,378 | 7.8 |
| 2026-09-14 04:54 UTC | 15,381 | 8.1 |
| 2026-09-13 20:48 UTC | 15,348 | 4.6 |
| 2026-09-13 16:15 UTC | 15,184 | 4.4 |
| 2026-09-13 11:49 UTC | 14,571 | 7.1 |
| 2026-09-13 04:45 UTC | 14,647 | 8.0 |
| 2026-09-12 20:44 UTC | 14,609 | 0.1 |
| 2026-09-12 20:40 UTC | 14,609 | 0.1 |
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.
| last at, UTC | what | times | first at, UTC |
|---|---|---|---|
| 2026-09-14 19:29 UTC | alert: worker exited | 1 | 2026-09-14 19:29 UTC |
| 2026-09-14 01:57 UTC | alert: worker exited | 1 | 2026-09-14 01:57 UTC |
| 2026-09-13 08:43 UTC | alert: worker exited | 2 | 2026-09-11 19:40 UTC |
Worker starts
36 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.
Every recorded start, 36
- · 1 start(s) in the last 10 min
- · 1 start(s) in the last 10 min
- · 4 start(s) in the last 10 min
- · 4 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
- · 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
- · 2 start(s) in the last 10 min
- · 2 start(s) in the last 10 min
- · 2 start(s) in the last 10 min
- · 2 start(s) in the last 10 min
- · 1 start(s) in the last 10 min
- · 2 start(s) in the last 10 min
- · 2 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
- · 2 start(s) in the last 10 min
- · 1 start(s) in the last 10 min
- · 4 start(s) in the last 10 min
- · 2 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.
| measure | 13 Sep, method not recorded | 14 Sep, recorder, simulated | 14 Sep, recorder, applied | 14 Sep, board, simulated | 14 Sep, board, applied | budget |
|---|---|---|---|---|---|---|
| Performance score | 92 | 97 | 98 | 98 | 99 | — |
| First contentful paint | 1.2 s | 1.0 s | 1.7 s | 0.9 s | 1.6 s | — |
| Largest contentful paint | 1.5 s | 2.6 s, over | 1.7 s, under | 2.4 s, over | 1.6 s, under | under 1.8 s |
| Cumulative layout shift | 0 | 0, under | 0, under | 0, under | 0, under | under 0.05 |
| Total blocking time | 300 ms | 80 ms | 120 ms | 40 ms | 70 ms | — |
| Transferred | 237 KiB | 256 KiB | 256 KiB | 285 KiB | 286 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.