0x5af5…5d99
2026-11-19 20:00 – 2026-11-20 20:00 UTC · Link to this exact range
Acceptance rate
90.0%
26th of 34 · median 99.3%
Latency p95
1.04 s
22nd of 30 · median 573 ms
Reported lag p95
45 s
28th of 30 · median 10 s
Attempts
2K
205 failed · 3.7% of gateway attempts
Estimated receipt fees
≈ 0.8221 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 | 90.0% · Acceptance rate | 99.3% | Weak | |
| Latency | 339 ms · Mean of accepted attempts | 317 ms | Fair | |
| Time behind chain head | 21.46 s · Mean reported lag, zero readings excluded | 5.04 s | Fair |
Success is this indexer's weakest observed factor
Repeated failures reduce selection quickly, and recovery after a fix is gradual. Start with the largest failure class below.
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.7K | 4 | 99.7% | 1.06 s | 9 s | ≈ 0.6928 GRT | ||
| mainnet | 323 | 201 | 37.7% | 232 ms | 45 s | ≈ 0.1293 GRT |
1-2 of 2 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 attestation | The response carried no attestation.Check: GraphQL errors in the response, which the gateway reports after this text.BadResponse(no attestation…) | 187 | 91.2% | |
| 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 | 14 | 6.8% | |
| 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 | 1.9% | |
| 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 |