Who is down right now

26 down now · 292 this week

OutSystems · Apps and SaaSJun 29, 2026, 04:28 UTC 4 months ago

Deployment Stage Incorrectly Ordered on ODC Platform

MajorConfig changeUpdated 4d ago
Jun 29, 04:28 UTCJun 29, 18:07 UTC
Duration
13h 38m
Impact
Major
Root cause
Config change
OutSystems, 90 days
16 incidents
Affected
US East / VirginiaEurope / FrankfurtAsia Pacific / TokyoAsia Pacific / SydneyODC - Platform and Portal - US East / VirginiaODC - Platform and Portal - Europe / FrankfurtODC - Platform and Portal - Asia Pacific / TokyoODC - Platform and Portal - Asia Pacific / Sydney
Status page

Final update

On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.

Timeline

  1. Postmortem · Jul 2, 08:15 UTC
    On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.
  2. Resolved · Jun 29, 18:07 UTC
    The incident has been resolved. The fix has been successfully applied across all affected regions, and we have verified that deployment pipelines are now operating with the correct stage ordering. We received direct confirmation from affected customers and have seen no further reports since the fix was implemented. We apologise for any disruption caused and thank you for your patience.
  3. Monitoring · Jun 29, 13:52 UTC
    We have applied a solution to resolve the configuration issue affecting deployment pipelines across multiple regions. We are now monitoring the platform closely to ensure that application promotions are functioning correctly and that all systems have fully recovered.
  4. Identified · Jun 29, 11:21 UTC
    We are continuing to work on a fix for this issue.
  5. Identified · Jun 29, 10:43 UTC
    We are continuing to work on implementing the fix for the configuration issue affecting deployment pipelines across multiple regions. While the mitigation actions are being executed, users may still experience issues promoting applications or see incorrect ordering in their deployment stages. We remain focused on resolving this as quickly as possible and will provide another update once the solution has been fully rolled out.
  6. Identified · Jun 29, 07:46 UTC
    The root cause has been found and linked to a misconfigured code that was deployed recently, which was then used to update the environment configuration orders. Mitigation actions will be implemented soon. We appreciate your patience while the fix is being fully rolled out.
  7. Investigating · Jun 29, 04:28 UTC
    We are currently investigating an issue where users are experiencing difficulties promoting applications through their deployment pipelines due to an incorrect ordering of deployment stages. This issue is affecting users across several regions. We are working to resolve the problem as quickly as possible and will provide updates as more information becomes available.

More from OutSystems

Full history

Also caused by configuration change

All