- Detected by Pingoru
- Apr 24, 2026, 02:14 PM UTC
- Resolved
- Apr 26, 2026, 07:22 AM UTC
- Duration
- 1d 17h
Affected: 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
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 08:34 PM UTC
- Resolved
- Feb 18, 2026, 11:40 PM UTC
- Duration
- 3h 5m
Affected: Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 3 updates
-
identified Feb 18, 2026, 08:34 PM UTC
We're experiencing intermittent timeouts in the AU Perth datacenter since 18-Feb-2026 19:37 UTC. We have contacted our service provider. There should be minimal or no impact on operations. If you encounter any issues, please contact Fortanix Support.
-
monitoring Feb 18, 2026, 08:43 PM UTC
Traffic is routed to other Datacenter of AU region and we're actively monitoring.
-
resolved Feb 18, 2026, 11:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 15, 2026, 09:09 PM UTC
- Resolved
- Feb 16, 2026, 08:25 AM UTC
- Duration
- 11h 15m
Affected: Service availability
Timeline · 6 updates
-
investigating Feb 15, 2026, 08:53 PM UTC
We are currently investigating this issue.
-
identified Feb 15, 2026, 09:09 PM UTC
The issue has been identified, and mitigation actions are in progress. Customers may continue to experience intermittent errors while remediation is underway.
-
identified Feb 16, 2026, 12:10 AM UTC
We are continuing to implement corrective measures and are seeing signs of improvement. Our team remains engaged in restoring full service stability.
-
identified Feb 16, 2026, 03:21 AM UTC
Mitigation actions are progressing, and service availability is improving. We are continuing remediation efforts to ensure full recovery.
-
monitoring Feb 16, 2026, 03:21 AM UTC
A fix has been implemented, and service has stabilized. We are actively monitoring system performance to ensure continued normal operation.
-
resolved Feb 16, 2026, 08:25 AM UTC
This incident has been resolved. Between 15 Feb 18:30 UTC and 16 Feb 02:25 UTC, customers in the AMER region experienced intermittent service degradation, with a small percentage of requests impacted. Service has fully recovered, and we continue to monitor platform health.
Read the full incident report →
- Detected by Pingoru
- Oct 21, 2025, 10:56 AM UTC
- Resolved
- Oct 21, 2025, 08:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 21, 2025, 10:56 AM UTC
We experienced a DSM SaaS service failover triggered by an upstream network event. The failover mechanism functioned as expected, and services were automatically restored. All systems are currently fully operational, and we are continuing to closely monitor the situation to ensure stability.
Read the full incident report →
Notice September 17, 2025 - Detected by Pingoru
- Sep 17, 2025, 10:05 PM UTC
- Resolved
- Sep 18, 2025, 02:20 AM UTC
- Duration
- 4h 15m
Affected: Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 2 updates
-
monitoring Sep 17, 2025, 10:05 PM UTC
On September 17, 2025, between 21:23 and 21:47 UTC, we experienced a network issue in our EU Frankfurt datacenter. During this time, traffic was automatically rerouted to the nearest datacenter. There should be no impact on operations. We have reached out to our service provider and will continue monitoring closely. If you experience any issues, please reach out to Fortanix Support.
-
resolved Sep 18, 2025, 02:20 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2025, 05:55 AM UTC
- Resolved
- Sep 08, 2025, 06:43 AM UTC
- Duration
- 47m
Affected: Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 2 updates
-
identified Sep 08, 2025, 05:55 AM UTC
During planned maintenance at our Singapore (SG) data center in the APAC region, we encountered an unexpected hardware failure. This has resulted in reduced redundancy for services in the APAC region. We have identified the root cause and are actively working on a resolution. We will provide further updates as progress is made.
-
resolved Sep 08, 2025, 06:43 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2025, 12:21 AM UTC
- Resolved
- Sep 08, 2025, 06:40 AM UTC
- Duration
- 6h 19m
Affected: Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 4 updates
-
investigating Sep 08, 2025, 12:21 AM UTC
We experienced the intermittent timeouts issue in AU region. We are actively investigating the cause. If you experience any problems, please contact Fortanix Support.
-
investigating Sep 08, 2025, 05:22 AM UTC
Our investigation has identified the root cause of the issue. We are now working on a resolution and will provide an update as soon as possible.
-
identified Sep 08, 2025, 05:24 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Sep 08, 2025, 06:40 AM UTC
We have implemented the fix and can confirm the issue is resolved. We will continue to monitor performance to ensure stability. For any new issues, please contact Fortanix Support.
Read the full incident report →
- Detected by Pingoru
- Aug 12, 2025, 09:33 AM UTC
- Resolved
- Aug 12, 2025, 11:33 AM UTC
- Duration
- 2h
Affected: Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 2 updates
-
identified Aug 12, 2025, 09:33 AM UTC
We are currently experiencing reduced redundancy in our connectivity to an upstream provider due to a hardware failure within their network. All traffic is being successfully rerouted through redundant paths, and no impact to customer services is expected at this time. The provider is actively working to resolve the issue and restore full network capacity. We are closely monitoring the situation and will provide updates as more information becomes available.
-
resolved Aug 12, 2025, 11:33 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2025, 12:32 PM UTC
- Resolved
- Aug 06, 2025, 07:02 PM UTC
- Duration
- 6h 29m
Timeline · 6 updates
-
investigating Aug 06, 2025, 12:32 PM UTC
We are currently investigating the issue affecting interDC connectivity between Paris and Amsterdam datacenter. There is no customer impact due to the issue. We will provide regular update as we make progress.
-
investigating Aug 06, 2025, 02:57 PM UTC
We've made progress and now suspect the issue is with a network component connecting our data centers. We'll provide an update once we confirm this.
-
investigating Aug 06, 2025, 03:54 PM UTC
We are continuing to investigate this issue.
-
monitoring Aug 06, 2025, 03:55 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Aug 06, 2025, 04:13 PM UTC
Issue with network components has been rectified and connectivity is restored between the 2 datacenters. We are currently monitoring the device for any further issue.
-
resolved Aug 06, 2025, 07:02 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2025, 03:25 PM UTC
- Resolved
- Jun 17, 2025, 06:36 PM UTC
- Duration
- 3h 11m
Affected: Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 4 updates
-
investigating Jun 17, 2025, 03:25 PM UTC
We are currently investigating this issue.
-
investigating Jun 17, 2025, 03:43 PM UTC
We are continuing to investigate this issue.
-
monitoring Jun 17, 2025, 03:43 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 17, 2025, 06:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 27, 2025, 09:22 AM UTC
- Resolved
- May 27, 2025, 08:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 27, 2025, 09:22 AM UTC
We experienced a timeout issue in the EU DSM SaaS service at Frankfurt region from 08:19:55 to 08:20:05 UTC on May 27, 2025. The service has fully recovered and is operating normally. We are actively investigating the cause and will continue monitoring for any further issues. If you experience any problems, please contact Fortanix Support.
Read the full incident report →
- Detected by Pingoru
- May 16, 2025, 06:40 PM UTC
- Resolved
- May 16, 2025, 11:24 PM UTC
- Duration
- 4h 44m
Affected: Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 2 updates
-
monitoring May 16, 2025, 06:40 PM UTC
We experienced the timeouts issue in the Frankfurt region from May 16 17:44 UTC to May 16th 17:46 UTC. The service has fully recovered and is operating normally. We are actively investigating the cause and will continue monitoring for any further issues. If you experience any problems, please contact Fortanix Support.
-
resolved May 16, 2025, 11:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 16, 2025, 12:41 AM UTC
- Resolved
- May 16, 2025, 12:53 PM UTC
- Duration
- 12h 11m
Affected: Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 2 updates
-
monitoring May 16, 2025, 12:41 AM UTC
We experienced the intermittent timeouts issue in Tokyo Data Center APAC region from May 15th, 2025 at 23:35 UTC to May 16th, 2025 at 00:17 UTC. The service has fully recovered and is operating normally. We are actively investigating the cause and will continue monitoring for any further issues. If you experience any problems, please contact Fortanix Support.
-
resolved May 16, 2025, 12:53 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2025, 02:37 PM UTC
- Resolved
- Apr 25, 2025, 11:43 AM UTC
- Duration
- 1d 21h
Affected: Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 4 updates
-
investigating Apr 23, 2025, 02:37 PM UTC
We experienced the outbound internet issue in Tokyo Data Center APAC region from 13:48 UTC on April 23, 2025. The key service operations are not impacted. We are actively investigating the cause and will continue monitoring for any further issues. If you experience any problems, please contact Fortanix Support.
-
monitoring Apr 23, 2025, 03:01 PM UTC
We are continuing to monitor for any further issues.
-
monitoring Apr 23, 2025, 03:05 PM UTC
An issue was identified with our service provider, and we executed a failover to resume normal operations.
-
resolved Apr 25, 2025, 11:43 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2025, 07:04 AM UTC
- Resolved
- Apr 16, 2025, 05:15 AM UTC
- Duration
- 22h 11m
Timeline · 4 updates
-
identified Apr 15, 2025, 07:04 AM UTC
The Key Attestation feature in DSM SaaS has been unavailable since April 9th. Our team is actively working on a fix, and we will share further updates as they become available. Please note that all other Cryptographic Operations and services are functioning normally. If you have any questions or concerns, feel free to contact our support team - [email protected]
-
identified Apr 15, 2025, 07:58 AM UTC
The Key Attestation feature has been fixed in the Americas DSM SaaS and has been functioning normally since April 11th. We are actively working on fixing it on other regions and will share further updates as they become available
-
monitoring Apr 16, 2025, 02:43 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 16, 2025, 05:15 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2025, 09:33 PM UTC
- Resolved
- Feb 28, 2025, 04:13 AM UTC
- Duration
- 6h 40m
Affected: Service availabilityService availabilityKey ManagementKey ManagementKey usage (Cryptographic operation)Key usage (Cryptographic operation)
Timeline · 6 updates
-
investigating Feb 27, 2025, 09:33 PM UTC
We're experiencing intermittent timeouts in the EU and UK region and have contacted our service provider. There should be minimal or no impact on operations. If you encounter any issues, please contact Fortanix Support.
-
investigating Feb 27, 2025, 09:38 PM UTC
We are continuing to investigate this issue.
-
monitoring Feb 27, 2025, 11:15 PM UTC
We are continuing to monitor for any further issues.
-
monitoring Feb 27, 2025, 11:22 PM UTC
We are continuing to monitor for any further issues.
-
monitoring Feb 27, 2025, 11:23 PM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 28, 2025, 04:13 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 25, 2024, 09:57 AM UTC
- Resolved
- Nov 28, 2024, 07:56 AM UTC
- Duration
- 2d 21h
Timeline · 5 updates
-
investigating Nov 25, 2024, 09:57 AM UTC
We are currently investigating this issue.
-
investigating Nov 25, 2024, 11:53 AM UTC
We are continuing to investigate this issue.
-
identified Nov 25, 2024, 11:54 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Nov 27, 2024, 06:10 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 28, 2024, 07:56 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 08, 2024, 03:55 PM UTC
- Resolved
- Oct 07, 2024, 08:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 08, 2024, 03:55 PM UTC
The Upstream Provider has scheduled maintenance for the Ashburn region on Tuesday, October 8th, 2024 at 02:00 UTC. We expect to complete the maintenance by Tuesday, October 8th, 2024 at 12:00 UTC.. During this period, traffic will be rerouted to the nearest data center. No interruptions in traffic are anticipated. If you encounter any issues, please reach out to Fortanix Support.
Read the full incident report →
- Detected by Pingoru
- Aug 27, 2024, 01:10 PM UTC
- Resolved
- Oct 18, 2024, 06:47 AM UTC
- Duration
- 51d 17h
Affected: Service availabilityService availabilityService availabilityKey ManagementKey ManagementKey ManagementKey usage (Cryptographic operation)Key usage (Cryptographic operation)Key usage (Cryptographic operation)
Timeline · 5 updates
-
investigating Aug 27, 2024, 01:10 PM UTC
We are currently investigating this issue.
-
investigating Aug 27, 2024, 01:38 PM UTC
We are actively investigating the issue. As a temporary workaround, reducing the MTU to 1400 has been found to resolve the issue in most cases.
-
identified Aug 27, 2024, 06:11 PM UTC
We have identified the issue and are currently implementing a fix. The rollout is expected to be completed within the next 30 minutes.
-
monitoring Aug 27, 2024, 07:32 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 18, 2024, 06:47 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2024, 09:49 PM UTC
- Resolved
- Jul 22, 2024, 09:49 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 22, 2024, 09:49 PM UTC
During a scheduled maintenance that was not expected to impact services, we encountered an issue that required us to restart the services.
Read the full incident report →
- Detected by Pingoru
- Jul 19, 2024, 04:34 AM UTC
- Resolved
- Jul 19, 2024, 08:47 AM UTC
- Duration
- 4h 13m
Affected: Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 5 updates
-
investigating Jul 19, 2024, 04:34 AM UTC
We are currently investigating this issue.
-
identified Jul 19, 2024, 04:44 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 19, 2024, 04:44 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jul 19, 2024, 05:16 AM UTC
We are continuing to monitor for any further issues.
-
resolved Jul 19, 2024, 08:47 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2024, 05:13 PM UTC
- Resolved
- Jul 16, 2024, 06:42 PM UTC
- Duration
- 1h 28m
Timeline · 2 updates
-
monitoring Jul 16, 2024, 05:13 PM UTC
We've detected a failover from the unplanned maintenance by upstream provider at the Sydney location from 14:41 PM UTC to 16:41 PM UTC. Our monitoring systems have not identified any connectivity issues, and we will continue to monitor the situation to ensure that the service has returned to normal
-
resolved Jul 16, 2024, 06:42 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2024, 02:38 PM UTC
- Resolved
- Jul 17, 2024, 03:49 PM UTC
- Duration
- 2d 1h
Affected: Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 6 updates
-
investigating Jul 15, 2024, 02:38 PM UTC
We are seeing in intermittent issue with one of the East Coast Data Center.
-
identified Jul 15, 2024, 03:40 PM UTC
A workaround has been implemented, however, customers may experience some latency when accessing AMER-DSM-SaaS.
-
identified Jul 16, 2024, 01:18 PM UTC
The issue was identified as a fault in a networking device on our provider's end. A workaround has been implemented, diverting traffic from the problematic provider POP. However, customers may experience some latency when accessing AMER-DSM-SaaS. Our service provider is still investigating the network service issue that caused this outage to ensure it is safe to route traffic back to this POP.
-
identified Jul 16, 2024, 05:32 PM UTC
We'll be performing maintenance to bring the traffic back to DC-11 POP.
-
monitoring Jul 17, 2024, 04:21 AM UTC
The maintenance is complete, and traffic is now being routed to all our data centers. We will continue to monitor the situation to ensure that the service has returned to normal.
-
resolved Jul 17, 2024, 03:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2024, 08:29 AM UTC
- Resolved
- Jul 09, 2024, 08:36 PM UTC
- Duration
- 12h 7m
Affected: Service availabilityKey ManagementKey usage (Cryptographic operation)
Timeline · 3 updates
-
investigating Jul 09, 2024, 08:29 AM UTC
We are currently investigating the issue.
-
monitoring Jul 09, 2024, 08:37 AM UTC
UK DSM SaaS is now operational and is under continuous monitoring.
-
resolved Jul 09, 2024, 08:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 27, 2024, 05:46 PM UTC
- Resolved
- Jun 27, 2024, 05:46 PM UTC
- Duration
- —
Affected: Service availability
Timeline · 1 update
-
resolved Jun 27, 2024, 05:46 PM UTC
This incident has been resolved.
Read the full incident report →