Outsystems experienced a critical incident on August 31, 2026 affecting Asia Pacific / Sydney, lasting 2h 31m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 31, 2026, 03:28 PM UTC
We are aware of an issue affecting ODC in the Sydney Region. Developers using Mentor Studio will run into an error stating, "Mentor couldn't connect. Please go online and try again." Our team is actively investigating and will provide updates as more information becomes available.
- investigating Aug 31, 2026, 03:30 PM UTC
We are continuing to investigate this issue.
- investigating Aug 31, 2026, 03:34 PM UTC
We are continuing to investigate this issue.
- identified Aug 31, 2026, 05:02 PM UTC
We have identified the cause of the issue affecting Mentor in ODC Studio in the Asia Pacific (Sydney) region, and a fix is being applied. Users may continue to see the connection error while the fix is rolled out across all affected environments. We will provide updates as more information becomes available.
- resolved Aug 31, 2026, 06:00 PM UTC
The issue affecting Mentor in ODC Studio in the Asia Pacific (Sydney) region has been resolved. A configuration change caused Mentor connection requests to be directed incorrectly, which produced the connection error. That change has been reversed across all affected environments, and our team has confirmed that Mentor is working as expected again. We apologise for any disruption caused and thank you for your patience.
- postmortem Aug 31, 2026, 06:59 PM UTC
_Between August 28th and August 31st, 2026, users in the Asia Pacific \(Sydney\) region were unable to use Mentor in ODC Studio. Connection attempts returned an error stating, "Mentor couldn't connect. Please go online and try again." Deployed applications and other ODC Studio functionality were not affected._ _As part of planned regional infrastructure work, Mentor connection requests from affected environments began being sent to a new regional destination. The services needed to handle those requests had not yet been deployed there, so every connection attempt failed. The change was applied ahead of those services becoming available._ _The issue was detected through customer reports. Automated monitoring did not alert on it, because connection requests were being sent to a destination where the supporting service was not yet running, so no failure signals were generated for our monitoring to detect._ _To restore service, we reversed the configuration change on a single environment and confirmed that Mentor connected successfully, then applied the same reversal across all affected environments. We verified recovery with each of the customers who had reported the issue._ _To prevent recurrence, the regional infrastructure work will not resume until all dependent services are available in the region. We are strengthening the validation applied before configuration updates of this kind, so that a change cannot be made ahead of the services it depends on. We are also reviewing our monitoring so that failures of this type are detected automatically rather than through customer reports._ _We apologise for any disruption caused and thank you for your patience._