Sources
Every published event links to the original source. This page describes what is monitored and how much weight each kind of source carries.
Coverage by provider
| Provider | Monitoring since | Events | Source status |
|---|---|---|---|
| CODEXOpenAI Codex | 2025-09-17 | 44 | Fresh |
| CLAUDEAnthropic Claude | 2026-04-16 | 14 | Fresh |
Source trust levels
- S0
- Official machine-readable status or API.
- S1
- Official documentation, help centre, changelog, or an official company account.
- S2
- An approved staff account making a direct statement about their own product.
- S3
- Credible secondary reporting. Requires corroboration.
- S4
- Community reports. Supporting evidence only, never sufficient to publish.
What we do not do
- We do not ask for, store, or transmit your provider account credentials.
- We do not bypass logins, CAPTCHAs, or access restrictions.
- We do not republish source content in full. We link to the original.
- When a source is removed, we stop showing the quotation and re-evaluate the event's confidence rather than silently keeping the claim.
When sources go quiet
If monitoring is interrupted, the affected provider is marked as delayed or stale and the last successful check is shown. Stored history stays available. We never present "no reset happened" as a fresh conclusion during an outage.