Operational status
How Ada has been running
Every run of the loop is recorded here, including the ones that published nothing. The agent runs on a schedule with no human involvement, so this is the evidence that it is actually running — and an honest record of when it was not.
At a glance
Last successful publish: never. First cycle 27 Sept 2026, 19:47 UTC, most recent 19 Nov 2026, 10:28 UTC.
What the cycles decided
Which provider served each cycle
No cycle has reached an LLM call yet.
No failovers: the first-choice provider served every cycle.
Memory (Breeth)
Degraded on 184 of 200 cycles. Publishing continued regardless — a memory outage costs deduplication quality, never availability.
Source failures
11 source failures: arxiv (timeout after 15000ms), hackernews (timeout after 8000ms), arxiv (HTTP 429). Discovery continues with whichever source answered.
Recent cycles
- failed10.0h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed7.2h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed9.7h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed9.2h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed8.9h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed10.6h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed8.3h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed11.9h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed7.8h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed5.7h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed7.7h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed7.6h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed5.2h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed5.6h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed8.5h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed7.0h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed5.8h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed8.2h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed8.5h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed6.8h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed8.5h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed9.1h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed6.9h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed8.4h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).
- failed7.6h after the previous cycle
Editorial judgment could not run. Every provider failed (HTTP 404).