Warp

Affected: Cloud agent execution

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-10-20 15:58 UTC

   We are investigating an issue with Warp-hosted agents waiting to be assigned to sandboxes.

2. investigating 2026-10-20 17:20 UTC

   We are continuing to investigate this issue.

3. resolved 2026-10-20 17:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Automations and integrations

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-10-16 15:34 UTC

   We are currently investigating a regression which prevents Oz scheduled cloud agents from executing.

2. monitoring 2026-10-16 17:49 UTC

   We have rolled out a remediation and are monitoring recovery.

3. resolved 2026-10-16 18:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Live sessions and agent control

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-09-30 14:22 UTC

   We are currently investigating an issue with degraded session share capabilities. Follow-ups and real-time communication with cloud agents is degraded.

2. identified 2026-09-30 14:59 UTC

   The issue has been identified and a fix is in progress.

3. monitoring 2026-09-30 16:51 UTC

   A fix has been deployed and we are monitoring the results.

4. resolved 2026-09-30 19:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Warp'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. resolved 2026-08-17 21:00 UTC

   Fully recovered by 5:24PM (ET).

Excerpts are shortened. Read the full incident on Warp'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. resolved 2026-06-23 15:30 UTC

   We discovered a issue where Oz runs were unable to start when invoked from the web.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Account, team, and data services

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-06-15 22:08 UTC

   Our servers are currently experiencing elevated latencies. We are currently investigating.

2. monitoring 2026-06-15 23:36 UTC

   We are still investigating a fix but latencies have returned to normal.

3. resolved 2026-06-16 00:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: warp.dev

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-27 19:43 UTC

   The warp.dev marketing page is down. We are currently investigating.

2. resolved 2026-04-27 20:09 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Account, team, and data services

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. identified 2026-04-13 12:28 UTC

   We are investigating inconsistent login errors due to unavailability of a third-party provider component.

2. identified 2026-04-13 12:29 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2026-04-13 13:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Account, team, and data services

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 18:01 UTC

   We're seeing reports of partial DNS failures when looking up `app.warp.dev`. We're investigating.

2. identified 2026-03-16 19:30 UTC

   The issue appears to be related to our hosting provider, GoDaddy, who is aware of an issue affecting DNS resolution on their side. If you're experiencing issues, flushing your DNS cache may help.

3. resolved 2026-03-16 22:33 UTC

   GoDaddy has resolved their issues and access to Warp appears restored. Thank you for your patience.

Excerpts are shortened. Read the full incident on Warp'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. resolved 2026-03-02 02:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Account, team, and data services

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 15:40 UTC

   We're investigating intermittent failures loading oz.warp.dev

2. investigating 2026-02-19 15:40 UTC

   We are continuing to investigate this issue.

3. resolved 2026-02-19 16:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Account, team, and data services

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. 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-02-13 12:30 UTC

   We are currently investigating this issue.

2. monitoring 2026-02-13 15:01 UTC

   A fix has been implemented and our systems are recovering. We are monitoring and investigating the root cause.

3. resolved 2026-02-13 19:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Account, team, and data services

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. investigating 2026-02-11 19:05 UTC

   We are currently investigating this issue.

2. identified 2026-02-11 19:28 UTC

   We’ve rolled back the recent change and service has been restored. Server is operating normally and we are continuing to investigate the root issue.

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

   A fix has been implemented and we're monitoring the results.

4. resolved 2026-02-11 22:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Warp's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-01-24 18:00 UTC

   Between 1:00 PM and 2:00 PM ET on Jan 24, 2026, some Agent Mode requests returned “Rate limit exceeded” errors. Service has been restored and Agent Mode is operating normally.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Account, team, and data services

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 2025-10-30 15:48 UTC

   We are currently investigating an issue with Warp's session-sharing functionality

2. resolved 2025-10-30 16:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Warp'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 high confidence (taxonomy v0.2).

1. resolved 2025-10-28 15:30 UTC

   Agent mode requests are failing with this error message I'm sorry, I couldn't complete that request. Request failed with error: ErrorStatus(401, "{\"error\":\"Unauthorized: User not in context: ERROR: column \\\"is_eligible_for_reverse_team_trial\\\" does not exist (SQLSTATE...

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: warp.dev

Failure mode: Security incident or emergency response to a vulnerability. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2025-10-21 14:43 UTC

   Log in and sign up at https://app.warp.dev/login via email is disabled due to continued abuse of our account creation APIs. We are continuing investigation and centralizing discussion in this GitHub issue: https://github.com/warpdotdev/Warp/issues/7808

2. investigating 2025-10-22 18:46 UTC

   We are continuing to investigate this issue.

3. resolved 2025-10-22 18:49 UTC

   We've re-enabled email login with a CAPTCHA check to prevent scaled abuse. Thanks for your patience.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: warp.dev, Account, team, and data services, Warp Client

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2025-10-19 01:25 UTC

   Attempting to log in at https://app.warp.dev/login via email is unavailable. Logging in via Google, GitHub, or SSO is unaffected. We are investigating.

2. investigating 2025-10-19 02:09 UTC

   We're aware that many authenticated requests from Warp, including Agent Mode requests, are failing. We're working to get things back up as soon as possible.

3. identified 2025-10-19 03:41 UTC

   We identified a major issue impacting authenticated requests originating from the Warp client, and have resolved it. We are still investigating issues with login. We are centralizing discussion in this GitHub issue: https://github.com/warpdotdev/Warp/issues/7808

4. resolved 2025-10-20 21:31 UTC

   We've restored email-based login to Warp. Thanks for your patience.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Account, team, and data services, Live sessions and agent control, Warp Client

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: Google Cloud.

1. investigating 2025-06-12 18:19 UTC

   Google Cloud Platform, Warp's cloud provider, appears to be experiencing issues. All Warp services are impacted. We are investigating.

2. identified 2025-06-12 18:53 UTC

   Google Cloud Platform has updated their status page, acknowledging the outage. We anticipate Warp's cloud services will return when Google resolves their issues. See https://status.cloud.google.com/

3. monitoring 2025-06-12 19:55 UTC

   Google Cloud services appear to be recovering slowly. Some Warp cloud functionality appears to be working, but Google has not stated the fix is complete just yet, so some users may still experience errors. We will continue to monitor and provide updates.

4. resolved 2025-06-13 00:28 UTC

   While Google is still experiencing issues in some regions, Warp's services are healthy once again.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Account, team, and data services, Live sessions and agent control

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. resolved 2025-01-22 19:37 UTC

   For a brief period, all requests to our server were failing.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Warp Client

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. monitoring 2024-12-03 01:19 UTC

   Updating the Warp client on macOS sometimes results in a corrupted application - see https://github.com/warpdotdev/Warp/issues/5492 for details. If affected, please reinstall Warp

2. resolved 2025-01-03 20:45 UTC

   We've made changes to ensure Warp will not install a corrupted update. If affected when updating from an older Warp version, please reinstall.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Account, team, and data services

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-10-31 22:01 UTC

   We are currently experiencing and actively investigating an issue where logging in via email on app.warp.dev does not load after email authentication. Existing logins are unaffected.

2. resolved 2024-10-31 22:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Warp's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-09-19 22:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Account, team, and data services

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. identified 2024-03-19 23:10 UTC

   We are currently experiencing an issue where assets on app.warp.dev pages may fail to load for a small percentage of attempts (2%), leading to a broken webpage. We have identified the issue and are actively working on resolving it. In most cases, clearing your browser's cache...

2. resolved 2024-03-19 23:47 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Warp's status page.

Affected: Warp Client

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-02-05 23:38 UTC

   We are investigating reports that Warp may be blocked for CrowdStrike users. If you experience this issue, please email us at feedback@warp.dev.

2. investigating 2024-02-06 19:15 UTC

   Warp users at a single company may be blocked from using Warp on MacOS Sonoma 14.3 due to permissions restrictions. If you experience this issue, please email us at feedback@warp.dev.

3. resolved 2024-02-10 03:42 UTC

   After investigating, Warp has determined this incident only affects a single company which has blocked Warp while performing a security review of the software. We are now closing this issue as it does not affect Warp users at large. We are in communication with the affected...

Excerpts are shortened. Read the full incident on Warp's status page.