Skip to content

0xf123…2a6f

Range
Resolution

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

FactorObservedMedian indexerObserved bandActions
Success99.4% · Acceptance rate99.3%Strong
Latency601 ms · Mean of accepted attempts317 msWeak
Time behind chain head5.19 s · Mean reported lag, zero readings excluded5.04 sFair

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.

Acceptance rate
Latency, accepted attempts
Attempts
Reported lag

Deployments

Deployment CIDNetworkAttemptsFailuresAcceptance rateLatency p95Reported lag p95Estimated receipt feesActions
mainnet1980100.0%283 ms8 s≈ 0.07967 GRT
arbitrum-one155199.3%687 msUnavailable≈ 0.0641 GRT
arbitrum-one22195.4%13.76 s12 s≈ 0.008754 GRT

1-3 of 3 deployments

Rows
Page 1 of 1

Failures

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.

FailureWhat it means and what to checkCountShare of failuresActions
TimeoutNo response before the gateway's timeout.Check: Slow queries or an overloaded Graph Node: compare your query latency at the same time.Timeout150.0%
HTTP error statusYour 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>)150.0%
Accepted with error textAccepted, but the response carried GraphQL error text. Not counted as a failure.Check: The GraphQL errors your Subgraph returns for these queries.0Not applicable