What happened
A plain-language description of the incident, with the user-visible symptom first and the technical cause second.
Incident history
Honest history. Post-mortems on the public record.
Every confirmed security or reliability incident that affected our users gets a public entry here, with a post-mortem within 14 days of resolution. Operational maintenance windows and ordinary deployments don't appear — that lives on the status page.
All-time log
From launch to now.
| Date | Severity | Surface | Summary | Post-mortem |
|---|---|---|---|---|
|
No incidents to date
No reportable security or user-impacting incidents have occurred since Aevrix Group services launched. This page updates within 24 hours of any future incident reaching the disclosure threshold below. |
||||
What we disclose
The threshold.
- 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 the product as designed.
- Any successful intrusion of Aevrix-controlled infrastructure, even if no user data was reached.
- Any incident where regulators require notification (e.g., a personal-data breach under GDPR Art. 33).
Post-mortem structure
Every report has these fields.
Impact
Scope and severity. How many users were affected, what data classes, and the duration of impact.
Root cause
The contributing technical, process, and human factors. We refuse to name a single person as the cause.
What we changed
The fix, plus the systemic changes we made so a similar incident becomes less likely. Tracked publicly.
Reporting an incident?
If you believe something is currently broken or actively under attack, write directly.