0xf123…2a6f
2026-11-19 20:00 – 2026-11-20 20:00 UTC · Link to this exact range
Acceptance rate
99.4%
16th of 34 · median 99.3%
Latency p95
1.64 s
27th of 30 · median 573 ms
Reported lag p95
10 s
13th of 30 · median 10 s
Attempts
375
2 failed · 0.6% of gateway attempts
Estimated receipt fees
≈ 0.1525 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.4% · Acceptance rate | 99.3% | Strong | |
| Latency | 601 ms · Mean of accepted attempts | 317 ms | Weak | |
| Time behind chain head | 5.19 s · Mean reported lag, zero readings excluded | 5.04 s | Fair |
Latency is this indexer's weakest observed factor
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 |
|---|---|---|---|---|---|---|---|---|
| mainnet | 198 | 0 | 100.0% | 283 ms | 8 s | ≈ 0.07967 GRT | ||
| arbitrum-one | 155 | 1 | 99.3% | 687 ms | Unavailable | ≈ 0.0641 GRT | ||
| arbitrum-one | 22 | 1 | 95.4% | 13.76 s | 12 s | ≈ 0.008754 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 |
|---|---|---|---|---|
| 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 | 50.0% | |
| HTTP error status | Your indexer answered with an HTTP error status, such as a 5xx.Check: indexer-service and proxy logs for the status code at that time.BadResponse(<status code>) | 1 | 50.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 |