2 Oct 2026
corr_2026-10-02_001 · acknowledged
Claim
Nobody raised this. We found it reading our own Facilitators page. From 28 September the page counted three facilitators, `three.ws`, `open.x402.host` and `facilitator.openmid.xyz`, among those where our record and the settlement leaderboard differ. We had never sent any of them a request. Every row we hold for the three is an absence we filed, so the difference the page counted was a gap in our own record.
Finding
Measured on 2 October against our own archive. None of the three endpoints holds an observation at any depth: every row is `Not probed`. For `three.ws/api/x402-facilitator/supported` the host's robots.txt refuses the path, on every row since the row was added on 1 October and on all seven daily checks of the same address from 25 September to 1 October; `open.x402.host/supported` and `facilitator.openmid.xyz/supported` have rows since 26 August and none of them is an observation, and every row of the seven days we read back is filed because the host's robots.txt could not be read, so no request followed. The page compared the newest row in its two-day window with the leaderboard. A row with no answer in it fell into the case for a facilitator that was read and did not come back with a listing, and was counted as a difference; for `three.ws` the page also said no answer had reached us, when no request had been sent. All three were in the leaderboard's active population from its 27 September reading, so all three were counted from the moment the page began comparing the two records, on 28 September at 01:40 UTC. On 2 October the page read: For 7 of the 18 active facilitators the two records differ. Three of the seven were these absences. Two more were Meridian and Dexter, read on the rows `corr_2026-10-01_001` already scopes; that record covers them. The rows themselves are correct as recorded.
Remedy
Fixed forward on the page, and nothing stored is edited. The page now keeps an absence of ours out of the comparison: a facilitator whose newest row is an absence we filed, with no answer in the window that came back with a listing, is counted with the facilitators we have no reading for, and the page says so as our gap. A daily check that was never sent is read the same way. The page also reads a facilitator on the row that continues its series where a correction replaced one. After the change the page reads: For 2 of the 18 active facilitators the two records differ, and for 3 more we have no reading of our own to compare. Every row on these three endpoints stays in the archive as recorded; this record is how the page's earlier count is to be read.
How to read the affected rows
Read every row on these three endpoints as recorded: an absence we filed, never a reading of the facilitator, and never a difference with the settlement leaderboard. `three.ws` (ep_1aafc569edcb1118): its robots.txt refuses the path, and no request was sent. `open.x402.host` (ep_7af5e283b8d31e0c) and `facilitator.openmid.xyz` (ep_2a761122d539c9ad): no request has reached either since its row was added; on every row we read back, its robots.txt could not be read. The Facilitators page counted all three as differing from the leaderboard from 28 September until the change this record describes. None of the three says anything about whether the facilitator was settling; the leaderboard is the channel that does.