Is Fortanix SaaS down?
Last checked 10m agoNo incidents right now.
Fortanix SaaS is operational right now. Last checked 10m ago; the most recent incident resolved 11d ago.
Real-time Fortanix SaaS status, recent outages, and incident history — pulled directly from Fortanix SaaS's official status page at https://status.fortanix.com every 5 minutes. Pingoru tracks 19 Fortanix SaaS services and has captured 30 incidents in the last 90 days (99.82% uptime). Get email, Slack, Discord, or webhook alerts the moment Fortanix SaaS reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 4 updates
- investigating · May 27, 2026, 03:25 PM UTC
We are currently investigating an issue impacting services in our Ashburn datacenter. Customers may experience increased latency. Our engineering team is actively working to identify the root cause and mitigate the impact. We will provide further updates as more information becomes available.
- identified · May 27, 2026, 04:27 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring · May 27, 2026, 05:00 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · May 27, 2026, 07:14 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 4 updates
- 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
Latest: Services have remained stable since recovery, with no further impact observed
-
- Started May 27, 2026, 03:25 PM UTC · Resolved May 27, 2026, 07:14 PM UTC · 3h 48m
- Started Apr 24, 2026, 02:14 PM UTC · Resolved Apr 26, 2026, 07:22 AM UTC · 1d 17h