Outsystems experienced a major incident on April 1, 2025 affecting US East / Virginia and Europe / Frankfurt and 1 more component, lasting 5h 57m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 01, 2025, 04:27 AM UTC
We are aware of an issue causing 1CP to fail in specific scenarios in the following regions. US East (N. Virginia) Europe (Frankfurt) Asia Pacific (Tokyo) Asia Pacific (Mumbai) Asia Pacific (Singapore) Asia Pacific (Sydney) Customers in the Development Environment may experience deployment timeouts. This issue has been occurring since March 31, 2025, 23:00 UTC. Our team is currently investigating the cause. We will provide an update as soon as more details are available.
- investigating Apr 01, 2025, 07:33 AM UTC
We are continuing to investigate this issue.
- identified Apr 01, 2025, 08:40 AM UTC
We have identified the cause of the issue affecting 1CP. This issue has been found to affect all regions. Customers may still experience deployment timeouts. Our team is actively working on a solution. We will provide an update once more details are available.
- monitoring Apr 01, 2025, 08:50 AM UTC
A solution has been applied to resolve this issue. We will continue monitoring this situation to ensure full recovery.
- resolved Apr 01, 2025, 01:12 PM UTC
This incident has been fully resolved and 1CP is now operating as expected. Thank you for your patience.
- postmortem Apr 04, 2025, 01:22 PM UTC
On April 1st, 2025, a critical incident affected 1CP operations. Users encountered an error code, which was traced to a misconfiguration. The issue originated from a deployment on March 31st. To resolve the incident, the team promptly rolled back the affected deployment.