Fortanix SaaS incident
DSM Saas | EU region | timeouts issue in the Frankfurt region | Monitoring
Resolved after 1 day 17 hours, affecting Service availability and Key Management and 1 more, on April 24, 2026.
Following the incident on April 24, 2026 (12:58–13:08 UTC), services in the Frankfurt region have remained stable, and no further issues have been observed. We believe we have identified the root cause and are in the process of validating it through testing. The team is also working on corrective actions to prevent recurrence. We will provide a detailed root cause analysis once our investigation is complete.
Affected components
Update timeline
- monitoring Apr 24, 2026, 02:14 PM UTC
Between 12:58 UTC and 13:08 UTC on April 24, 2026, we observed elevated error rates and pod restarts in our Frankfurt region. All affected pods have since recovered and are currently running normally. Investigation into the root cause is ongoing.
- monitoring Apr 24, 2026, 05:50 PM UTC
We are continuing to monitor for any further issues.
- monitoring Apr 25, 2026, 06:03 PM UTC
Following the incident on April 24, 2026 (12:58–13:08 UTC), services in the Frankfurt region have remained stable, and no further issues have been observed. We believe we have identified the root cause and are in the process of validating it through testing. The team is also working on corrective actions to prevent recurrence. We will provide a detailed root cause analysis once our investigation is complete.
- resolved Apr 26, 2026, 07:22 AM UTC
Services have remained stable since recovery, with no further impact observed
Your product runs on more than Fortanix SaaS
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services