Service status

Status page#

The public page aicscan.io/statut shows, without logging in:

• the reading state of each chain (up to date or late, seconds since the last block);
• the cross-checks of the last 7 days: events verified against an independent source and missed events;
• the delay between the block and alert delivery over 7 days (median and 95th percentile);
• the outcome of the canary alert sent end to end at regular intervals over 30 days;
• the incidents of the last 30 days.

GET /v1/health#

For automated monitoring, use GET /v1/health. It is public (no key), counts toward no quota and returns no customer data.

curl https://aicscan.io/v1/health

{
  "at": "2026-11-14T09:31:02.551Z",
  "chains": [
    { "chain_id": 56, "name": "BNB Chain", "up": true, "last_processed_block": 45123470, "last_confirmed_block": 45123455, "seconds_since_block": 1.2 },
    { "chain_id": 728126428, "name": "TRON", "up": true, "last_processed_block": 77104412, "last_confirmed_block": 77104393, "seconds_since_block": 2.8 }
  ],
  "status": "ok",
  "api_version": "1"
}

A high seconds_since_block (several minutes) means reading is late: alerts for that chain will arrive late, without being lost. After an interruption, the reader catches up on the missed blocks and every late alert says so in its text.

During an incident#

• Workspaces are notified on their channels with a type: "service" message when monitoring of a chain is interrupted and when it recovers.
• During an API outage, alerts keep being produced and delivered to your channels; your calls may receive 5xx: retry with increasing delays and the same Idempotency-Key.
• After a real-time disconnect, reconnect with last_id: missed alerts are replayed (7 days).