API availability
CheckingWaiting for the first response.
Current health of the indexer and API, read from GET /api/health.
Asking the API for its current health.
Waiting for the first response.
How recently the API reloaded stored events into memory. It reloads every 30 seconds.
The last block the indexer finished and saved. The checkpoint normally moves every 30 seconds.
Events older than this are removed from the API, and from storage by a lifecycle rule. Older activity is still on Etherscan.
The indexer reads a block only once it is this many blocks behind the newest one. This lowers reorganization risk but is not a finality guarantee.
Each signal is judged on its own and the summary shows the most serious one. Thresholds are counted in missed cycles: the indexer and the API both run every 30 seconds.
| State | Rule | What visitors see |
|---|---|---|
| Healthy | Status "ok", index refreshed under 90 s ago, checkpoint under 2 min old | Transfers appear about 1 to 3 minutes after their block |
| Delayed | Index 90 s to 5 min old, or checkpoint 2 to 5 min old | Data is correct but new transfers arrive late |
| Degraded | HTTP 200 with status "degraded": a refresh or checkpoint read failed | Results load but may stop updating |
| Stale | Index or checkpoint more than 5 min old | Recent transfers are missing. The API refuses at 10 min |
| Unavailable | HTTP 503, any other error status, or no response | The monitor cannot load transfers |
| Paused | The site was built in maintenance mode. No requests are made | Docs work. Monitoring returns on the stated date |
This page shows the current state only. Uptime history and incident records are not collected, so none are shown.