FTAPI Outage History

Started Oct 21, 2026, 09:28 AM UTC· resolved Oct 21, 2026, 12:23 PM UTC

1. investigating Oct 21, 2026, 09:28 AM UTC

   We’re currently experiencing degraded performance issues with for a subset of customers . Our team is currently working to restore normal performance levels. We apologize for any inconvenience.

2. monitoring Oct 21, 2026, 09:42 AM UTC

   The infrastructure issue at our cloud provider has been mitigated, and all affected FTAPI Cloud instances are now back online. Our team is closely monitoring the systems to ensure that all services are functioning correctly and remain stable. We will provide a final update once normal operations have been fully verified. We apologize for the disruption and thank you for your patience and understanding.

3. monitoring Oct 21, 2026, 09:53 AM UTC

   We remain in close contact with our cloud infrastructure provider as they work to resolve the underlying infrastructure issue. Some customers may continue to experience degraded performance or service interruptions. We are closely monitoring the situation and will provide further updates as soon as new information becomes available. We apologize for the continued inconvenience and appreciate your patience.

4. monitoring Oct 21, 2026, 10:47 AM UTC

   We continue to see short, recurring interruptions on part of our hosted SecuTransfer environments. The cause is an ongoing storage infrastructure issue at our cloud infrastructure provider. Each interruption lasts several minutes and ends with the affected instances recovering automatically. We remain in close contact with our provider, who is working to resolve the underlying infrastructure issue, and we are testing mitigations on our side to reduce the impact of further interruptions. We will post the next update as soon as the provider confirms a fix or within the next two hours, whichever comes first. We apologize for the inconvenience.

5. monitoring Oct 21, 2026, 11:20 AM UTC

   We have applied mitigations to reduce the impact of the recurring interruptions caused by the storage issue at our cloud infrastructure provider. All affected SecuTransfer environments are currently available and we are monitoring them closely. The provider is still working on the underlying issue, so short interruptions remain possible until it is resolved. Next update within one hour or as soon as the provider confirms a fix.

6. monitoring Oct 21, 2026, 11:31 AM UTC

   Our cloud infrastructure provider has confirmed that the underlying storage issue has been fixed. In addition, the mitigations we applied on our side have handled the remaining load spikes without impact. All SecuTransfer environments are operational and have been stable since. We"ll still monitor the situation further

7. resolved Oct 21, 2026, 12:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2026, 01:20 PM UTC· resolved Oct 20, 2026, 03:36 PM UTC

1. investigating Oct 20, 2026, 01:20 PM UTC

   We’re currently experiencing degraded performance issues with for a subset of customers . Our team is currently working to restore normal performance levels. We apologize for any inconvenience.

2. identified Oct 20, 2026, 01:27 PM UTC

   The issue has been identified and a fix is being implemented.

3. identified Oct 20, 2026, 02:11 PM UTC

   We identified the problem to be caused by the underlying infrastructure of the cloud provider.

4. identified Oct 20, 2026, 02:42 PM UTC

   We remain in close contact with our cloud infrastructure provider as they work to resolve the underlying infrastructure issue. Some customers may continue to experience degraded performance or service interruptions. We are closely monitoring the situation and will provide further updates as soon as new information becomes available. We apologize for the continued inconvenience and appreciate your patience.

5. monitoring Oct 20, 2026, 03:10 PM UTC

   The infrastructure issue at our cloud provider has been mitigated, and all affected FTAPI Cloud instances are now back online. Our team is closely monitoring the systems to ensure that all services are functioning correctly and remain stable. We will provide a final update once normal operations have been fully verified. We apologize for the disruption and thank you for your patience and understanding.

6. resolved Oct 20, 2026, 03:36 PM UTC

   The issue caused by the underlying infrastructure of our cloud provider has been resolved. All affected FTAPI Cloud instances are back online, and normal service availability has been restored. We apologize for any inconvenience caused and thank you for your patience and understanding.

Read the full incident report →

Started Aug 04, 2026, 12:50 PM UTC· resolved Aug 04, 2026, 03:34 PM UTC

1. investigating Aug 04, 2026, 12:50 PM UTC

   We’re currently experiencing degraded performance issues with for a subset of customers . Our team is currently working to restore normal performance levels. We apologize for any inconvenience.

2. identified Aug 04, 2026, 01:05 PM UTC

   We have identified the likely cause of the current disruption affecting our platform. Our engineering team is applying a fix now. We expect services to be fully available again within approximately the next 30 minutes. We will post another update once the fix is confirmed, or sooner if the situation changes. Thank you for your patience.

3. identified Aug 04, 2026, 01:28 PM UTC

   The fix is taking longer than we anticipated in our previous update. Our team is still actively working on restoring full service, and the issue remains our top priority. We will post our next update within the next 30 minutes regardless of whether the issue is resolved by then. We apologise for the continued disruption and appreciate your patience.

4. identified Aug 04, 2026, 02:01 PM UTC

   Our team is still working on resolving the issue. There is no significant change to report since our last update. We will post the next update within 30 minutes, or sooner if the situation changes. Thank you for your continued patience.

5. monitoring Aug 04, 2026, 02:54 PM UTC

   The root cause has been identified and we have implemented a fix. We are currently seeing services having fully recovered. We are monitoring the situation closely to maintain stability.

6. resolved Aug 04, 2026, 03:34 PM UTC

   This incident has been resolved.

7. postmortem Aug 13, 2026, 07:25 AM UTC

   **Executive Summary**: On August 4, 2026, customers hosted in one of our production environments experienced a full service outage of approximately two hours \(14:40–16:43 CEST\). The outage occurred during planned, downtime-free infrastructure maintenance on our database nodes and was caused by a failure of the external DNS resolvers used during node bootstrap without technical connection to the maintenance work itself. As a result, newly provisioned nodes were unable to join the cluster and the database became unavailable. As of August 4, 17:34 CEST, all services have been fully restored to operational state. ## **Incident Details** As part of a planned infrastructure improvement, a configuration change was applied to the database nodes in the affected production environment. The change was designed to be downtime-free and was carried out under standard change procedures. During the maintenance, and without technical connection to it, name resolution through the external DNS resolvers configured for node bootstrap stopped working. Because newly provisioned nodes depend on this name resolution to register with the cluster, they were unable to join. Existing database components could therefore not be rescheduled, which made the database — and consequently all customer-facing services in that environment — unavailable. The configuration change was rolled back promptly, but recovery was not immediate: as long as name resolution remained unavailable, new nodes still could not join the cluster. The subsequent root cause analysis, carried out together with our infrastructure provider, showed that the failure of the external DNS resolvers had caused the outage and not our maintenance work. Once name resolution was restored, nodes joined the cluster, the database recovered, and all services returned to normal operation within minutes. ## **Timeline \(CEST\)** * 04.08.2026, 13:28 – 13:55: Planned, downtime-free configuration change applied to the database nodes of the affected environment. * 04.08.2026, ~14:40: Name resolution via the external DNS resolvers used for node bootstrap begins to fail. Database components become unavailable; newly provisioned nodes can no longer join the cluster. * 04.08.2026, 14:42: Incident detected internally and incident response process initiated. * 04.08.2026, 14:50: Status page updated – _Investigating_. * 04.08.2026, ~15:00: Rollback of the configuration change initiated; escalation to our infrastructure provider opened. * 04.08.2026, 15:05: Status page updated – _Identified_. * 04.08.2026, 15:30 – 16:20: Joint analysis with the engineering teams of our infrastructure provider; DNS resolution identified as the blocking factor for node bootstrap. * 04.08.2026, 16:38: Name resolution restored. * 04.08.2026, 16:44: Database available again; all services recover. * 04.08.2026, 16:54: Status page updated – _Monitoring_. * 04.08.2026, 17:34: Stability confirmed. Status page updated – _Resolved_. ## **Strategic Prevention & Corrective Actions** To reinforce the resilience of our platform infrastructure and prevent recurrence, we have initiated the following measures: ### **Resilience of DNS configuration for node bootstrap** * We are removing the dependency on the DNS service that failed and are distributing the risk by including several providers in the configuration of our node groups. * This ensures that the failure of a single external resolver can no longer prevent new nodes from joining the cluster. ### **Monitoring & Alerting** * We are adding dedicated monitoring for name resolution and for the successful bootstrap of new nodes, so that failures in this layer are detected and attributed immediately rather than as a downstream symptom. ### **Escalation path with our infrastructure provider** * We are establishing a defined fast-track escalation path with our infrastructure provider for platform-level incidents, in order to reduce the time to substantive engineering engagement.

Read the full incident report →

Started Jul 28, 2026, 09:04 AM UTC· resolved Jul 28, 2026, 10:01 AM UTC

1. investigating Jul 28, 2026, 09:04 AM UTC

   Customers on Prod-1 cannot reach their instances. We are investigating the root-cause.

2. monitoring Jul 28, 2026, 09:14 AM UTC

   We identified the issue and implemented a fix. Customers are back online and we are monitoring the system.

3. resolved Jul 28, 2026, 10:01 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 09, 2026, 11:10 AM UTC· resolved Jul 09, 2026, 11:55 AM UTC

1. investigating Jul 09, 2026, 11:10 AM UTC

   We are aware of a partial outage that made services unavailable for some of our customers. We are currently investigating the issue.

2. monitoring Jul 09, 2026, 11:18 AM UTC

   We have identified an infrastructure outage that affected 2 out of 4 of our production environments as the root cause. Our services are currently operational again. We are monitoring the situation.

3. resolved Jul 09, 2026, 11:55 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 18, 2026, 06:29 AM UTC· resolved Jun 18, 2026, 10:24 AM UTC

1. investigating Jun 18, 2026, 06:29 AM UTC

   We are currently investigating reports about error messages when trying to send Deliveries with the classic Outlook Add-In

2. identified Jun 18, 2026, 06:39 AM UTC

   The issue is identified we will rollout fix in a few moments

3. identified Jun 18, 2026, 07:24 AM UTC

   We have found a solution for the issue and are currently rolling it out to our customers. This may cause downtime of up to 5 minutes for individual customers. We apologize for the service disruption.

4. identified Jun 18, 2026, 08:33 AM UTC

   We are still working on rolling out the fix to our customers and are expecting the issue to be resolved by 11:30 CEST.

5. identified Jun 18, 2026, 09:28 AM UTC

   We have rolled out the fix for >95% of affected customers. The remaining 5% will be fixed with the next 20 minutes.

6. monitoring Jun 18, 2026, 10:08 AM UTC

   The fix has been implemented for all customers and we are monitoring to verify.

7. resolved Jun 18, 2026, 10:24 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 29, 2026, 01:33 PM UTC· resolved May 29, 2026, 01:58 PM UTC

1. identified May 29, 2026, 01:33 PM UTC

   We have identified the root cause and are currently working on remediating the issue.

2. monitoring May 29, 2026, 01:44 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved May 29, 2026, 01:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 26, 2026, 03:29 PM UTC· resolved May 26, 2026, 04:06 PM UTC

1. investigating May 26, 2026, 03:29 PM UTC

   We’re experiencing service unavailabilities. Our team is currently working to restore the normal operations of the service. We apologize for any inconvenience.

2. identified May 26, 2026, 03:34 PM UTC

   The issue has been identified, a fix has been applied.

3. monitoring May 26, 2026, 03:36 PM UTC

   All systems are up and running again, we closely monitor now.

4. resolved May 26, 2026, 04:06 PM UTC

   We observed no further anomalies. Incident resolved.

Read the full incident report →

Started May 08, 2026, 09:22 AM UTC· resolved May 08, 2026, 11:54 AM UTC

1. investigating May 08, 2026, 09:22 AM UTC

   We are currently investigating an issue affecting our G.Data Virus Scanning (VaaS) service. A small number of customers may experience errors or failed scans at this time. Our engineering team is actively looking into the cause and working on a resolution. We will provide an update as soon as we have more information.

2. identified May 08, 2026, 09:58 AM UTC

   We have identified the specific trigger for the failed scans. Our team is currently deploying a potential fix and testing it against the problematic file sample. We are carefully evaluating whether this new version fully stabilizes the service and will keep you informed as soon as we know more.

3. monitoring May 08, 2026, 10:35 AM UTC

   We have applied the patch to address the resource constraints. Service performance has returned to normal, and virus scans are completing successfully for all customers. We will monitor the system actively over the next period to confirm the fix holds under normal load.

4. monitoring May 08, 2026, 11:54 AM UTC

   This incident has been resolved. The fix we deployed has stabilized the system, and we are no longer seeing any failed scans. Thank you for your patience while we addressed this issue.

5. resolved May 08, 2026, 11:54 AM UTC

   This incident has been resolved. The fix we deployed has stabilized the system, and we are no longer seeing any failed scans. Thank you for your patience while we addressed this issue.

Read the full incident report →

Started Apr 07, 2026, 10:20 AM UTC· resolved Apr 07, 2026, 03:15 PM UTC

1. investigating Apr 07, 2026, 10:20 AM UTC

   We are currently investigating an issue that affects our PDF Conversion capabilities.

2. identified Apr 07, 2026, 11:25 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Apr 07, 2026, 01:20 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Apr 07, 2026, 02:28 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Apr 07, 2026, 03:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 23, 2026, 08:46 AM UTC· resolved Feb 23, 2026, 04:11 PM UTC

1. identified Feb 23, 2026, 08:46 AM UTC

   The SecuFlows Advanced service is currently not available. We identified the issue and are working on restoring full functionality.

2. identified Feb 23, 2026, 08:47 AM UTC

   We are continuing to work on a fix for this issue.

3. identified Feb 23, 2026, 10:10 AM UTC

   We are continuing to get the service up and ready.

4. monitoring Feb 23, 2026, 12:58 PM UTC

   The incident is resolved and the services are running again. We are further monitoring the situation.

5. monitoring Feb 23, 2026, 04:10 PM UTC

   We observed no further anomalies. Incident resolved.

6. resolved Feb 23, 2026, 04:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 20, 2026, 06:58 AM UTC· resolved Feb 20, 2026, 10:13 AM UTC

1. investigating Feb 20, 2026, 06:58 AM UTC

   We are currently investigating authentication failures when logging in via SAML/Single Sign-On (SSO). Users may encounter error messages or be unable to complete the sign-in process. Our engineering team is actively looking into the root cause. We apologize for the disruption and will provide an update as soon as we have more information.

2. identified Feb 20, 2026, 07:29 AM UTC

   We have identified the root cause of the SAML failures and have a fix ready for deployment. To resolve the issue, we will be rolling out a configuration update across our clusters. During this process, individual customers may experience a brief 3-minute window of downtime.

3. identified Feb 20, 2026, 08:36 AM UTC

   We are now beginning the fix rollout for SAML authentication. The entire procedure is expected to take approximately 30 minutes to complete across all accounts. Individual customers may experience a brief 3-minute interruption. We will provide a final update once the rollout is finished.

4. monitoring Feb 20, 2026, 09:19 AM UTC

   The rollout of the fix for SAML authentication is now complete across all systems. We are currently monitoring the stability of login services to ensure all authentication flows are performing as expected. Users should now be able to log in successfully via SSO.

5. resolved Feb 20, 2026, 10:13 AM UTC

   We have completed our monitoring period and confirmed that all SAML authentication services are fully restored. All customers have been updated, and login success rates have returned to normal levels.

Read the full incident report →

Started Jan 08, 2026, 03:51 PM UTC· resolved Jan 08, 2026, 04:50 PM UTC

1. investigating Jan 08, 2026, 03:51 PM UTC

   We see problems with underlying system which lead to the major outage. We are working on fixing the issue.

2. identified Jan 08, 2026, 04:14 PM UTC

   Our infrastructure provider is dealing with a multi-region network outage at the moment. We expect the capabilities to return soon. While the availability is affected, we do not expect any impact on the integrity and confidentiality of our customer's data. We will share updates as soon as we retrieve new information about the course of recovery.

3. monitoring Jan 08, 2026, 04:37 PM UTC

   The Network connectivity has resumed and we are seeing service availability for the majority of our customers. We are closely monitoring our service availability to make sure all customers are able to access their data again.

4. resolved Jan 08, 2026, 04:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 04, 2025, 10:47 AM UTC· resolved Dec 04, 2025, 12:12 PM UTC

1. investigating Dec 04, 2025, 10:47 AM UTC

   Some of our customers may face with partial service degradation.

2. identified Dec 04, 2025, 10:53 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Dec 04, 2025, 11:07 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Dec 04, 2025, 12:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 17, 2025, 11:55 AM UTC· resolved Nov 17, 2025, 12:28 PM UTC

1. investigating Nov 17, 2025, 11:55 AM UTC

   We are currently seeing a full service outage and are investigating the root cause.

2. identified Nov 17, 2025, 12:04 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Nov 17, 2025, 12:11 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Nov 17, 2025, 12:28 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 29, 2025, 12:52 PM UTC· resolved Oct 29, 2025, 01:03 PM UTC

1. identified Oct 29, 2025, 12:52 PM UTC

   Currently our services are unavailable for about 0,1% of our customers. Our engineers are investigating the reason for this.

2. monitoring Oct 29, 2025, 12:57 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Oct 29, 2025, 01:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 23, 2025, 08:34 AM UTC· resolved Oct 23, 2025, 11:06 AM UTC

1. investigating Oct 23, 2025, 08:34 AM UTC

   We are identifying root cause of the issue.

2. identified Oct 23, 2025, 09:40 AM UTC

   Impact: Some services are currently affected due to technical issues in the underlying infrastructure. Users may experience slower response times or even not reaching their FTAPI instance due to temporary unavailability of certain features. Root Cause: The issue has been traced to an infrastructure-level problem. Next Steps: Our engineering and SRE teams have identified the cause and are currently deploying a fix to restore full functionality.

3. identified Oct 23, 2025, 10:22 AM UTC

   Impact: services remain affected due to the previously identified infrastructure issue. Update: We have evaluated multiple solution strategies and decided on the optimal recovery path. Our team is now performing the necessary steps to restore the system. Next Steps: We will continue to monitor the recovery process closely and verify system stability once all services are back online.

4. monitoring Oct 23, 2025, 10:31 AM UTC

   Impact: Customers are starting up again Update: Solution has been applied. System is still slow but working again. Next Steps: Monitor the System and stabilize infrastructure components

5. resolved Oct 23, 2025, 11:06 AM UTC

   The service comes back online.

Read the full incident report →

Started Oct 10, 2025, 09:55 AM UTC· resolved Oct 10, 2025, 09:55 AM UTC

1. resolved Oct 10, 2025, 09:55 AM UTC

   Due to an error in our process, a change was made to our central database system that should have been applied during a maintenance window. This led to severe performance degradation of most of our customer facing services and downtime for about 15% of our customers. The degradation lasted up to 15 minutes before we could resolve the issue. We sincerely apologize for any inconvenience caused to our customers.

Read the full incident report →

Started Sep 18, 2025, 06:34 AM UTC· resolved Sep 18, 2025, 08:18 AM UTC

1. identified Sep 18, 2025, 06:34 AM UTC

   Our virus scanning service has been slower than usual. The root cause has been identified, and our team is actively working on a resolution. Files continue to be scanned, but processing times may still be delayed until the fix is fully implemented. We will provide an update once performance has returned to normal.

2. monitoring Sep 18, 2025, 07:49 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Sep 18, 2025, 08:18 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 28, 2025, 08:01 AM UTC· resolved Aug 28, 2025, 10:00 AM UTC

1. investigating Aug 28, 2025, 08:01 AM UTC

   We are seeing that LDAP login currently is unavailable for some of our customers and are investigating the underlying cause.

2. identified Aug 28, 2025, 08:35 AM UTC

   The underlying cause has been identified and a fix has been validated. We will rollout the fix to affected customers, which will cause a downtime of up to 5 minutes. We expect the LDAP authentication to resume regular operations for all customers until noon today. We are sorry for the service degradation and disruption caused by this.

3. monitoring Aug 28, 2025, 09:45 AM UTC

   The underlying issue has been fixed and we are monitoring for any LDAP-related errors.

4. resolved Aug 28, 2025, 10:00 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 06, 2025, 03:53 PM UTC· resolved Aug 06, 2025, 04:15 PM UTC

1. identified Aug 06, 2025, 03:53 PM UTC

   We see some services becoming unresponsive for a limited amount of customers. The underlying issue has been identified and we are working towards full service recovery.

2. identified Aug 06, 2025, 04:00 PM UTC

   Less than 2% of customers are affected. Full service recovery is awaited within the next 15 minutes.

3. monitoring Aug 06, 2025, 04:10 PM UTC

   All services are operational. We are monitoring their performance closely.

4. resolved Aug 06, 2025, 04:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 30, 2025, 09:55 AM UTC· resolved Jul 30, 2025, 12:03 PM UTC

1. investigating Jul 30, 2025, 09:55 AM UTC

   We are seeing the application responding slowly for multiple customers and are investigating the issue.

2. monitoring Jul 30, 2025, 11:18 AM UTC

   The application responsiveness is back to regular levels. We are monitoring the situation closely.

3. resolved Jul 30, 2025, 12:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 01, 2025, 03:21 AM UTC· resolved Jun 01, 2025, 01:10 PM UTC

1. investigating Jun 01, 2025, 03:21 AM UTC

   We are currently investigating a full service outage.

2. monitoring Jun 01, 2025, 03:54 AM UTC

   All services are back in usable state. The root cause has been identified and we are monitoring the recovery process.

3. identified Jun 01, 2025, 04:28 AM UTC

   The services are currently offline again due to complications in the recovery process. We estimate recovery of service to take up to 30 minutes.

4. monitoring Jun 01, 2025, 04:53 AM UTC

   All services are back in usable state. The root cause has been identified and we are monitoring the recovery process.

5. resolved Jun 01, 2025, 01:10 PM UTC

   The recovery process was successful. This incident has been resolved.

Read the full incident report →

Started May 29, 2025, 04:16 AM UTC· resolved May 29, 2025, 04:21 AM UTC

1. investigating May 29, 2025, 04:16 AM UTC

   We are currently investigating the issue.

2. investigating May 29, 2025, 04:21 AM UTC

   The issue is resolved.

3. resolved May 29, 2025, 04:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 07, 2025, 02:49 PM UTC· resolved May 08, 2025, 08:10 PM UTC

1. investigating May 07, 2025, 02:49 PM UTC

   We are currently investigating the issue.

2. identified May 07, 2025, 03:25 PM UTC

   The service recovery process is started.

3. monitoring May 07, 2025, 03:33 PM UTC

   We have implemented a fix and all services are now available and fully functional. We are closely monitoring the situation to ensure continued stability. Thank you for your patience.

4. monitoring May 08, 2025, 08:10 PM UTC

   The issue has been resolved and systems have remained stable throughout the day. After continuous monitoring, we’re confident in closing the incident.

5. resolved May 08, 2025, 08:10 PM UTC

   The issue has been resolved and systems have remained stable throughout the day. After continuous monitoring, we’re confident in closing the incident.

Read the full incident report →