Outsystems incident

Incident affecting application deployments in all regions

Major Resolved View vendor source →

Outsystems experienced a major incident on December 8, 2025 affecting US East / Virginia and Canada / Central and 1 more component, lasting 2h 9m. The incident has been resolved; the full update timeline is below.

Started
Dec 08, 2025, 01:36 PM UTC
Resolved
Dec 08, 2025, 03:46 PM UTC
Duration
2h 9m
Detected by Pingoru
Dec 08, 2025, 01:36 PM UTC

Affected components

US East / VirginiaCanada / CentralSouth America / São PauloEurope / IrelandEurope / LondonEurope / FrankfurtIsrael / Tel AvivMiddle East / UAEAsia Pacific / MumbaiAsia Pacific / Singapore

Update timeline

  1. investigating Dec 08, 2025, 01:36 PM UTC

    We are aware that the issue affecting application deployments continues for deployments to stages other than Development. Customers may experience failed application deployments when deploying to these stages. Our team is currently investigating its cause. We will provide an update as soon as more details are available.

  2. resolved Dec 08, 2025, 03:46 PM UTC

    This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.

  3. postmortem Dec 11, 2025, 04:46 PM UTC

    On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages. The incident was caused by an issue related to connection limits on an internal message mechanism. A high volume of retries from a specific Data Services Execution Job, which lacked retry limits, escalated the problem into a connection exhaustion situation. To resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter. To prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.