Snapshot 20101
Normalized text
Scripts and page chrome removed; this is what change detection compares.
{
"pages": [
{
"end_time": "2026-09-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "vdhg299b2y1r",
"impact": "major",
"message": "The fix has now been fully applied across all affected regions, and error rates have returned to normal levels. Users should once again be able to preview data in ODC Studio and access their applications as expected.\n\nWe are continuing to monitor the platform closely and are confirming full recovery with affected users. We will provide a further update once we have confirmed the incident is fully resolved.",
"name": "Incident affecting data preview in ODC Studio and runtime applications",
"timestamp": "Sep \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e10:49\u003c/var\u003e UTC"
},
{
"code": "nrn6x8f3lcqs",
"impact": "major",
"message": "We have applied the fix to a first set of affected accounts in the Asia Pacific (Singapore) region and confirmed that users on those accounts are able to log in to their Personal Environments again. The remaining affected accounts have not yet been updated, and users on those accounts will continue to see the \"Login with external provider failed\" error until the fix is applied.\n\nWe will provide a further update as more information becomes available.",
"name": "Incident affecting Personal Edition login in Asia Pacific (Singapore)",
"timestamp": "Sep \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e09:00\u003c/var\u003e UTC"
},
{
"code": "15fgt1vw0r45",
"impact": "critical",
"message": "This incident has been resolved. Our cloud provider has confirmed that the infrastructure disruption in the underlying cloud region is fully resolved, and we have verified that services in the Israel (Tel Aviv) region are operating normally, including sign-in to the ODC Portal and access to applications.\n\nWe apologise for any disruption caused and thank you for your patience.",
"name": "Authentication Issues Affecting ODC in the Israel (Tel Aviv) Region",
"timestamp": "Sep \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e15:50\u003c/var\u003e - \u003cvar data-var='time'\u003e19:22\u003c/var\u003e UTC"
},
{
"code": "q5hnbklbq414",
"impact": "major",
"message": "The issue affecting logins with the error \"wrong credentials and password resets with \"incorrect verification code\" on OutSystems Personal Edition and the Community website has been fully resolved. The fix has been confirmed effective for all affected accounts, and password resets are now completing successfully.\nWe apologise for any disruption this may have caused and thank you for your patience.",
"name": "Incident affecting password reset functionality",
"timestamp": "Sep \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e11:07\u003c/var\u003e - Sep \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e12:56\u003c/var\u003e UTC"
},
{
"code": "d28tgj15ygzt",
"impact": "major",
"message": "The migration to the new Community unified login system has been completed. Sign-in and account operations are now available again across the Community, the Support Portal, O11 Personal Environments and the ODC Personal Edition.\n\nAll services are operating as expected. We apologise for any disruption caused and thank you for your patience.",
"name": "Ongoing authentication maintenance",
"timestamp": "Sep \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e12:47\u003c/var\u003e - \u003cvar data-var='time'\u003e16:43\u003c/var\u003e UTC"
},
{
"code": "4srmswh35n9j",
"impact": "minor",
"message": "Our team has completed the fix and confirmed that the pagination of Logs in ODC Portal is now working as expected. We apologize for any disruption caused and thank you for your patience.",
"name": "Issue Affecting Log Pagination in ODC Portal Monitor",
"timestamp": "Sep \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e06:23\u003c/var\u003e - \u003cvar data-var='time'\u003e11:56\u003c/var\u003e UTC"
},
{
"code": "sj4jv07jryz5",
"impact": "major",
"message": "This incident has been resolved.",
"name": "MABS Android and iOS builds timming out",
"timestamp": "Sep \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e11:15\u003c/var\u003e - \u003cvar data-var='time'\u003e12:47\u003c/var\u003e UTC"
}
],
"name": "September",
"year": 2026
},
{
"incidents": [
{
"code": "wq54m4r9r8gt",
"impact": "critical",
"message": "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.\n\nWe apologise for any disruption caused and thank you for your patience.",
"name": "Connection issue in Mentor Studio",
"timestamp": "Aug \u003cvar data-var='date'\u003e31\u003c/var\u003e, \u003cvar data-var='time'\u003e15:28\u003c/var\u003e - \u003cvar data-var='time'\u003e18:00\u003c/var\u003e UTC"
},
{
"code": "9mbjvhq01gpf",
"impact": "minor",
"message": "This incident has been resolved. The issue was caused by a recent platform update that could prevent a timer's status from being recorded correctly after it ran, leaving it in a pending state. Our team has corrected this and confirmed that timers are executing as expected across the affected regions.\nWe apologise for any disruption caused and thank you for your patience.",
"name": "Issue with delayed timer execution in ODC",
"timestamp": "Aug \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e05:16\u003c/var\u003e - \u003cvar data-var='time'\u003e16:33\u003c/var\u003e UTC"
},
{
"code": "2kdld7xjgwcb",
"impact": "major",
"message": "This incident has been resolved. The issue affecting application deployments in ODC Portal has been mitigated, and deployments are operating normally.\n\nUsers attempting to deploy an application to another stage should no longer encounter the error OS-STGC-60005. Our monitoring shows no further occurrences of this error since 16:23 UTC.\n\nWe apologise for the disruption this caused to deployment activities.",
"name": "Issue affecting application deployments in ODC",
"timestamp": "Aug \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e14:57\u003c/var\u003e - \u003cvar data-var='time'\u003e19:12\u003c/var\u003e UTC"
},
{
"code": "74cpqbhr1l6y",
"impact": "minor",
"message": "This incident has been resolved. \nThe issue affecting Mentor in the ODC Portal was caused by an outdated permission check that remained in place after a recent change to how the service communicates internally. Our team has removed that check and confirmed that generating and editing applications using Mentor is working as expected across the affected regions.\nWe apologise for any inconvenience caused.",
"name": "Incident affecting Mentor in ODC Portal",
"timestamp": "Aug \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e10:54\u003c/var\u003e - \u003cvar data-var='time'\u003e16:20\u003c/var\u003e UTC"
},
{
"code": "t0qyyv71700d",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "Partial System outage",
"timestamp": "Aug \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e16:56\u003c/var\u003e - Aug \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e11:21\u003c/var\u003e UTC"
},
{
"code": "wrm735tmxtg9",
"impact": "minor",
"message": "This incident has been resolved. The issue affecting the ODC Portal in the Asia Pacific (Singapore), Europe (Frankfurt), and US East (N. Virginia) regions has been fully addressed, and all services are now operating as expected.",
"name": "Issue Affecting Application Configuration in ODC Portal",
"timestamp": "Aug \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e05:41\u003c/var\u003e - \u003cvar data-var='time'\u003e10:38\u003c/var\u003e UTC"
},
{
"code": "f6cfrcg8v72j",
"impact": "major",
"message": "The incident affecting sign-in and application access in the South America / São Paulo region has been resolved. All services are now fully operational.",
"name": "Incident affecting sign-in and application access on ODC",
"timestamp": "Aug \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e20:48\u003c/var\u003e - Aug \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e07:54\u003c/var\u003e UTC"
},
{
"code": "5386jslw1nhj",
"impact": "minor",
"message": "This issue has been resolved. Following ongoing monitoring, no new occurrences of the issue have been reported.\nApplications in the Development Stage in Europe Central (Frankfurt) have been scaling up successfully without errors since our fix was implemented.",
"name": "Incident affecting Applications in Development Stage in Europe Central",
"timestamp": "Jul \u003cvar data-var='date'\u003e31\u003c/var\u003e, \u003cvar data-var='time'\u003e08:31\u003c/var\u003e - Aug \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e08:34\u003c/var\u003e UTC"
}
],
"name": "August",
"year": 2026
},
{
"incidents": [
{
"code": "9mr2dqfzh6tv",
"impact": "none",
"message": "The 502 errors affecting the ODC Portal globally have been resolved. Between 15:19 and 15:59 UTC on July 30th, users experienced connectivity issues caused by a recent configuration change affecting header validation. The change has been reverted, and access to the ODC Portal has been fully restored. All services are now operating as expected. We apologise for any disruption caused and thank you for your patience.",
"name": "502 Error Affecting ODC Portal Access Globally",
"timestamp": "Jul \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e18:39\u003c/var\u003e - \u003cvar data-var='time'\u003e18:39\u003c/var\u003e UTC"
},
{
"code": "dgn5sb05y31r",
"impact": "major",
"message": "We have successfully resolved the issue affecting ODC Personal Editions across multiple regions. Environments that were unable to wake from hibernation are now fully operational. \nAll known affected customers have now been restored to service, and we confirm that services are operating as expected across all regions.\nWe apologize for any disruption caused and thank you for your patience.",
"name": "Recurrence of the incident affecting Personal Editions on ODC in several regions",
"timestamp": "Jul \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e02:13\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e09:06\u003c/var\u003e UTC"
},
{
"code": "33bp48m8bgb6",
"impact": "major",
"message": "This incident has been resolved. ODC Personal Editions are now\noperating normally.\nIf you have not yet done so, please access your\nPersonal Edition by clicking \"Wake Up\" in the ODC Portal.\nIf you experience any issues, our support team is available to assist.\nThank you for your patience.",
"name": "Incident affecting Personal Editions on ODC in several regions",
"timestamp": "Jul \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e11:46\u003c/var\u003e - \u003cvar data-var='time'\u003e17:37\u003c/var\u003e UTC"
},
{
"code": "bf55fqxxcl60",
"impact": "critical",
"message": "All customers impacted by this incident have been contacted and supported individually. While the Middle East region continues to be affected by the ongoing geopolitical situation and AWS continues to report the region as impacted, OutSystems has completed its direct response to every affected organization. \nThe affected services remain flagged as a major outage while these conditions persist. Customers who need further assistance can contact OutSystems Support by raising a new ticket or continuing their existing case through Support Services.",
"name": "Connectivity and Power Issues Detected in Middle East",
"timestamp": "Mar \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e16:33\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e14:41\u003c/var\u003e UTC"
}
],
"name": "July",
"year": 2026
}
],
"start_time": "2026-07-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-06-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "88zljdg67gjj",
"impact": "major",
"message": "The configuration issue affecting deployment pipeline stage ordering across multiple regions for ODC has been resolved. The fix has fully addressed both the primary issue identified on June 29th and a secondary edge case affecting users with custom environment names.\nOur team has completed the monitoring period, and all services are now operating as expected. We apologise for any disruption caused and thank you for your patience.",
"name": "Recurring issue Deployment Stage Incorrectly Ordered on ODC Platform",
"timestamp": "Jun \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e08:56\u003c/var\u003e - \u003cvar data-var='time'\u003e18:22\u003c/var\u003e UTC"
},
{
"code": "m91pp7s5pf33",
"impact": "major",
"message": "The incident has been resolved. The fix has been successfully applied across\nall affected regions, and we have verified that deployment pipelines are now\noperating with the correct stage ordering. We received direct confirmation\nfrom affected customers and have seen no further reports since the fix was\nimplemented. We apologise for any disruption caused and thank you for your\npatience.",
"name": "Deployment Stage Incorrectly Ordered on ODC Platform",
"timestamp": "Jun \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e04:28\u003c/var\u003e - \u003cvar data-var='time'\u003e18:07\u003c/var\u003e UTC"
},
{
"code": "9kbcqc8jdp1q",
"impact": "minor",
"message": "This incident has been fully resolved. Services are now operating as expected, and users can successfully deploy their apps without encountering the previous error.",
"name": "Incident affecting ODC app deployments",
"timestamp": "Jun \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e08:44\u003c/var\u003e - \u003cvar data-var='time'\u003e12:31\u003c/var\u003e UTC"
},
{
"code": "9h2d0j336780",
"impact": "minor",
"message": "We are pleased to confirm that the incident has been resolved, and all services are now operating as expected. ODC users in the US East (N. Virginia) region should no longer experience issues accessing applications in the DEV stage or encounter \"Upstream Request Timeout\" errors.",
"name": "Incident affecting ODC applications in the DEV stage",
"timestamp": "Jun \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e11:37\u003c/var\u003e - \u003cvar data-var='time'\u003e12:42\u003c/var\u003e UTC"
}
],
"name": "June",
"year": 2026
},
{
"incidents": [
{
"code": "mc3zc0tcwm2j",
"impact": "minor",
"message": "This incident has been fully resolved, and the Count parameter in advanced SQL queries is now operating as expected. To ensure you benefit from this fix, please make sure you republish the affected application and deploy it to the affected stage if necessary.\n\nThank you for your patience and understanding while we worked to resolve this matter.",
"name": "Incident: Error OS-BERT-60409 when using Count in Advanced Query across multiple regions",
"timestamp": "May \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e14:58\u003c/var\u003e - May \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e13:37\u003c/var\u003e UTC"
},
{
"code": "jmn9ty1qrc65",
"impact": "major",
"message": "This incident has been fully resolved, and Personal Environments in the N. Virginia region for O11 and ODC are now operating as expected. Thank you for your patience.",
"name": "Incident affecting Personal Environments for O11 and ODC",
"timestamp": "May \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e11:56\u003c/var\u003e - May \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e16:12\u003c/var\u003e UTC"
}
],
"name": "May",
"year": 2026
},
{
"incidents": [
{
"code": "x0h4d1vpw5n9",
"impact": "major",
"message": "This incident has been resolved.",
"name": "Partial System outage",
"timestamp": "Apr \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e02:36\u003c/var\u003e - \u003cvar data-var='time'\u003e10:19\u003c/var\u003e UTC"
},
{
"code": "7jnr80lq6fjy",
"impact": "critical",
"message": "The cause of this incident has been found. A new deployment of the Identity Services relied on a database schema that had not yet been updated, resulting in service unavailability and authentication failures, affecting all ODC regions.\nA solution has been applied by rolling back the deployment.\nThe incident is now resolved, and services are operating as expected. We have confirmed that user applications were not affected during this time.",
"name": "Login Access Issue with ODC Portal",
"timestamp": "Apr \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e02:24\u003c/var\u003e - \u003cvar data-var='time'\u003e03:30\u003c/var\u003e UTC"
}
],
"name": "April",
"year": 2026
}
],
"start_time": "2026-04-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-03-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "kw88rtpv80n1",
"impact": "critical",
"message": "The issues affecting our services have been resolved, and all systems are now operating normally. We apologize for any disruption this may have caused to your workflows.",
"name": "Partial System outage",
"timestamp": "Mar \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e01:06\u003c/var\u003e - Mar \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e11:22\u003c/var\u003e UTC"
},
{
"code": "84szdpkff8n3",
"impact": "major",
"message": "The incident is now resolved and login to ODC Portal and ODC Studio is operating as expected. \nThe issue, which prevented a subset of users from logging in, was caused by a change intended to strengthen the email verification process. We have resolved the situation by rolling back to a previous version of the services and will perform a root cause analysis to prevent a recurrence in future releases.",
"name": "Incident affecting ODC Portal and ODC Studio",
"timestamp": "Mar \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e09:35\u003c/var\u003e - \u003cvar data-var='time'\u003e11:32\u003c/var\u003e UTC"
},
{
"code": "277jd0w4kwhr",
"impact": "major",
"message": "This incident has been fully resolved and application access in ODC Portal is now operating as expected. Thank you for your patience.",
"name": "Incident affecting app access in ODC Portal",
"timestamp": "Mar \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e09:09\u003c/var\u003e - \u003cvar data-var='time'\u003e10:41\u003c/var\u003e UTC"
}
],
"name": "March",
"year": 2026
},
{
"incidents": [],
"name": "February",
"year": 2026
},
{
"incidents": [
{
"code": "cl40f332lxtx",
"impact": "major",
"message": "This incident has been fully resolved and the applications login is now operating as expected. Thank you for your patience.",
"name": "Incident affecting logins in Europe (Frankfurt), Europe (London), and Israel (Central)",
"timestamp": "Jan \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e20:00\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e12:43\u003c/var\u003e UTC"
},
{
"code": "tx930457yrt0",
"impact": "major",
"message": "The incident affecting the ODC Mentor has been resolved, and all services are now operating normally. On January 27th, ODC Mentor experienced a service disruption. This was caused by an outage with an external cloud provider. We mitigated the impact by implementing infrastructure changes to bypass the affected provider services.",
"name": "Incident affecting Mentor",
"timestamp": "Jan \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e12:53\u003c/var\u003e - \u003cvar data-var='time'\u003e18:20\u003c/var\u003e UTC"
},
{
"code": "d5cl1xqpqxfj",
"impact": "major",
"message": "This incident has been fully resolved and the 1-Click Publish feature is now operating as expected. Thank you for your patience.",
"name": "Incident affecting 1CP operations in Europe Central region (Frankfurt)",
"timestamp": "Jan \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e15:29\u003c/var\u003e - \u003cvar data-var='time'\u003e16:52\u003c/var\u003e UTC"
},
{
"code": "yc6nbbjlnxdn",
"impact": "major",
"message": "This incident is now fully resolved. If you continue to experience issues, please follow the steps shared in our previous communication. \nThank you for your patience and understanding.",
"name": "Incident affecting login via custom domains",
"timestamp": "Jan \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e10:13\u003c/var\u003e - \u003cvar data-var='time'\u003e14:35\u003c/var\u003e UTC"
}
],
"name": "January",
"year": 2026
}
],
"start_time": "2026-01-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2025-12-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "pzq8htm5krlm",
"impact": "major",
"message": "This incident has been fully resolved, and Application Publishing is now operating as expected. Thank you for your patience.",
"name": "Incident affecting application deployments in all regions",
"timestamp": "Dec \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e13:36\u003c/var\u003e - \u003cvar data-var='time'\u003e15:46\u003c/var\u003e UTC"
},
{
"code": "f15k70ys33vr",
"impact": "major",
"message": "This incident has been fully resolved and application deployments are now operating as expected. Our team will continue to investigate the root cause. Thank you for your patience.",
"name": "Incident affecting 1-Click Publish functionality",
"timestamp": "Dec \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e10:15\u003c/var\u003e - \u003cvar data-var='time'\u003e11:12\u003c/var\u003e UTC"
}
],
"name": "December",
"year": 2025
},
{
"incidents": [
{
"code": "71pqvp3w05xt",
"impact": "major",
"message": "We have successfully applied a manual fix for the Personal Edition users who reported the “no permissions” error; access for these accounts has been restored.\n\nRegarding other affected users who did not submit a report, we have sent a dedicated communication to your registered email address with further details. We will continue to monitor the system to ensure stability.",
"name": "Incident affecting Personal Edition Users – Post-Login Permissions Issue",
"timestamp": "Nov \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e10:07\u003c/var\u003e - \u003cvar data-var='time'\u003e21:01\u003c/var\u003e UTC"
},
{
"code": "nnbkyfhmws2m",
"impact": "major",
"message": "We experienced an issue that prevented some users from logging in to their Personal Editions across multiple regions. This affected tenants created between November 17 and 18 and assigned on November 22.\n\nThe problem was caused by an incomplete internal configuration during setup, which blocked the login process. Our team has corrected the configuration for all affected tenants, and access has now been fully restored.\n\nThank you for your patience while we resolved this issue.",
"name": "Incident Affecting ODC Personal Edition User Logins",
"timestamp": "Nov \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e12:37\u003c/var\u003e - \u003cvar data-var='time'\u003e17:06\u003c/var\u003e UTC"
},
{
"code": "6v80x83962w5",
"impact": "major",
"message": "This incident has been fully resolved, and the Publish/Promote of External Libraries is now fully operating as expected. \nThank you for your patience.",
"name": "Incident affecting timeouts when deploying an app with external libraries packaged",
"timestamp": "Nov \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e11:46\u003c/var\u003e - \u003cvar data-var='time'\u003e12:09\u003c/var\u003e UTC"
},
{
"code": "4tq2gsdw9ynl",
"impact": "critical",
"message": "This incident has been fully resolved and the login on Personal Edition is now operating as expected. \nThank you for your patience.",
"name": "Incident affecting Personal Edition login",
"timestamp": "Nov \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e09:56\u003c/var\u003e - \u003cvar data-var='time'\u003e11:28\u003c/var\u003e UTC"
},
{
"code": "m1h99thjhsdm",
"impact": "minor",
"message": "We have successfully deployed a fix for the LogMessage issue that affected timers in the Europe (Frankfurt) and Asia Pacific (Tokyo) regions. Our monitoring confirms that the issue is fully resolved and all services are operating normally. Thank you for your patience.",
"name": "Incident affecting timers LogMessage in ODC Portal",
"timestamp": "Nov \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e14:26\u003c/var\u003e - Nov \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e17:45\u003c/var\u003e UTC"
},
{
"code": "1lh68m1ygyf0",
"impact": "major",
"message": "The issue affecting multiple ODC functionalities in Europe (Frankfurt) region has been resolved and services are now operating as expected. Thank you for your patience.",
"name": "Incident affecting Deployments to Production, Application Runtime and End-User Authentication",
"timestamp": "Nov \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e09:36\u003c/var\u003e - \u003cvar data-var='time'\u003e10:50\u003c/var\u003e UTC"
},
{
"code": "qc7xx0333v18",
"impact": "major",
"message": "The issue affecting user authentication on the ODC platform, causing some users to encounter HTTP 401 errors, has been resolved. The service is now fully operational. Thank you for your patience.",
"name": "Incident affecting user authentication on ODC Portal",
"timestamp": "Nov \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e13:16\u003c/var\u003e - \u003cvar data-var='time'\u003e15:16\u003c/var\u003e UTC"
},
{
"code": "b5twjq1sx4s0",
"impact": "minor",
"message": "This incident has been fully resolved.\nOur teams identified an issue that was affecting timer logs. A fix was developed, tested, and successfully applied to all environments. Monitoring confirms that the issue is now fully resolved.\nThank you for your patience and understanding.",
"name": "Incident affecting timer logs",
"timestamp": "Nov \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e09:41\u003c/var\u003e - Nov \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e12:38\u003c/var\u003e UTC"
}
],
"name": "November",
"year": 2025
},
{
"incidents": [
{
"code": "yzckctqcvcs2",
"impact": "minor",
"message": "We have confirmed that all services in the eu-central-1(Frankfurt) region are now fully operational. Our team applied a fix by restarting an underlying service, which has restored normal performance. We will continue to investigate the root cause to prevent a recurrence.",
"name": "ODC - 1CP fails due to build timeout (OS-DPL-BLD-40801)",
"timestamp": "Oct \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e20:46\u003c/var\u003e - \u003cvar data-var='time'\u003e21:24\u003c/var\u003e UTC"
},
{
"code": "4hq2tzzpm620",
"impact": "major",
"message": "This incident has been fully resolved.\n\nOutSystems Support identified that today, between 08:15 UTC and 11:30 UTC, some customers experienced service disruptions. The issue began around 08:15 UTC and recovery was observed by 11:30 UTC. Any remaining errors after that time were related to earlier requests made during the affected period.\n\nOur team determined that a system update deployed at 08:19 UTC was the likely cause of the disruption. The update was reverted at 11:41 UTC, after which services stabilised and have since been operating as expected.\n\nThank you for your patience and understanding.",
"name": "Incident affecting 1-Click-Publish operations",
"timestamp": "Oct \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e11:49\u003c/var\u003e - \u003cvar data-var='time'\u003e14:23\u003c/var\u003e UTC"
},
{
"code": "qt540cjhk8w2",
"impact": "major",
"message": "The fix has been deployed in all regions. Our team reverted the service version that was causing authentication errors, and the process was successfully completed across all regions.\nAll services have been fully restored, and this incident is now resolved.",
"name": "External authentication issues (502 error) when logging into ODC with External IdPs in all regions",
"timestamp": "Oct \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e14:57\u003c/var\u003e - \u003cvar data-var='time'\u003e16:21\u003c/var\u003e UTC"
},
{
"code": "j44j3fx9cspr",
"impact": "minor",
"message": "We are pleased to inform you that the issue has been resolved and the reported concerns from our customers earlier today have been successfully addressed.",
"name": "Incident affecting Platform in ODC and O11 in US Virginia",
"timestamp": "Oct \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e09:43\u003c/var\u003e - \u003cvar data-var='time'\u003e13:06\u003c/var\u003e UTC"
},
{
"code": "rpq42j443tpg",
"impact": "major",
"message": "We have identified the issue as a client-side issue, and the suggested workaround has been shared with the affected customers for implementation. We have now confirmed that the workaround has fully resolved the issue, and our service is now operating as expected.",
"name": "Cannot log in through ODC Studio",
"timestamp": "Oct \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e17:25\u003c/var\u003e - \u003cvar data-var='time'\u003e23:26\u003c/var\u003e UTC"
},
{
"code": "z5xfwqpg8y00",
"impact": "major",
"message": "This incident has been fully resolved and the timer execution on ODC Portal is now operating as expected. Thank you for your patience.",
"name": "Incident affecting Timers on Asia Pacific (Tokyo)",
"timestamp": "Oct \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e10:51\u003c/var\u003e - \u003cvar data-var='time'\u003e12:12\u003c/var\u003e UTC"
}
],
"name": "October",
"year": 2025
}
],
"start_time": "2025-10-01T00:00:00Z",
"time_zone": "UTC"
}
]
}