FTAPI incident

Partial service unavailability

Major Resolved View vendor source →

FTAPI experienced a major incident on August 4, 2026 affecting FTAPI Cloud Systems, lasting 2h 44m. The incident has been resolved; the full update timeline is below.

Started
Aug 04, 2026, 12:50 PM UTC
Resolved
Aug 04, 2026, 03:34 PM UTC
Duration
2h 44m
Detected by Pingoru
Aug 04, 2026, 12:50 PM UTC

Affected components

FTAPI Cloud Systems

Update timeline

  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.