| Date | Region | Impact | Duration | Summary |
|---|
| 2026-09-13 | hel1 | Partial | 16 min | Replication lag exceeded the alert threshold after a large customer upload finished. |
| 2026-08-31 | ams1 | Elevated latency | 25 min | A backup job saturated the metadata disk; read latency rose until the job was rescheduled. |
| 2026-08-18 | fra1 | Partial | 11 min | A bad gateway deploy was rolled back; the error rate returned to baseline. |
| 2026-08-05 | ash1 | Maintenance | 22 min | Scheduled capacity expansion in the US region; a small share of requests were retried. |
| 2026-07-23 | hel1 | Elevated latency | 35 min | Transit provider rerouted traffic after a fibre fault; p99 in the Nordics rose for half an hour. |
| 2026-07-10 | ams1 | Read errors | 14 min | Two read nodes lost their cache after a failed firmware update and were drained and restarted. |
| 2026-06-27 | fra1 | Degraded writes | 27 min | Metadata service leader election took longer than usual; a subset of writes returned 503. |