{
"vendor": "Outsystems",
"slug": "outsystems",
"platform": "statuspage",
"status_url": "https://status.outsystems.com",
"last_checked": "2026-09-16T12:28:20Z",
"last_state": "partial",
"history_backfilled": true,
"first_watched": "2026-09-04T07:06:16Z",
"incidents": [
{
"body": "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.",
"first_seen": "2026-09-14T12:29:13Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-09-15T12:56:47.738Z",
"resolved_inferred": false,
"started_at": "2026-09-14T11:07:42.121Z",
"state": "resolved",
"title": "Incident affecting password reset functionality",
"updated_at": "2026-09-15T12:56:47.753Z",
"url": "https://stspg.io/h51gqpqqc9zh"
},
{
"body": "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.",
"first_seen": "2026-09-12T12:30:15Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-09-11T16:43:32.719Z",
"resolved_inferred": false,
"started_at": "2026-09-11T12:47:15.000Z",
"state": "resolved",
"title": "Ongoing authentication maintenance",
"updated_at": "2026-09-11T16:43:32.744Z",
"url": "https://stspg.io/hmg0b09knzc6"
},
{
"body": "Between September 10th and September 11th, 2026, customers experienced an issue affecting the Logs page in ODC Portal, where browsing beyond the first page would still show logs from the first page of results. This issue affected every region and Stage. No log data was lost, the issue only affected the ability to browse beyond the first page of results.  \nThis issue was detected through customer reports, and our team reproduced the behaviour internally to confirm its scope. The root cause was identified as a defect introduced by a recent update to the Logs pagination logic, which caused the same set of results to be returned regardless of which page was requested. A fix was developed, tested, and rolled out across all affected regions, with full recovery confirmed on September 11th, 2026, at 11:56 UTC.  \nFollowing this incident, we are working to reduce the time it takes for validated fixes to reach production for confirmed customer-impacting issues, and strengthening our testing and internal review processes to catch this type of defect before it reaches production. We apologise for any disruption caused and thank you for your patience.",
"first_seen": "2026-09-11T12:29:42Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-09-11T11:56:51.863Z",
"resolved_inferred": false,
"started_at": "2026-09-11T06:23:17.198Z",
"state": "postmortem",
"title": "Issue Affecting Log Pagination in ODC Portal Monitor",
"updated_at": "2026-09-14T17:01:33.050Z",
"url": "https://stspg.io/7ssr1zclzrs8"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T11:14:03Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-09-04T12:47:37.977Z",
"resolved_inferred": false,
"started_at": "2026-09-04T11:15:06.692Z",
"state": "resolved",
"title": "MABS Android and iOS builds timming out",
"updated_at": "2026-09-04T12:47:37.991Z",
"url": "https://stspg.io/c5xghzgxc8ly"
},
{
"body": "_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._  \n_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._  \n_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._  \n_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._  \n_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._  \n_We apologise for any disruption caused and thank you for your patience._",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-31T18:00:40.904Z",
"resolved_inferred": false,
"started_at": "2026-08-31T15:28:49.850Z",
"state": "postmortem",
"title": "Connection issue in Mentor Studio",
"updated_at": "2026-08-31T19:05:27.794Z",
"url": "https://stspg.io/5rx4z4hz5p9y"
},
{
"body": "On August 26th, between 05:16 UTC and 16:26 UTC, some ODC users experienced delays in the execution of timers. Affected timers remained pending instead of running as scheduled, and subsequent runs did not start. Users in US East / Virginia and Asia Pacific / Singapore were affected. Applications themselves remained available throughout.\n\nThe issue was caused by a recent platform update that changed how a timer's status is recorded once it has run. Under that update, a timer whose status needed to be recorded more than once in sequence failed to update correctly, leaving it pending and blocking later scheduled executions. To restore service, our team returned the affected part of the platform to its previous version, which stopped the issue recurring for affected users. A permanent correction was then developed, validated and deployed across the platform, and we confirmed that timers were executing normally before closing the incident.\n\nWe are reviewing our monitoring of timer execution so that issues of this kind are detected automatically rather than through customer reports. We apologise for any disruption caused and thank you for your patience.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-26T16:33:04.484Z",
"resolved_inferred": false,
"started_at": "2026-08-26T05:16:49.409Z",
"state": "postmortem",
"title": "Issue with delayed timer execution in ODC",
"updated_at": "2026-08-27T04:57:22.123Z",
"url": "https://stspg.io/tkcdgqxgq4nz"
},
{
"body": "On August 24th, 2026, some users experienced an issue affecting application deployments in ODC Portal. Affected users intermittently saw the error message: \"An error occurred while getting the generated code from revision. \\(OS-STGC-60005\\)\".\n\nThe issue was caused by an internal scaling tool that interfered with a backend service used to prepare deployment packages, causing delays and errors for some deployment requests. We fixed the scaling configuration to restore normal behavior.\n\nTo prevent a recurrence, we are working with the provider of the automated scaling tool to correct the underlying behavior, and have put a permanent safeguard in place to stop the affected service from being mismanaged by that tool going forward.\n\nWe apologize for any disruption caused and thank you for your patience.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-24T19:12:27.000Z",
"resolved_inferred": false,
"started_at": "2026-08-24T14:57:08.453Z",
"state": "postmortem",
"title": "Issue affecting application deployments in ODC",
"updated_at": "2026-08-25T11:40:46.529Z",
"url": "https://stspg.io/khdrc2zlc3s4"
},
{
"body": "Between 20 August 9:52 UTC and 21 August 13:22 UTC, some users were unable to generate or edit applications using Mentor in the ODC Portal, and received the error OS-IDE-CONVERSATIONAL-50035.    \nThe issue was caused by an outdated permission check that remained in place after a recent change to how the service communicates internally.    \nWe removed the outdated check and confirmed that the Mentor App Generator App Editor recovered across the affected regions.    \nWe apologise for the disruption this caused.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-21T16:20:15.691Z",
"resolved_inferred": false,
"started_at": "2026-08-21T10:54:59.659Z",
"state": "postmortem",
"title": "Incident affecting Mentor in ODC Portal",
"updated_at": "2026-08-21T16:41:05.307Z",
"url": "https://stspg.io/ntdjqnjrrlhr"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-13T11:21:50.855Z",
"resolved_inferred": false,
"started_at": "2026-08-12T16:56:12.323Z",
"state": "resolved",
"title": "Partial System outage",
"updated_at": "2026-08-13T11:21:50.875Z",
"url": "https://stspg.io/45rnhzv390cg"
},
{
"body": "On August 12th, 2026, at approximately 02:56 UTC, we received our first customer report regarding an issue that affected the Application Configuration and IP Filter List features, resulting in these areas failing to load for a number of customers. Application publishing and runtime were not affected. Customers saw the error codes OS-APPC-60043 and OS-CFGC-GEN-60030. This prevented some users from completing required application configuration changes. Normal service was restored at 08:00 UTC.\n\nIt was caused by a recent update to an internal service that provides configuration data. The update unintentionally changed how requests were routed between instances of that service, so most requests for IP filter information reached an instance that could not answer them and timed out. Our team identified the faulty update and rolled it back across all environments to restore normal behavior.\n\nWe are improving our pre-release testing and monitoring so that this type of issue is caught before it reaches production, and adding monitoring coverage specifically for this failure mode.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-12T10:38:54.028Z",
"resolved_inferred": false,
"started_at": "2026-08-12T05:41:29.472Z",
"state": "postmortem",
"title": "Issue Affecting Application Configuration in ODC Portal",
"updated_at": "2026-08-13T11:16:21.184Z",
"url": "https://stspg.io/wcwk8z12j21y"
},
{
"body": "On August 10th, 2026, from 20:31 to 22:19 UTC, users in the South America / S\u00e3o Paulo region experienced errors when signing in to ODC. This prevented affected users from accessing their Production applications and also affected the ODC Portal and ODC Studio.\n\nThe issue was detected through customer reports and monitoring. Our investigation found that a fault in an internal caching component of our identity service was preventing it from issuing sign-in tokens, even though the service otherwise appeared to be running normally.\n\nTo restore service, our team restarted the affected identity service, which cleared the fault and allowed token issuance to resume. We confirmed with affected customers that sign-in and application access had returned to normal before closing the incident.\n\nWe have identified additional monitoring and preventive improvements for this component and are prioritising their rollout to help reduce the risk of similar issues recurring. We apologise for any disruption caused and thank you for your patience.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-11T07:54:40.255Z",
"resolved_inferred": false,
"started_at": "2026-08-10T20:48:01.967Z",
"state": "postmortem",
"title": "Incident affecting sign-in and application access on ODC",
"updated_at": "2026-08-12T06:47:19.489Z",
"url": "https://stspg.io/kb0jdx8tj3yb"
},
{
"body": "On July 31st, 2026, an issue affected applications running in the Development Stage in Europe Central \\(Frankfurt\\). Applications experienced extended delays \\(2\u20133 minutes\\) and timeout errors when starting up from an idle state.\n\nThe issue lasted approximately a few hours and was detected through customer reports and platform monitoring. During this time, several customers in the region reported difficulties launching their applications in the Development Stage's Runtime.\n\nOur investigation identified a memory issue in a critical component responsible for automatically scaling applications based on incoming traffic. This component was consuming excessive memory and restarting repeatedly, which prevented applications from scaling up when first accessed. Our team immediately implemented an operational workaround by increasing resource limits for this component. This mitigation immediately allowed applications to scale up as expected.\n\nIn parallel, we developed a permanent code fix to address the root cause and deployed it on August 7th. The system remained stable, with no new occurrences during and after the deployment of the permanent fix.\n\nTo prevent similar issues, OutSystems is improving how we monitor and validate infrastructure configuration to catch memory and resource issues earlier, and we are enhancing our automated scaling components to handle traffic pattern changes more gracefully.\n\nWe apologise for any disruption caused and thank you for your patience.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-07T08:34:33.760Z",
"resolved_inferred": false,
"started_at": "2026-07-31T08:31:58.000Z",
"state": "postmortem",
"title": "Incident affecting Applications in Development Stage in Europe Central",
"updated_at": "2026-08-07T15:42:01.599Z",
"url": "https://stspg.io/qyc01hd3t73m"
},
{
"body": "On July 30, 2026, between 15:19 and 15:59 UTC, customers in multiple regions experienced an outage affecting access to the OutSystems ODC Portal, preventing them from logging in or accessing their development environments. The incident was caused by the addition of a custom header, which prevented requests from reaching the portal. Following the code change rollback, service was restored by 15:59 UTC. To prevent similar incidents in the future, we are implementing additional automated testing to validate configuration changes before they are deployed to production and conducting a comprehensive review of our code review and testing procedures to catch such issues earlier in the development process. We appreciate your patience during this incident and apologize for any disruption to your work.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-30T18:39:10.991Z",
"resolved_inferred": false,
"started_at": "2026-07-30T18:39:10.882Z",
"state": "postmortem",
"title": "502 Error Affecting ODC Portal Access Globally",
"updated_at": "2026-08-04T15:32:44.158Z",
"url": "https://stspg.io/p13qwvwtmc3n"
},
{
"body": "On the 20th of July 2026, there was an issue with the wake-up functionality affecting Personal Editions. This occurred in all three regions \\(US East, Europe and Asia Pacific\\).  \nUsers were unable to wake up their environments from hibernation. When attempting to wake up the environments, they either remained in hibernation or moved to a \"waking up\" state indefinitely, preventing access to applications.  \nThis was caused by an issue in how our backend systems processed environment status updates. Due to messages being processed out of order, some environments' internal state was incorrectly reverted to 'hibernated' after they had already woken up successfully, even though the environment itself remained accessible on the backend. This caused the ODC Portal to keep showing an inaccurate 'hibernated' or 'waking up' status, and repeated wake-up attempts did not resolve it since the underlying state kept getting overwritten.  \nWe identified the root cause on the 21st of July and deployed a code fix to correct the state synchronization. The fix started to be rolled out to all regions on 22nd of July and completed by the 23rd of July. All affected environments were woken up successfully.  \nWe are implementing additional state verification checks to ensure the ODC Portal and backend systems remain in sync. A full technical review is underway to identify similar synchronization gaps across other features.  \nWe apologize for any disruption caused and thank you for your patience.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-23T09:06:28.653Z",
"resolved_inferred": false,
"started_at": "2026-07-21T02:13:51.671Z",
"state": "postmortem",
"title": "Recurrence of the incident affecting Personal Editions on ODC in several regions",
"updated_at": "2026-07-23T13:06:14.696Z",
"url": "https://stspg.io/hk3hjs3s5ssm"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-20T17:37:51.191Z",
"resolved_inferred": false,
"started_at": "2026-07-20T11:46:15.940Z",
"state": "resolved",
"title": "Incident affecting Personal Editions on ODC in several regions",
"updated_at": "2026-07-20T17:37:51.208Z",
"url": "https://stspg.io/1zs69723rtxm"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-30T18:22:41.851Z",
"resolved_inferred": false,
"started_at": "2026-06-30T08:56:27.789Z",
"state": "postmortem",
"title": "Recurring issue Deployment Stage Incorrectly Ordered on ODC Platform",
"updated_at": "2026-07-02T08:14:02.867Z",
"url": "https://stspg.io/thsy1h69sgw2"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-29T18:07:13.000Z",
"resolved_inferred": false,
"started_at": "2026-06-29T04:28:44.715Z",
"state": "postmortem",
"title": "Deployment Stage Incorrectly Ordered on ODC Platform",
"updated_at": "2026-07-02T08:15:05.290Z",
"url": "https://stspg.io/wh6y61qnc6zf"
},
{
"body": "On June 24th, an issue occurred that impacted ODC application deployments for non-administrator users across multiple regions, including Asia Pacific and Europe. Affected users experienced failures when attempting to deploy applications to higher stages and received an error during the build preparation step. Administrator accounts were not affected.\n\nThe issue was caused by a configuration change deployed on June 23rd, which introduced a technical mismatch in how permission roles were validated within the build pipeline, preventing non-admin users from initiating deployments. The engineering team identified the root cause and reversed the change.\n\nDeployments are now functioning normally for all affected users. We are conducting a post-incident review to prevent similar issues from occurring in the future.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-25T12:31:39.814Z",
"resolved_inferred": false,
"started_at": "2026-06-25T08:44:37.103Z",
"state": "postmortem",
"title": "Incident affecting ODC app deployments",
"updated_at": "2026-06-25T13:16:06.773Z",
"url": "https://stspg.io/ks3lkjzz0wym"
},
{
"body": "On June 22nd, an incident affected ODC users in the US East \\(N. Virginia\\) region. Users were unable to access any applications in the Development stage, receiving an \"Upstream Request Timeout\" error. Production and Test stages, as well as all other regions, were unaffected.\n\nThe incident was caused by a platform configuration change that prevented the component responsible for starting idle Development-stage applications on demand from functioning. As a result, when a request arrived, the application failed to start, causing the connection to time out at the gateway.\n\nThe issue was resolved by reverting the configuration change. The component fully recovered, app startup resumed, and normal service operation was verified.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-22T12:42:49.313Z",
"resolved_inferred": false,
"started_at": "2026-06-22T11:37:51.203Z",
"state": "postmortem",
"title": "Incident affecting ODC applications in the DEV stage",
"updated_at": "2026-06-22T14:50:39.229Z",
"url": "https://stspg.io/y3cytpywx6dm"
},
{
"body": "On May 22, 2026, we deployed an update intended to improve internal diagnostics. This update added automatic comments to generated SQL statements. In a specific edge case, where count-based queries were used inside nested SQL statements, these added comments disrupted the structure of the query and caused it to fail. Affected applications returned runtime errors and certain database queries could not complete successfully.  \nAfter deploying a fix for this, services were restored and all affected queries are now functioning normally.  \nWe appreciate your patience while this was being resolved and remain committed to continuously improving the stability and reliability of the platform.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-25T13:37:01.699Z",
"resolved_inferred": false,
"started_at": "2026-05-22T14:58:38.280Z",
"state": "postmortem",
"title": "Incident: Error OS-BERT-60409 when using Count in Advanced Query across multiple regions",
"updated_at": "2026-05-26T16:18:41.784Z",
"url": "https://stspg.io/2pvnc4dsgk7q"
},
{
"body": "On May 8, 2026, at 12:03 AM UTC, ODC and O11 Personal Environments in the N. Virginia region experienced a service disruption caused by an AWS infrastructure event affecting a single Availability Zone. The disruption was related to an external power and cooling issue that impacted the availability of underlying AWS services.  \nCustomers experienced service unavailability, including issues with logging in and publishing applications.The impact was limited to O11 Personal Environments and a small subset of users, while impact on ODC remained contained.  \nAs AWS services recovered, many OutSystems environments resumed normal operation automatically. Some environments required additional recovery actions to fully restore service availability.  \nFor ODC, the incident was fully resolved on May 9, 2026, at 3:30 AM UTC. Recovery efforts for O11 Personal Environments continued afterward due to the additional complexity of restoring affected environments.  \nAll services are now operating as expected, and no user action is required.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-11T16:12:05.338Z",
"resolved_inferred": false,
"started_at": "2026-05-08T11:56:03.115Z",
"state": "postmortem",
"title": "Incident affecting Personal Environments for O11 and ODC",
"updated_at": "2026-05-13T16:11:01.078Z",
"url": "https://stspg.io/vzdrnh3344nq"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-21T10:19:47.188Z",
"resolved_inferred": false,
"started_at": "2026-04-21T02:36:07.374Z",
"state": "resolved",
"title": "Partial System outage",
"updated_at": "2026-04-21T10:19:47.205Z",
"url": "https://stspg.io/ryg03swwwm4s"
},
{
"body": "On April 13,2026 between 1:13 and 3:07 AM UTC, an incident occurred that prevented users from logging in to the ODC Portal across multiple regions. The issue was caused by a deployment of a Identity Service that required a database schema change that had not yet been applied, resulting in authentication failures.\n\nService was restored after the team initiated a rollback to the previous stable version. Validation confirmed that login functionality was restored for all users. \n\nThe incident is fully resolved, and all services are operating as expected.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-13T03:30:32.085Z",
"resolved_inferred": false,
"started_at": "2026-04-13T02:24:21.692Z",
"state": "postmortem",
"title": "Login Access Issue with ODC Portal",
"updated_at": "2026-04-13T07:20:42.658Z",
"url": "https://stspg.io/1qgrp5z7cl8l"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-30T11:22:22.790Z",
"resolved_inferred": false,
"started_at": "2026-03-29T01:06:32.583Z",
"state": "resolved",
"title": "Partial System outage",
"updated_at": "2026-03-30T11:22:22.806Z",
"url": "https://stspg.io/nrj6s3sx1598"
},
{
"body": "On March 19th, 2026, at approximately 06:43 UTC, an issue was identified affecting ODC, where some users were unable to complete the login process for the ODC Portal and ODC Studio when using external Identity Providers. Affected users encountered an error message stating \"Email verification not supported\" or were blocked from accessing their accounts because the system could not verify their email addresses via the external provider's claims.\n\nThe incident was caused by a configuration change intended to strictly enforce email verification from external providers. This change inadvertently bypassed a native fallback verification process that certain users relied upon when their external providers did not share specific verification data.\n\nThe issue was resolved by 11:00 UTC on March 19th following a rollback to the previous service versions. To prevent recurrence, future updates to this functionality will be implemented via a gradual rollout plan, including additional validation steps to ensure all identity provider configurations are fully supported.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-19T11:32:05.121Z",
"resolved_inferred": false,
"started_at": "2026-03-19T09:35:30.445Z",
"state": "postmortem",
"title": "Incident affecting ODC Portal and ODC Studio",
"updated_at": "2026-03-23T13:53:34.177Z",
"url": "https://stspg.io/dk0zwwqlzsr0"
},
{
"body": "On March 4th, 2026, between 2:39 am and 10:29 am UTC, ODC experienced an incident that prevented users from accessing the App Detail screen and performing app configurations across all stages. The runtime of existing applications was not affected by this issue.  \nThe root cause was a subscription validation misalignment between internal APIs and ODC Portal, which resulted in errors for customers without the ODC Sentry add-on.  \nTo prevent future occurrences, we are updating ODC Portal to verify subscription status in alignment with these APIs and improving UI error handling to ensure failures like this do not obstruct the overall page experience.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-04T10:41:33.282Z",
"resolved_inferred": false,
"started_at": "2026-03-04T09:09:44.870Z",
"state": "postmortem",
"title": "Incident affecting app access in ODC Portal",
"updated_at": "2026-03-10T11:02:31.186Z",
"url": "https://stspg.io/5lzx2hk4ny46"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-03T14:41:51.440Z",
"resolved_inferred": false,
"started_at": "2026-03-01T16:33:04.355Z",
"state": "resolved",
"title": "Connectivity and Power Issues Detected in Middle East",
"updated_at": "2026-07-03T14:41:51.455Z",
"url": "https://stspg.io/4242zfq5sgr1"
},
{
"body": "On January 30th, several ODC customers experienced intermittent issues where the username attribute was missing data from the User entity within applications.  \nThe cause was identified as a bug in a recent release of an identity component. This issue prevented specific user and identity provider data from correctly populating the Username Attribute.  \nThe incident was resolved by rolling back the affected release. A corrected version has since been deployed to ensure consistent data availability and prevent future occurrences.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-30T12:43:09.769Z",
"resolved_inferred": false,
"started_at": "2026-01-29T20:00:44.115Z",
"state": "postmortem",
"title": "Incident affecting logins in Europe (Frankfurt), Europe (London), and Israel (Central)",
"updated_at": "2026-02-06T14:39:55.999Z",
"url": "https://stspg.io/5qpcjnf89y3g"
},
{
"body": "On January 27th, we experienced a service disruption in Mentor affecting APAC and EMEA regions. Users encountered elevated error rates and a loss of functionality for Mentor features.\n\nThe incident was triggered by a third-party service outage, which hosts the models supporting our Data & AI services. While a fallback system was in place, it also became unavailable during the outage. Furthermore, the impact of the external service disruption also prevented our team from implementing a manual configuration fix immediately.\n\nWe are also working toward an automated fallback mechanism to minimize the need for manual intervention. Additionally, we are implementing agent-level fallbacks to different models at the product level.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-27T18:20:48.471Z",
"resolved_inferred": false,
"started_at": "2026-01-27T12:53:02.416Z",
"state": "postmortem",
"title": "Incident affecting Mentor",
"updated_at": "2026-01-30T09:04:20.033Z",
"url": "https://stspg.io/slyjjtjmn2rr"
},
{
"body": "On January 22nd, between 15:00 UTC and 17:00 UTC, an incident affected ODC in the Europe \\(Frankfurt\\) region. Users experienced issues with One-Click Publish, specifically resulting in build timeouts and publish failures. \n\nThe issue was caused by a communication failure between the internal queuing system and the Build Service, which prevented build processes from completing. \n\nOur team resolved the incident by restarting the Build Service and restoring communication. Normal service has been restored, and we are evaluating measures to improve system resilience moving forward.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-22T16:52:18.961Z",
"resolved_inferred": false,
"started_at": "2026-01-22T15:29:09.888Z",
"state": "postmortem",
"title": "Incident affecting 1CP operations in Europe Central region (Frankfurt)",
"updated_at": "2026-01-27T11:35:05.307Z",
"url": "https://stspg.io/xww82jbr7zdg"
},
{
"body": "On January 16th, a service change related to an ongoing migration caused a temporary issue where customers were unable to log in using their custom domains. Our engineering team immediately identified the cause and implemented a mitigation to resolve the issue quickly by temporarily disabling the custom domain redirection feature. A controlled restart of system deployments was performed to expedite this fix.\n\nTo ensure stability and prevent recurrence, a technical recommendation has been made to enhance the system. This improvement will increase resilience to future updates and configuration changes, helping maintain continuous operation without service interruptions.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-16T14:35:08.339Z",
"resolved_inferred": false,
"started_at": "2026-01-16T10:13:39.978Z",
"state": "postmortem",
"title": "Incident affecting login via custom domains",
"updated_at": "2026-01-29T10:12:43.916Z",
"url": "https://stspg.io/mqzxcg6vnrwp"
},
{
"body": "On December 8th, we experienced an issue affecting application deployments, resulting in application promotion failures to test and production stages.\n\nThe 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.\n\nTo resolve the issue, a configuration change was implemented to increase the connection limit on the internal message mechanism, and deployments recovered quickly thereafter.\n\nTo prevent new occurrences, we are creating an action item to limit retries on the offending job to mitigate future connection escalations.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-08T15:46:04.126Z",
"resolved_inferred": false,
"started_at": "2025-12-08T13:36:21.621Z",
"state": "postmortem",
"title": "Incident affecting application deployments in all regions",
"updated_at": "2025-12-12T08:08:06.910Z",
"url": "https://stspg.io/498m5b6z7f3x"
},
{
"body": "On December 8th, we experienced an issue that affected application publishing. This resulted in users being unable to publish any applications in the Development stage across all regions, encountering the error code OS-DPL-40802 \\(Deployment timeout\\).\n\nThe root cause of the incident was a new version of an internal service that was deployed around the same time the problem started. This new version contained changes that caused application deployments to fail.\n\nThe issue was resolved by reverting the internal service to the previous stable version.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-08T11:12:45.118Z",
"resolved_inferred": false,
"started_at": "2025-12-08T10:15:04.809Z",
"state": "postmortem",
"title": "Incident affecting 1-Click Publish functionality",
"updated_at": "2025-12-16T15:19:07.851Z",
"url": "https://stspg.io/jw3m5hm7hvp9"
},
{
"body": "On November 26th, an issue was experienced affecting Personal Editions users, resulting in users seeing a \u201cno permissions\u201d page and being unable to use their Personal Edition environments. Normal service was restored at 21:00 UTC.\n\nThe incident was caused by the reconfiguration step used to fix an earlier issue. This step correctly re-applied the Identity Provider \\(IdP\\) but also unintentionally made the affected Personal Editions environments available for re-assignment. As a result, many of the previously fixed Personal Editions were re-assigned to \"second\" users who were created without any permissions upon first login, leading to the \u201cno permissions\u201d screen.\n\nTo prevent new occurrences, all Personal Editions environments created during the faulty period that had gone through the reconfiguration were discarded. Impacted users were proactively informed and instructed to request a new Personal Edition.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-26T21:01:14.873Z",
"resolved_inferred": false,
"started_at": "2025-11-26T10:07:52.000Z",
"state": "postmortem",
"title": "Incident affecting Personal Edition Users \u2013 Post-Login Permissions Issue",
"updated_at": "2025-12-10T11:20:02.458Z",
"url": "https://stspg.io/9b0t367t722h"
},
{
"body": "On November 25th, around 11:15 UTC, we experienced an issue affecting Personal Editions, resulting in users being unable to log in and consistently seeing the error \u201cIncorrect username or password \\(OS-UAUC-60004\\)\u201d despite using valid credentials in the regions of US East \\(Ohio\\), Europe \\(Ireland\\), and Asia Pacific \\(Singapore\\). Normal service was restored by approximately 17:00 UTC the same day.\n\nThe incident was caused by an issue in provisioning that led Personal Editions to not have the built-in community provider configured as an Identity Provider. This resulted in the login failures when users attempted to access their Personal Editions.\n\nTo prevent new occurrences, the provisioning logic was updated to treat a similar empty response as an error, triggering an internal alert and preventing affected environments from being handed out as ready-to-use. Additionally, a targeted reconfiguration job was run to correctly apply the required identity provider to all impacted Personal Editions, which restored normal login functionality",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-25T17:06:54.578Z",
"resolved_inferred": false,
"started_at": "2025-11-25T12:37:30.726Z",
"state": "postmortem",
"title": "Incident Affecting ODC Personal Edition User Logins",
"updated_at": "2025-12-10T11:20:40.200Z",
"url": "https://stspg.io/xhp7dstdcytp"
},
{
"body": "On November 24, 2025, a new version of our deployment service was released, including an internal library update intended to optimize the processing of external libraries. This update inadvertently caused a logic error that made deployments hang during certain operations, leading to intermittent timeouts for customers deploying external libraries or applications that depend on them. Not all deployments were affected, and the impact varied by region and library volume. We immediately reverted the service to the previous stable version, restoring normal deployment operations. \n\nWe are working to correct the issue in the internal library and will reintroduce the optimization after thorough validation to prevent future disruptions. \n\nWe apologize for the inconvenience and appreciate your patience.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-24T12:09:07.383Z",
"resolved_inferred": false,
"started_at": "2025-11-24T11:46:09.029Z",
"state": "postmortem",
"title": "Incident affecting timeouts when deploying an app with external libraries packaged",
"updated_at": "2025-12-03T15:20:37.260Z",
"url": "https://stspg.io/h4850fcpllvn"
},
{
"body": "On November 18th, we experienced an issue that prevented users with Personal Editions from accessing the ODC Portal login page. Customers who were affected saw the error message: \"Something unexpected happened during login. Please try logging in again using a new tab or a different browser\". Normal service was restored at 11:09 AM UTC.\n\nThe incident was caused by a recent system update that introduced an error in how login data was processed. Full access was restored after we reverted the affected system component to its previous version. We apologize for the inconvenience this caused.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-18T11:28:20.067Z",
"resolved_inferred": false,
"started_at": "2025-11-18T09:56:52.556Z",
"state": "postmortem",
"title": "Incident affecting Personal Edition login",
"updated_at": "2025-11-20T16:21:35.513Z",
"url": "https://stspg.io/pfsvtg8t2c31"
},
{
"body": "A platform-wide issue was identified where log messages generated within successful Timers were inconsistently or completely missing from the monitoring interface.  \nThe root cause was a technical race condition during a critical component startup, which prevented logs from reaching the central logging system. Engineering team developed and deployed an update that resolved the issue, and extensive monitoring has confirmed the platform is now stable, with all Timer-originated log entries appearing correctly.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-17T17:45:47.025Z",
"resolved_inferred": false,
"started_at": "2025-11-14T14:26:56.766Z",
"state": "postmortem",
"title": "Incident affecting timers LogMessage in ODC Portal",
"updated_at": "2025-11-19T09:05:27.654Z",
"url": "https://stspg.io/3z8cdnsvqdn5"
},
{
"body": "Customers experienced intermittent service issues with core operations, including deployments and authentication, between 2:58 and 10:40 UTC.  \nThe disruption was caused by a core system component reaching its maximum connection limit. Our engineering team successfully identified the issue, implemented a configuration update to increase connection capacity, and fully restored service by 10:40 UTC.  \nWe are also conducting a full analysis to understand the unexpected usage increase and are enhancing our monitoring for earlier detection of similar events in the future.  \nWe apologize for the inconvenience this may have caused.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-11T10:50:20.250Z",
"resolved_inferred": false,
"started_at": "2025-11-11T09:36:03.178Z",
"state": "postmortem",
"title": "Incident affecting Deployments to Production, Application Runtime and End-User Authentication",
"updated_at": "2025-11-13T12:47:29.293Z",
"url": "https://stspg.io/20p6d18rjs6b"
},
{
"body": "On November 10th, a system optimization deployment led to a two-hour unavailability of core platform services due to a missing technical dependency. \n\nAlthough quickly resolved, the incident underscored the critical importance of strictly adhering to comprehensive quality assurance gates to ensure platform stability and prevent service disruption.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-10T15:16:52.293Z",
"resolved_inferred": false,
"started_at": "2025-11-10T13:16:43.747Z",
"state": "postmortem",
"title": "Incident affecting user authentication on ODC Portal",
"updated_at": "2025-11-19T09:20:34.834Z",
"url": "https://stspg.io/tg7mn6hzyhs0"
},
{
"body": "On October 20, some customers noticed duplicate timer execution logs appearing in the console. A fix was implemented to address this issue.  \nOn November 3, another issue occurred in which parts of the timer log display were missing in the console. The investigation determined that the problem originated from a faulty service version introduced in a recent update. The affected version was identified and fixed.  \nThe issue was fully resolved on November 7 at 13:07 UTC, and normal log visibility is now available for all customers. \n\nWe sincerely apologize for the inconvenience and appreciate your patience while we worked to restore full functionality.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-07T12:38:39.944Z",
"resolved_inferred": false,
"started_at": "2025-11-06T09:41:34.347Z",
"state": "postmortem",
"title": "Incident affecting timer logs",
"updated_at": "2025-11-10T12:00:49.529Z",
"url": "https://stspg.io/rbqkhdv4swgt"
},
{
"body": "On October 30th, between 18:55 UTC and 21:22 UTC, customers experienced degraded success rates and timeouts when using the 1-Click Publish functionality. The issue, caused by an internal system component, was identified and resolved by our engineering team through a service restart, which immediately restored normal operation by 9:22 PM WET.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-30T21:24:39.984Z",
"resolved_inferred": false,
"started_at": "2025-10-30T20:46:05.199Z",
"state": "postmortem",
"title": "ODC - 1CP fails due to build timeout (OS-DPL-BLD-40801)",
"updated_at": "2025-11-13T15:52:46.556Z",
"url": "https://stspg.io/ldkzbpcbj6lz"
},
{
"body": "On October 29th, at approximately 08:15 AM UTC, we observed a significant drop in service success rate primarily affecting Personal Edition instances. Users may have experienced timeout errors.  \nAn immediate investigation traced the issue to a recent deployment. Reverting to the previous version resolved the problem, and all affected environments were restored to a healthy condition.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-29T14:23:19.676Z",
"resolved_inferred": false,
"started_at": "2025-10-29T11:49:37.168Z",
"state": "postmortem",
"title": "Incident affecting 1-Click-Publish operations",
"updated_at": "2025-11-05T08:25:26.543Z",
"url": "https://stspg.io/y9pcys1nqjwg"
},
{
"body": "On October 20, some customers across all regions experienced issues logging in using external Identity Providers \\(IdPs\\), receiving an error or not being redirected to complete authentication. A temporary workaround was provided while the root cause, a faulty service version introduced in recent updates, was identified and reverted.\n\nThe issue was fully resolved on October 20 at 18:15 UTC, restoring normal login functionality for all customers. The incident duration was extended due to an unrelated AWS outage that impacted service rollback times.\n\nWe apologize for the inconvenience and appreciate your patience while we restored full functionality.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-20T16:21:38.883Z",
"resolved_inferred": false,
"started_at": "2025-10-20T14:57:55.773Z",
"state": "postmortem",
"title": "External authentication issues (502 error) when logging into ODC with External IdPs in all regions",
"updated_at": "2025-11-04T09:39:46.797Z",
"url": "https://stspg.io/5g2h1wg1sms9"
},
{
"body": "On October 20th, our cloud service provider experienced a high error rate and latency in the N. Virginia Region, which temporarily affected some of our internal tools and caused service disruption for\u00a0O11 and ODC customers.  \nThe issue was first reported at 08:37 UTC\\+1 for ODC, affecting access to ODC Studio and running applications in ODC Portal.  \nO11 had the first report at 08:54 UTC\\+1. Cloud customers weren't able to access their Service Centers, IdP Authentication started to present some failures, CloudWatch started to fail, and several other symptoms were felt, since it affected several networking resources, including 503 error messages.  \nCustomers also experienced delays or interruptions using our services, including Forge, MABs, Licensing Registration, and accessing our Portals and telephony services.  \nOur Support and Operations teams closely monitored the situation throughout the day, providing continuous updates to affected customers and coordinating internally to restore full functionality as quickly as possible.  \nBy 14:06 UTC\\+1, it was reported that a full recovery of services had been achieved, and customers began confirming that their services were operating normally. However, later in the afternoon, around 16h32 UTC\\+1, we started again receiving reports of connectivity issues, affecting O11 customers. During the recovery process, due to latency errors, several customers experienced network connectivity issues. Our teams continued providing updates and ensured all systems remained stable.  \nAWS confirmed that all its services returned to normal operations by 23:01 UTC\\+1. This disruption affected 142 AWS services, causing a direct impact on OutSystems services. They determined that the incident was caused by DNS resolution issues affecting DynamoDB. Following this, EC2 instance launches and Network Load Balancer health checks were also impacted, which in turn affected connectivity for Lambda, DynamoDB, and CloudWatch. \n\nWe apologize for any inconvenience caused and thank you for your patience.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-20T13:06:17.063Z",
"resolved_inferred": false,
"started_at": "2025-10-20T09:43:29.542Z",
"state": "postmortem",
"title": "Incident affecting Platform in ODC and O11 in US Virginia",
"updated_at": "2025-10-23T08:01:00.677Z",
"url": "https://stspg.io/plw425xnzsx6"
},
{
"body": "On October 15th, multiple customers reported being unable to log in to ODC Studio, temporarily interrupting their development work. Access through the ODC Portal remained available.\n\nThe issue was caused by recent Microsoft Windows updates affecting certain users. A temporary workaround was provided, and uninstalling the updates restored normal access. Microsoft has since released an update to resolve the problem, and customers should now be able to run Windows Update and install it.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-15T23:26:27.616Z",
"resolved_inferred": false,
"started_at": "2025-10-15T17:25:25.422Z",
"state": "postmortem",
"title": "Cannot log in through ODC Studio",
"updated_at": "2025-10-16T13:06:33.511Z",
"url": "https://stspg.io/1vrt43j6pfc2"
},
{
"body": "On October 7th, 2025, the TimerManager service experienced an issue that prevented it from responding to requests, leading to customers being unable to execute their timers and continue development. The problem was resolved by restarting the affected service, which restored full functionality.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-07T12:12:26.938Z",
"resolved_inferred": false,
"started_at": "2025-10-07T10:51:09.988Z",
"state": "postmortem",
"title": "Incident affecting Timers on Asia Pacific (Tokyo)",
"updated_at": "2025-10-28T09:33:10.024Z",
"url": "https://stspg.io/7tzzp6hk9d5s"
},
{
"body": "On Wednesday, August 20, between 18:09 UTC and 21:58 UTC, some customers experienced intermittent errors in the DEV environment in US East \\(Virginia\\) and Europe \\(Frankfurt\\).  \nSupport teams identified a configuration issue that reduced service availability. A workaround was shared, and service was fully restored by 21:58 UTC. A permanent fix has since been applied to prevent similar issues in the future.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-08-20T21:43:07.992Z",
"resolved_inferred": false,
"started_at": "2025-08-20T19:39:01.654Z",
"state": "postmortem",
"title": "Issue Affecting Applications in US East / Virginia and Europe / Frankfurt",
"updated_at": "2025-08-26T08:10:29.346Z",
"url": "https://stspg.io/gc19tzwjzrm7"
},
{
"body": "On August 14th, a system update caused a critical service to restart with a faulty configuration, leading to connectivity issues for some applications. The issue was addressed and resolved on the same day by correcting the configuration.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-08-14T18:37:39.397Z",
"resolved_inferred": false,
"started_at": "2025-08-14T15:21:00.981Z",
"state": "postmortem",
"title": "Online community degraded performance",
"updated_at": "2025-08-18T11:13:21.122Z",
"url": "https://stspg.io/g2tgwhkpd5k3"
}
]
}