0xf92f…a6d4
2026-11-19 20:00 – 2026-11-20 20:00 UTC · Link to this exact range
Acceptance rate
99.8%
6th of 34 · median 99.3%
Latency p95
755 ms
18th of 30 · median 573 ms
Reported lag p95
14 s
21st of 30 · median 10 s
Attempts
3.6K
4 failed · 6.5% of gateway attempts
Estimated receipt fees
≈ 1.514 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.8% · Acceptance rate | 99.3% | Strong | |
| Latency | 317 ms · Mean of accepted attempts | 317 ms | Fair | |
| Time behind chain head | 4.18 s · Mean reported lag, zero readings excluded | 5.04 s | Strong |
Latency is a little below the median indexer
Only successful responses count toward latency, and a request that times out after 20 seconds counts as a failure.
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 | 2.7K | 4 | 99.8% | 619 ms | 3 s | ≈ 1.1 GRT | ||
| mainnet | 536 | 0 | 100.0% | 143 ms | 12 s | ≈ 0.2587 GRT | ||
| mainnet | 239 | 0 | 100.0% | 1.38 s | 15 s | ≈ 0.11 GRT | ||
| arbitrum-one | 87 | 0 | 100.0% | 1.16 s | 5 s | ≈ 0.03899 GRT | ||
| mainnet | 5 | 0 | 100.0% | 2.94 s | Unavailable | ≈ 0.001964 GRT | ||
| arbitrum-sepolia | 3 | 0 | 100.0% | 128 ms | 1 s | ≈ 0.001582 GRT | ||
| arbitrum-sepolia | 2 | 0 | 100.0% | 232 ms | Unavailable | ≈ 0.001027 GRT | ||
| arbitrum-one | 2 | 0 | 100.0% | 128 ms | Unavailable | ≈ 0.0008292 GRT | ||
| arbitrum-one | 1 | 0 | 100.0% | 13.38 s | Unavailable | ≈ 0.0004156 GRT | ||
| arbitrum-one | 1 | 0 | 100.0% | 1.12 s | Unavailable | ≈ 0.0006251 GRT |
1-10 of 10 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 | 100.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. | 1 | Not applicable |