0x9af3…f0d0
2026-11-19 20:00 – 2026-11-20 20:00 UTC · Link to this exact range
Acceptance rate
99.6%
12th of 34 · median 99.3%
Latency p95
595 ms
16th of 30 · median 573 ms
Reported lag p95
10 s
13th of 30 · median 10 s
Attempts
1.5K
5 failed · 2.7% of gateway attempts
Estimated receipt fees
≈ 0.6099 GRT
Not settled revenue
Observed selection factors
Observed from this range's data and set beside the median indexer on the same slice. The gateway weighs recent results differently, so an observed band is not the score the gateway used. Stake and fee also count and are not shown. How selection works
| Factor | Observed | Median indexer | Observed band | Actions |
|---|---|---|---|---|
| Success | 99.6% · Acceptance rate | 99.3% | Strong | |
| Latency | 312 ms · Mean of accepted attempts | 317 ms | Strong | |
| Time behind chain head | 5.73 s · Mean reported lag, zero readings excluded | 5.04 s | Fair |
Time behind chain head is a little below the median indexer
For queries that want the latest data, the gateway prefers indexers closer to chain head, and skips one more than 30 minutes behind whenever another is within 30 minutes.
Over time
Percentiles are approximate. Times are UTC; gaps are intervals without observations.
Deployments
| Deployment CID | Network | Attempts | Failures | Acceptance rate | Latency p95 | Reported lag p95 | Estimated receipt fees | Actions |
|---|---|---|---|---|---|---|---|---|
| arbitrum-one | 1.3K | 4 | 99.6% | 607 ms | 3 s | ≈ 0.5231 GRT | ||
| mainnet | 206 | 0 | 100.0% | 275 ms | 10 s | ≈ 0.08205 GRT | ||
| arbitrum-one | 12 | 1 | 91.6% | 17.79 s | 7 s | ≈ 0.004744 GRT |
1-3 of 3 deployments
Rows
Page 1 of 1Failures
Why this indexer's attempts failed. A failed attempt does not always fail a client's query: the gateway can answer it from another indexer.
| Failure | What it means and what to check | Count | Share of failures | Actions |
|---|---|---|---|---|
| Missing block | Your indexer reported it has not indexed the block the query needs.Check: Sync progress on the deployment and whether it was pruned below the queried block.Unavailable(missing block…) | 4 | 80.0% | |
| Timeout | No response before the gateway's timeout.Check: Slow queries or an overloaded Graph Node: compare your query latency at the same time.Timeout | 1 | 20.0% | |
| Accepted with error text | Accepted, but the response carried GraphQL error text. Not counted as a failure.Check: The GraphQL errors your Subgraph returns for these queries. | 0 | Not applicable |