Fortanix SaaS incident

DSM Saas | EU region | timeouts issue in the Frankfurt region | Monitoring

Notice Resolved View vendor source →
Started
Apr 24, 2026, 02:14 PM UTC
Resolved
Apr 26, 2026, 07:22 AM UTC
Duration
1d 17h
Detected by Pingoru
Apr 24, 2026, 02:14 PM UTC

Affected components

Service availabilityKey ManagementKey usage (Cryptographic operation)

Update timeline

  1. 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.

  2. monitoring Apr 24, 2026, 05:50 PM UTC

    We are continuing to monitor for any further issues.

  3. 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.

  4. resolved Apr 26, 2026, 07:22 AM UTC

    Services have remained stable since recovery, with no further impact observed

Looking to track Fortanix SaaS downtime and outages?

Pingoru polls Fortanix SaaS's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Fortanix SaaS reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Fortanix SaaS alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Fortanix SaaS for free

5 free monitors · No credit card required