Ona (Gitpod)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

Started during GitHub: Incident with GitHub.com.

1. investigating 2026-08-17 15:02 UTC

   GitHub originated incident is resulting in environments being unable to checkout content, webhooks for automations are not being delivered.

2. monitoring 2026-08-17 16:02 UTC

   GitHub continues to be affected with many of their services degraded - [https://www.githubstatus.com/incidents/zkxwbgr0cnmx](https://www.githubstatus.com/incidents/zkxwbgr0cnmx "https://www.githubstatus.com/incidents/zkxwbgr0cnmx"). Ona environments and agent sessions using...

3. monitoring 2026-08-17 17:06 UTC

   GitHub has indicated the issue has been resolved, we're seeing improvements to the error rate and continue to observe.

4. resolved 2026-08-17 17:47 UTC

   We're no longer seeing degradation when interacting with GitHub.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. identified 2026-07-25 09:31 UTC

   Users using Codex can experience delays or intermittent errors due to an OpenAI API and Codex outage.

2. monitoring 2026-07-25 10:12 UTC

   OpenAI applied a mitigation and we haven't observed errors for the past 30 minutes. We will keep monitoring.

3. resolved 2026-07-25 12:05 UTC

   OpenAI confirmed that their mitigation is in place and stable. We haven't seen errors in the past hour. Codex conversations operational.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. monitoring 2026-07-23 19:37 UTC

   Codex conversations may be slow or fail right now due to an OpenAI service degradation. We're monitoring and will update shortly.

2. monitoring 2026-07-23 20:21 UTC

   Codex conversations may be slow or fail right now due to an OpenAI outage. We're monitoring and will update shortly.

3. monitoring 2026-07-23 20:26 UTC

   Codex conversations performance has returned to baseline conditions. We will continue to monitor the issue

4. resolved 2026-07-23 20:36 UTC

   Codex conversations are fully operational now.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. investigating 2026-06-23 14:43 UTC

   free/core customers with Ona backed by an Anthropic model and enterprise with BYOK Anthropic integration are experiencing slower or not working conversations.

2. identified 2026-06-23 14:47 UTC

   Confirmed is due to an Anthropic outage. You can use Codex on free/core as alternative as it's not impacted.

3. monitoring 2026-06-23 15:58 UTC

   A fix was introduced by Anthropic and we can observe less errors on affected conversations. We're still monitoring.

4. resolved 2026-06-23 16:48 UTC

   Anthropic resolved the outage and we haven't been experiencing disruptions in the past hour. Closing the incident.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-18 12:59 UTC

   We're seeing an increase in start duration for agent sessions. The environment starts normally but agents are taking a while to start. We're actively investigating the issue

2. investigating 2026-06-18 13:47 UTC

   We've observed that VS Code Browser, services, and tasks are also suffering from degraded performance.

3. monitoring 2026-06-18 14:38 UTC

   We scaled messaging infrastructure to address a capacity issue, and have observed performance is now normal. We'll continue to monitor to ensure the problem is resolved.

4. monitoring 2026-06-18 15:02 UTC

   Degraded performance is ongoing, we'll pursing a follow-up fix to mitigate, and will update the incident in 30m.

5. monitoring 2026-06-18 15:27 UTC

   We shipped a fix to shift traffic to the newly scaled up infrastructure and have observed an improvement in performance. We'll continue to monitor the situation.

6. resolved 2026-06-18 17:36 UTC

   Performance continues to remain quick and stable.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-29 14:00 UTC

   We're experiencing disrupted environment and conversations experience with intermittent failures and delays. We have identified the issue and are working to deploy a fix in the next minutes. All customers on free, core and enterprise tiers are impacted.

2. monitoring 2026-05-29 14:13 UTC

   Environments and conversations should now work as expected. We rolled back changes that caused the disruption.

3. identified 2026-05-29 14:47 UTC

   We're experiencing more degraded experience for environments and conversations and are looking into applying a fix in the next minutes to prevent.

4. monitoring 2026-05-29 14:55 UTC

   We applied a fix an now conversations and environments should no longer be disrupted. We're monitoring the fix.

5. resolved 2026-05-29 16:44 UTC

   We monitored the fix and observed no disruptions to environments or conversations in the past hours. We're resolving the incident.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-05 17:29 UTC

   Reports of US customers cannot start environments.

2. investigating 2026-05-05 17:51 UTC

   The issue has been identified and we are preparing a fix.

3. resolved 2026-05-05 18:55 UTC

   This has now been resolved.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-22 18:46 UTC

   We are aware of an issue impacting Ona conversations, where the agent is not responding. Old environments will continue to work, but new agent conversations will not. We are investigating.

2. monitoring 2026-04-22 19:43 UTC

   We have applied a fix and are currently monitoring the situation. Please note that any previously unresponsive conversations will need to be reset.

3. resolved 2026-04-22 20:25 UTC

   Conversations start normally again.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-21 15:59 UTC

   We've received reports of [app.gitpod.io](http://app.gitpod.io "app.gitpod.io") being inaccessible, investigating

2. resolved 2026-04-21 16:17 UTC

   Edge CDN has cached an incomplete frontend-asset, which prevented the dashboard from loading.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-17 08:40 UTC

   We're seeing issues starting new Ona conversations. Not all conversations might be impacted. We identified the issue and are on track to fix it.

2. monitoring 2026-04-17 08:48 UTC

   We deployed a fix and are monitoring. New conversations should work as expected.

3. resolved 2026-04-17 10:51 UTC

   The issue has been fully resolved and we haven't observed disrupted conversations in the last hour.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-01 15:56 UTC

   Ona Cloud customers are seeing `Ask your admin to enable Agents for your organization.` when trying to start new agent conversations on Environments. We are investigating the issue.

2. identified 2026-04-01 16:09 UTC

   We have identified a possible root cause and are rolling out a fix

3. identified 2026-04-01 16:11 UTC

   We have identified a possible root cause and are rolling out a fix

4. monitoring 2026-04-01 16:14 UTC

   We've rolled out a fix. New and existing environments should have accessible agent conversations again.

5. resolved 2026-04-01 16:48 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-03-30 19:49 UTC

   We've identified an increase in Github logins failing. Existing GitHub sessions continue work OK, new logins are failing.

2. identified 2026-03-30 20:03 UTC

   We've identified the issue. Originally we suspected Github logins failing, however, we've since narrowed it down to custom SSO configurations.

3. identified 2026-03-30 20:41 UTC

   Our initial attempt at a mitigation has been ineffective. We're applying a secondary mitigation. The issue stems from stricter SSO claims validation, which affects some IDPs. Next update in <30m.

4. identified 2026-03-30 21:14 UTC

   The bulk of the issues have now been mitigated. We're still tracking a small number of failing logins, and we continue to investigate.

5. identified 2026-03-30 21:47 UTC

   We've identified the cause of the remaining failures, applying a fix.

6. resolved 2026-03-30 22:21 UTC

   We've applied a fix, and we're not seeing any new errors.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. monitoring 2026-03-27 08:55 UTC

   Core and Free customers might experience disrupted conversations.

2. resolved 2026-03-27 17:16 UTC

   Anthropic API recovered for more than 1h. Customers on free and core plans won't be impacted anymore.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-03-24 12:50 UTC

   A small group of customers is experiencing issues starting new environments - existing environments are able to start. We are investigating the root cause.

2. monitoring 2026-03-24 13:28 UTC

   We've rolled back to the prior stable release as a mitigation, and confirmed that new environments are able to start. AWS Runners will pickup the change in the next 5m. After waiting, please try creating new environments again.

3. resolved 2026-03-24 13:47 UTC

   The rollback was successful. Users are able to start new environments after the Runner auto-updated.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. identified 2026-03-18 12:59 UTC

   Anthropic unavailability impacting Ona core and free customers.

2. resolved 2026-03-18 14:52 UTC

   We observed anthropic API availability for over one hour and can confirm that we're no longer impacted.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-16 14:54 UTC

   VSCode web and local not starting on new environments. We're investigating.

2. identified 2026-03-16 14:57 UTC

   The issue is caused by VSCode Update Service unavailability - [https://github.com/microsoft/vscode/issues/302112](https://github.com/microsoft/vscode/issues/302112 "https://github.com/microsoft/vscode/issues/302112"). We're assessing what we can do to circumvent the issue now.

3. monitoring 2026-03-16 15:27 UTC

   Upstream recovered, VSCode is available in all Ona environments again

4. resolved 2026-03-16 15:53 UTC

   Upstream failure rate has fully recovered, all environments operational since.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. monitoring 2026-03-03 09:19 UTC

   Anthropic high error rate is leading to degraded conversation experience for Ona free and core customers as well as for customers with a custom Anthropic integration.

2. resolved 2026-03-03 11:14 UTC

   Anthropic API has been looking healthy for the past 1h. Closing the incident.

3. investigating 2026-03-03 12:40 UTC

   Spike of Anthropic API errors on Opus 4.6. Customers on free and core plan as well as customers with custom Anthropic integration will be impacted.

4. resolved 2026-03-03 14:29 UTC

   We observed no issues for the past 1:30h. Closing the incident.

5. identified 2026-03-04 14:49 UTC

   Anthropic API are experiencing high error rates. Ona free and core customers, as well as customers on enterprise with a custom Anthropic integration will be impacted and have potential disruptions in their conversations

6. resolved 2026-03-04 16:36 UTC

   We observed no issues for the past 1h. Closing the incident.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. identified 2026-03-02 14:34 UTC

   Anthropic API outage is impacting the reliability of conversations for Ona free and core customers.

2. monitoring 2026-03-02 15:55 UTC

   Monitoring Anthropic API status before closing the incident.

3. resolved 2026-03-02 16:16 UTC

   Anthropic APIs are stable and have been stable for the past 30m. Conversations on all tier should work as usual.

4. monitoring 2026-03-02 17:04 UTC

   Anthropic API are having issues. Customers on Ona free and core as well as customers with custom Anthropic integrations will be impacted and have degraded experience in conversations.

5. resolved 2026-03-02 18:03 UTC

   Anthropic API availability looks healthy and we've monitored no issues for the past 40m. Conversations should work as expected on all plans.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. monitoring 2026-02-27 15:09 UTC

   We are actively monitoring an upstream issue that is causing elevated conversation errors on Ona Cloud. The provider is working on a resolution, which can be tracked here: [https://status.claude.com/incidents/6rw4nd44bqqh](https://status.claude.com/incidents/6rw4nd44bqqh...

2. monitoring 2026-02-27 15:26 UTC

   Correction: Our previous update included an incorrect link. You can track the upstream Anthropic incident here: [https://status.claude.com/incidents/zp9x05pcbwxq](https://status.claude.com/incidents/zp9x05pcbwxq "https://status.claude.com/incidents/zp9x05pcbwxq"). We are...

3. resolved 2026-02-27 17:37 UTC

   The upstream issue with Anthropic has been resolved, and we have confirmed that conversation errors on Ona Cloud have subsided. All systems are fully operational again. Thank you for your patience while this was being addressed.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-26 09:29 UTC

   Dashboard unresponsive in some sessions.

2. identified 2026-02-26 09:40 UTC

   Issue identified and we're applying a fix.

3. monitoring 2026-02-26 09:49 UTC

   Fix applied and we're monitoring. The dashboard should be now responsive.

4. resolved 2026-02-26 10:17 UTC

   We verified that the fix works as expected. Dashboard loads as expected.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. investigating 2026-02-25 14:11 UTC

   Conversations disrupted for free and core Ona users. Users on enterprise with custom Anthropic integrations can be impacted on these models.

2. resolved 2026-02-25 16:34 UTC

   Conversation on Opus and Sonnet 4.6 are back to normal availability.

3. monitoring 2026-02-25 17:17 UTC

   Elevated error rate of Opus and Sonnet 4.6 backed conversations on free and core tiers. Customers with custom anthropic llm integrations are impacted as well.

4. resolved 2026-02-25 18:41 UTC

   Anthropic API have been stable for the past hour.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. investigating 2026-02-23 08:22 UTC

   Conversations are stuck and showing errors for Ona Cloud users, because the Anthropic API is overloaded. We’re on it and working toward a resolution. Enterprise customers using "Ona Intelligence" remain unaffected.

2. investigating 2026-02-23 08:36 UTC

   We are actively monitoring an upstream issue that is causing elevated conversation errors on Ona Cloud. The provider is working on a resolution, which can be tracked here: [https://status.claude.com/incidents/162g24n9sm8p](https://status.claude.com/incidents/162g24n9sm8p...

3. resolved 2026-02-23 10:08 UTC

   This incident has been resolved by our upstream provider. Ona Cloud is now operating normally. We apologize for any inconvenience this may have caused.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-19 09:58 UTC

   We are investigating reports from some users that conversations are starting slower than usual

2. identified 2026-02-19 10:37 UTC

   We have been able to reproduce the issue and are currently working on a fix.

3. monitoring 2026-02-19 11:46 UTC

   Monitoring fix in new environments.

4. resolved 2026-02-19 15:21 UTC

   The issue is fixed and all conversations work as expected on new environments,

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. identified 2026-02-18 15:50 UTC

   Customers on free, core plans are impacted. Enterprise customers not on Ona Intelligence (Bring Your Own Key) and that use Anthropic directly are impacted: they will have issues starting or continuing conversations.

2. resolved 2026-02-18 19:05 UTC

   All chats on Ona Cloud and Ona Intelligence customers should function as usual. Customers with an Anthropic custom BYOK should also not be impacted anymore.

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-16 18:21 UTC

   The issue has been identified and a fix is currently being deployed. We are working to restore command functionality immediately.

2. resolved 2026-02-16 19:00 UTC

   A fix has been deployed and commands are fully restored. If you still encounter issues, please reset your conversation or restart the environment to apply the changes

Excerpts are shortened. Read the full incident on Ona (Gitpod)'s status page.