Status
Partial degradation
- Settlement backfill · eip155:8453 has not run recently
- Continuity audit · eip155:8453 is behind schedule
- Supabase RESTPostgres + PostgREST369msHTTP 200
- api-workerCloudflare control plane367msHTTP 200
- Marketing & discoveryCloudflare marketing-worker · R2455msHTTP 200
- DispatcherCloudflare dispatcher-worker · *.ioi.md269msHTTP 200
- Roundhouse read APIapi-worker · /v0 flow of funds826msHTTP 200
- Cron workerCloudflare cron-worker · discovery / CDP crawl / enrichment239msHTTP 200
- Observer workerCloudflare observer-worker · Roundhouse capture + resolve196msHTTP 200
- x402 facilitatorverify + settle endpoint296msHTTP 200
Ingestion pipeline
1 of 1 chain pipeline current · ~64.1 settlements/min at the cursor · 42,580 services catalogued
Record completeness
No known gaps in the settlement record.
A continuity audit walks back through indexed history comparing the EIP-3009 markers on chain against the settlements stored for the same blocks. Anything it cannot account for is queued and re-indexed through the normal capture pipeline. 519,676 settlements have been recovered this way.
Background services
- Entity resolutionENS + ERC-8004 identity · every 5 min3m agoLast activity
- Rollup refreshmv_global_stats every 5 min · mv_entity_* twice hourly (pg_cron)6m agoLast activity
- Discovery regenerationdiscovery.{md,json} → R2 · every 5 min21s agoLast activity
- ERC-8004 agent indexingregistry enumeration · round-robin slot7m agoLast activity
- Facilitator discoveryrelayer detection + sampling · round-robin slot2m agoLast activity
- Settlement capture · eip155:8453marker → collapse → attribute · Durable Object alarm5s agoLast activity
- Continuity audit · eip155:8453on-chain markers vs stored settlements, block by block11h agoLast activity
- Settlement backfill · eip155:8453walking back towards the registry’s earliest first_tx2d agoLast activity
- Fee-proxy correctionspayee + amount corrected on pre-collapse rows · round-robin slot4d agoLast activity
- Service enrichmentCDP catalog liveness + volume · twice hourly20m agoLast activity
- Web enrichmentfavicon + description + host geo · 14/30-day staleness gates20m agoLast activity
Checks run from the dashboard's server runtime on every request to this page. Latency figures include the round-trip from Vercel to each upstream. Catch-up ETA is derived from the observer's recent block-drain rate versus chain production. Lifetime settlement counts are planner estimates; the hourly chart is an exact count per whole UTC hour, and settlements/min is measured over the newest 1,000 rows — operational telemetry, not audited figures.