Status · live
Live telemetry.
The site’s own instruments, in public. Events on the ops bus, MCP calls, challenges satisfied, queue depth and a one-minute canary — read live from the stores that hold them.
- Ops · events (24h)500reporting· just now
- MCP · requests (24h)0no data· just now
- Challenge · satisfied (24h)0no data· just now
- DLQ · depth0msgsreporting· just now
- Canary · last tick13s agoreporting· just now
Live feed
What the site is doing right now.
- Last 60s
- 0
- Waiting for the first event…
Events on aethelforge.ai’s own bus. Client addresses and tenant identifiers are never shown.
In one paragraph
What does aethelforge.ai/status show?
The status page publishes the site’s live telemetry: events reaching the ops bus in the last day, MCP requests, challenges satisfied, dead-letter queue depth and the last canary tick. Every tile is read on request from its source store; a tile with no data says so rather than showing a placeholder.
Every tile is derived from a live source — DynamoDB, SQS or the one-minute canary — with the data path in its hover hint. A tile that reads no data has a reachable source and an empty counter. One that reads alert is already being looked at.
The Index is published separately, on fixed windows, and signed. This page is what the site is doing right now.
FAQ
Status, answered.
01Is this the Index?
No. The Index is a fixed, signed window of inbound across the fleet’s channels. This page is the live telemetry of aethelforge.ai itself — the events its own endpoints generate. The two are published separately on purpose: one is citable, the other is current.
02How often does it update?
Tiles are recomputed at most every five minutes and read directly from DynamoDB, SQS and the canary. The live feed below streams events to the browser as they land on the bus.
03What is the canary?
A scheduled tick emitted every minute onto the same bus as every other event. If the last tick is more than a couple of minutes old, delivery from the bus to the stores is broken, and the tile says so.
04Why publish this at all?
A service that counts other people’s inbound should show its own instruments working. If this page ever goes quiet, treat every other claim on the site accordingly.