Validator Ops
Is it me or the network?
Live
For your validator and a window: whether missed votes or skipped slots were yours, the network's, or your client's or region's, with the evidence, signed; plus the cluster's incident feed.
Included in: Validator Ops (every size).
Each correlation, incident and the feed are signed by the service’s own key, listed in /attest/keys.json.
Endpoints
Served from http://186.233.184.235:8080. Send a key as Authorization: Bearer psol_…. Indexes and status files need no key.
/incidents/correlate.json?vote=<vote>&at=<time>/incidents/feed.json
curl -fsS -H "Authorization: Bearer psol_…" "http://186.233.184.235:8080/incidents/correlate.json?vote=<vote>&at=2026-10-23T16:35:00Z&minutes=5"Access and limits
monitor: Validator Ops' managed features: monitor subscriptions, webhooks and dashboards, the delegation guard, maintenance windows.
| Plan | monitor | Data a month |
|---|---|---|
| Validator Ops, up to 1.5M SOL | 5 requests a second, bursts of 20 | 2 TB per key |
| Validator Ops, up to 5M SOL | 10 requests a second, bursts of 40 | 5 TB per key |
| Validator Ops, up to 25M SOL | 20 requests a second, bursts of 80 | 10 TB per key |
Limits apply to each key; the free tier’s apply to each address. Prices for each plan are on the plans page.