infradao.eth
Eligible8 of 29 days published
The rest of the window has not been published to the metrics subgraph, so those days are unknown and online-day counts are a lower bound. Eligibility itself always comes from the contract.
- Contract status
- Eligible
- Last renewed 7 Oct 2026, 10:00 UTC
- Eligible until
- 21-Oct-2026
- At least Nov 13 even if no further day qualifies
- Next run · Oct 8
- Will be renewed
- 8 of 5 online days at 5 subgraphs/day
- Online days
- 8 of 29
- 5 required
Last 29 days
Each day as the oracle counted it. Select a day for its numbers.
Sep 9Oct 7
- Online day
- Did not qualify
- Not routed
- No data published
- 5 online days required
Tue, Oct 6, 2026
Online day- 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
8 of 8 published days counted.
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.
Subgraphs per day
Online days required
15+0
5 subgraphs
Sep 9Oct 7
- Today’s rule · 5 subgraphs
- 8 online days
- Would qualify
- Simulated · 5 subgraphs, 5 days
- 8 online days
- Would qualify
Query this yourself
Everything above comes from the . Build your own alerting on it.
{
indexer(id: "0x63c9dc729ba7a22bb8605216b24a34b902e5fe94") {
onlineDays
daysWithAttempts
lastDayWithAttempts { date }
days(
where: { dayNumber_gte: 20705 }
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