Elevated error rates on oz.warp.dev
Timeline · 1 update
- resolved Jun 23, 2026, 04:48 PM UTC
We discovered a issue where Oz runs were unable to start when invoked from the web.
Warp had 14 outages in the last 2 years totaling 93h 42m of downtime — averaging 0.6 incidents per month.
There were 14 Warp outages since October 19, 2025 totaling 93h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.
We discovered a issue where Oz runs were unable to start when invoked from the web.
Our servers are currently experiencing elevated latencies. We are currently investigating.
We are still investigating a fix but latencies have returned to normal.
This incident has been resolved.
The warp.dev marketing page is down. We are currently investigating.
This incident has been resolved
We are investigating inconsistent login errors due to unavailability of a third-party provider component.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We're seeing reports of partial DNS failures when looking up `app.warp.dev`. We're investigating.
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.
GoDaddy has resolved their issues and access to Warp appears restored. Thank you for your patience.
This incident has been resolved.
We're investigating intermittent failures loading oz.warp.dev
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and our systems are recovering. We are monitoring and investigating the root cause.
This incident has been resolved.
We are currently investigating this issue.
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.
A fix has been implemented and we're monitoring the results.
This incident has been resolved.
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.
We are currently investigating an issue with Warp's session-sharing functionality
This incident has been resolved.
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 42703)\"}") Update (15:40 UTC): A bad server release has been rolled back, and the incident is resolved
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
We are continuing to investigate this issue.
We've re-enabled email login with a CAPTCHA check to prevent scaled abuse. Thanks for your patience.
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.
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.
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
We've restored email-based login to Warp. Thanks for your patience.