Comfora Incidents

Long-term incident reporting and post-mortems powered by Incident.io
View status page »

How this repository works

When a incident happens on Comfora Servers, Services or dependent¹ services with Comfora, we write a technical post-mortem on...

• What Happend?
• How did it happen?
• Steps we took to recover.
• What could we have done differently?

incidents/
├─ post-mortems/
│  ├─ 2026/
│  │  ├─ 2026-12-31.md <-- YYYY-MM-DD formatted file; Example on how post-mortems are published.

This is meant to give long-term storage and document incidents as to remain transparent with the community and how you can learn from our mistakes.

Footnotes

1. Services we depend on are, for instance, Github are non maintained by Comfora as such we cannot control downtime. We will continue to write a post-mortem on how we can improve however with less details. Self-hosted or Comfora maintained services for instance, Github Enterprise Server allows us to have detailed post-mortems. ↩