downHow Iszdown publishes confirmed outage briefs
An outage graph can show rising activity without proving that a service is down. The Iszdown blog is a separate incident journal: its automated outage briefs require an official major or critical incident with clear disruption evidence.
When we publish
New briefs require a recent major or critical incident with clear disruption evidence. Estimated activity and a single failed website check do not qualify by themselves. The absence of a blog post does not establish that a service was available.
Dates and status
Each article identifies the event date in UTC. First-report timestamps, resolution markers, and publication times remain distinct. A first report is not necessarily the start of downtime, and a resolution marker does not guarantee recovery for every user. One article is updated as an incident develops.
Current availability
Use dated articles to understand past incidents. Use the live service page for current status, website measurements, recorded reports, and estimated activity. The journal does not infer affected-user totals, geographic scope, root cause, or full downtime duration from a title or activity spike.