Status

Operational

Last checked Thu, 24 Sep 2026 00:40:35 GMT
  • Aggregate refresh is behind schedule
  • Settlement backfill is not draining

Ingestion pipeline

1 of 1 chain pipeline current · ~46.8 settlements/min at the cursor · 82,193 services catalogued

Capture loop runningnext pass within 10s
Base
Current
eip155:8453
Current block
51,710,543
Indexed block
51,710,536
Behind
7 blk
14s
Catch-up ETA
Caught up
30 blk/min
Last settlement
16s ago
Settlements indexed
≈162,162,115
Settlements indexed per hour
102,319 in the last 12h
-11hThis hour (partial)

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. 35,109,526 settlements have been recovered this way.

Historical recovery

Parts of the record are still being rebuilt behind the live feed. Every other figure on this page says whether a pass is running; these say whether it is finishing. A stretch missing from a facilitator chart is usually a queue below that has not reached it yet rather than a gap in the chain.

  • Settlement backfillBase

    Not draining

    13,736,610 blocks outstanding

    Not draining over the last 24h. The pass may be running and finding nothing it can resolve.

    Indexed down to block 35,664,817; stops at 21,928,207.

    Walking backwards from where the forward pass started towards the earliest date any known relayer could have settled.

  • Facilitator attributionBase

    Complete

    Nothing outstanding.

    Which operator relayed each settlement. Until a settlement is attributed it sits under “route unresolved” and appears in no facilitator’s series.

  • Gap repairBase

    Complete

    Nothing outstanding.

    Block ranges the continuity audit found short, being re-indexed through the same pipeline as live capture.

All 8 aggregate rollups are inside their refresh budget. 2 were refreshed off-cadence by the recovery watchdog in the last 24h, which means their scheduled refresh is not keeping up.

Background services

  • Entity resolution
    ENS + ERC-8004 identity · every 5 min
    3m ago
    Last activity
  • Aggregate refresh
    3 of 8 views are losing refresh runs to their time limit · detail available to operators
    12h ago
    Last activity
  • Discovery regeneration
    discovery.{md,json} → object storage · every 5 min
    57s ago
    Last activity
  • ERC-8004 agent indexing
    registry enumeration · round-robin slot
    2m ago
    Last activity
  • Facilitator discovery
    relayer detection + sampling · round-robin slot
    8m ago
    Last activity
  • History backfill (indexed) · eip155:8453
    the same history through the indexed connector · the fast path
    5s ago
    Last activity
  • Attribution (indexed) · eip155:8453
    who relayed the rows captured before attribution ran · one query per window
    8s ago
    Last activity
  • Settlement capture · eip155:8453
    marker → collapse → attribute · continuous
    9s ago
    Last activity
  • Settlement backfill · eip155:8453
    walking back towards the registry’s earliest first_tx
    14s ago
    Last activity
  • Continuity audit · eip155:8453
    on-chain markers vs stored settlements, block by block
    40s ago
    Last activity
  • Indexed provider · eip155:8453
    second capture provider · one query per window
    5m ago
    Last activity
  • Fee-proxy corrections
    payee + amount corrected on pre-collapse rows · round-robin slot
    7d ago
    Last activity
  • Service enrichment
    catalog liveness + volume · twice hourly
    24m ago
    Last activity
  • Web enrichment
    favicon + description + host geo · 14/30-day staleness gates
    25m ago
    Last activity

Checks run from the dashboard's server runtime on every request to this page. Latency figures include the round-trip from the dashboard 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.