Home / Incidents
Incident history
Every confirmed security or reliability incident that affected Axion users gets a public entry here, with a post-mortem within 14 days of resolution. Ordinary deployments and maintenance windows live on the status page.
All-time log
| Date | Severity | Surface | Summary | Post-mortem |
|---|---|---|---|---|
|
No incidents to date No reportable security or user-impacting incidents have occurred. This page updates within 24 hours of any future incident reaching the disclosure threshold below. |
||||
What we disclose
- Any incident where user data was, may have been, or was likely to have been exposed to an unauthorised party.
- Any incident where the integrity of user data was, may have been, or was likely to have been compromised.
- Any extended outage (≥ 1 hour for a billed service, ≥ 4 hours for a free service) that prevented users from using Axion as designed.
- Any successful intrusion of Aevrix-controlled infrastructure, even if no user data was reached.
- Any incident where regulators require notification (e.g., GDPR Art. 33 personal-data breach).
Post-mortem structure
Every post-mortem published here will include:
- What happened — plain-language description, user-visible symptom first, technical cause second.
- Impact — scope and severity. How many users were affected, which data classes, duration of impact.
- Root cause — contributing technical, process, and human factors. We refuse to name a single person as the cause.
- What we changed — the fix plus systemic changes so a similar incident becomes less likely. Tracked publicly.
Active incident reporting
If you believe something is currently broken or actively under attack, write directly: security@axionchat.chat.