rampdefi3.eth
Eligible- Contract status
- Eligible
- Last renewed 7 Oct 2026, 10:00 UTC
- Eligible until
- 21-Oct-2026
- Fixed period. Not qualifying does not shorten it
- Next run · Oct 8
- Not enough data
- 8 of 29 days published so far
- Online days
- 3 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
Sat, Oct 3, 2026
4 of 5 subgraphsQualifying queries landed on fewer subgraphs than the day requires.
- 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
3 of 8 published days counted. For the rest, the main reason:
- Error responses4 days
Most failing responses were not 200 OK.
- Too few subgraphs1 day
Qualifying queries landed on fewer subgraphs than the day requires.
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 · 5 subgraphs
- 3 online days
- Short of 5 on published days
- Simulated · 5 subgraphs, 5 days
- 3 online days
- Short of 5 on published days
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: 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