Aggregator Head Lag
On-chain event to WebSocket emission, in seconds. Measured against canonical-tip archive nodes.
Field min · p50
0.7s
Lowest provider
Field median · p50
1.2s
Across 3 providers
Field max · p50
7.0s
Highest provider
Tail spread
10.3×
2.3 s → 24.0 s
Samples · 24h
154,490
3 providers
Head lag · last 24 hours
- GeckoTerminal10.1 s
- Codex1.5 s
- Mobula0.7 s
Provider ledger · sorted by p50
| Provider | Latency aggregates | 24-hour range | Reliability | Trend | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| № | Name | p50 | p90 | p99 | Mean | Min | Max | Δ field | Success | n | 24h | ||
| 01 | MobulaWebSocket feed | 0.7 s | 1.5 s | 2.6 s | 0.8 s | 0.5 s | 1.3 s | −76% | 99.88% | 51,551 | |||
| 02 | CodexGraphQL feed | 1.2 s | 1.6 s | 2.3 s | 1.3 s | 1.3 s | 1.8 s | −60% | 99.83% | 51,445 | |||
| 03 | GeckoTerminalREST feed | 7.0 s | 13.7 s | 24.0 s | 8.1 s | 7.3 s | 13.1 s | +136% | 99.83% | 51,494 | |||
By region
| Provider | US-East | EU-West | AP-Southeast |
|---|---|---|---|
| Mobula | 0.8 s | 0.7 s | 0.9 s |
| Codex | 1.2 s | 1.2 s | 1.3 s |
| GeckoTerminal | 7.0 s | 7.0 s | 7.2 s |
About this benchmark
We measure the gap between a transaction settling on chain and the same transaction appearing on each aggregator's data feed. The harness watches reference pools across Base, BNB Chain and Solana from three regions (us-east, eu-west, sgp), records every new on-chain event with millisecond timestamps, and observes when each aggregator's WebSocket reflects the same event. Lower is better.
Methodology
- ·Aggregators measured: Mobula, Codex, GeckoTerminal.
- ·Chains: Base, BNB Chain, Solana.
- ·Regions: us-east, eu-west, sgp. Cross-region median reported in the headline.
- ·Reference: archive nodes per chain, validated against block hashes.
- ·Metric: gauge `head_lag_seconds`, sampled every 15 seconds. Aggregated over the 24-hour window using `quantile_over_time`.
- ·Success rate: presence ratio. share of expected sampling slots where a value was actually emitted (5,760 expected per provider per day at the 15s cadence). 100% means the aggregator's feed was reachable for the full window.
- ·Cardinality: 3 aggregators × 3 chains × 3 regions = 27 active series.
Share · export · embed
Pick a layout and download a 1200×630 PNG ready for Twitter, Reddit, LinkedIn or any OG-card embed. Same data, same colors as this dashboard.
Vertical bars sorted ascending by p50, with provider names and p99 tails.
Source code github.com/OpenChainBench/OpenChainBench/tree/main/harnesses/aggregator-head-lag