New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages, May 2026
Services Pricing Dashboard

Fortanix SaaS Outage History

Uptime record, past incidents, and downtime history for Fortanix SaaS.

Checking current status...
74.7% uptime over 91 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

Mar 30Jun 27

Monthly Uptime

Month Uptime Days Tracked Days with Issues
June 2026 81.5% 27 5
May 2026 71% 31 9
April 2026 73.3% 30 8
March 2026 66.7% 3 1

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 91 Days)

Mar 29 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

June 2026
DSM SaaS | EU Region | Paris Datacenter Incident

Started: Jun 24, 8:02 PM

investigating
At this time, no service outage is expected. Traffic has been redirected to alternate EU SaaS datacenters, which continue to operate normally with available redundancy. However, customers whose traffic was previously served from the Paris datacenter may experience slightly increased latency due to traffic being routed through alternate locations.
Jun 24, 8:06 PM
investigating
We are continuing to investigate this issue.
Jun 24, 8:04 PM
investigating
We are currently investigating this issue.
Jun 24, 8:02 PM
May 2026
DSM SaaS AMER | Increased Latency and Pod Restarts in Ashburn Datacenter
minor

Started: May 27, 3:25 PM

monitoring
A fix has been implemented and we are monitoring the results.
May 27, 5:00 PM
identified
The issue has been identified and a fix is being implemented.
May 27, 4:27 PM
investigating
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.
May 27, 3:25 PM
April 2026
DSM Saas | EU region | timeouts issue in the Frankfurt region | Monitoring

Started: Apr 24, 2:14 PM

monitoring
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.
Apr 25, 6:03 PM
monitoring
We are continuing to monitor for any further issues.
Apr 24, 5:50 PM
monitoring
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.
Apr 24, 2:14 PM