0x32bb…157b
Eligible- Contract status
- Eligible
- Last renewed 19 Nov 2026, 10:00 UTC
- Eligible until
- 3-Dec-2026
- At least Dec 23 even if no further day qualifies
- Next run · Nov 21
- Will be renewed
- 14 of 5 online days at 10 subgraphs/day
- Online days
- 14 of 29
- 5 required
Last 29 days
Each day as the oracle counted it. Select a day for its numbers.
- Online day
- Did not qualify
- Not routed
- No data published
- 5 online days required
Thu, Nov 19, 2026
Error responsesMost failing responses were not 200 OK.
- Qualifying subgraphs
- Qualifying queries
- Query attempts
- Not 200 OK
- 5,000 ms or slower
- 50,000+ blocks behind
One response can fail more than one check, so the failure counts overlap and need not add up.
Why days did not count
14 of 28 published days counted. For the rest, the main reason:
- Too few subgraphs11 days
Qualifying queries landed on fewer subgraphs than the day requires.
- Error responses3 days
Most failing responses were not 200 OK.
Daily breakdown
The published counters, newest first. Subgraphs and queries count qualifying ones only. The three failure columns overlap: one slow, stale response counts in both.
Criteria simulator
Qualifying subgraphs per day against a threshold. Latency and chainhead limits cannot be simulated, since they decide which queries qualify in the first place.
- Today’s rule · 10 subgraphs
- 14 online days
- Would qualify
- Simulated · 10 subgraphs, 5 days
- 14 online days
- Would qualify
Query this yourself
Everything above comes from the . Build your own alerting on it.
{
indexer(id: "0x32bbd16a94ebb289edceebe77f35acc82664157b") {
onlineDays
daysWithAttempts
lastDayWithAttempts { date }
days(
where: { dayNumber_gte: 20749 }
orderBy: dayNumber
orderDirection: desc
) {
date isFinal isOnlineDay
queryAttempts qualifyingQueries qualifyingSubgraphs
failedStatus failedLatency failedBlocksBehind
}
}
}Where these numbers come from
- Eligibility
- Daily metrics
- Latest run
- Window
- Criteria
- Metrics transaction