Warp Outage History
15 incidents recorded over the last 365 days, 15 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Warp Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 23, 2026 | Degraded API reliabilityThis incident has been resolved. | 5h 40m | Resolved |
| Oct 20, 2026 | Warp-hosted agents waiting to be assigned to sandboxesThis incident has been resolved. | 1h 22m | Resolved |
| Oct 16, 2026 | Scheduled cloud agents unavailableThis incident has been resolved. | 2h 34m | Resolved |
| Sep 30, 2026 | Session sharing is degradedThis incident has been resolved. | 4h 44m | Resolved |
| Aug 17, 2026 | Incident with oz.warp.devFully recovered by 5:24PM (ET). | -30 min | Resolved |
| Jun 23, 2026 | Elevated error rates on oz.warp.devWe discovered a issue where Oz runs were unable to start when invoked from the web. | -78 min | Resolved |
| Jun 15, 2026 | Elevated LatenciesThis incident has been resolved. | 2h 37m | Resolved |
| Apr 27, 2026 | Warp.dev webpage is downThis incident has been resolved | 26 min | Resolved |
| Apr 13, 2026 | Partial login unavailabilityThis incident has been resolved. | 57 min | Resolved |
| Mar 16, 2026 | Intermittent DNS IssuesGoDaddy has resolved their issues and access to Warp appears restored. Thank you for your patience. | 4h 31m | Resolved |
| Mar 2, 2026 | Warp Server partial outageThis incident has been resolved. | 0 min | Resolved |
| Feb 19, 2026 | Partial outage of oz.warp.devThis incident has been resolved. | 1h 12m | Resolved |
| Feb 13, 2026 | Service is overloadedThis incident has been resolved. | 7h 26m | Resolved |
| Feb 11, 2026 | Service overloadThis incident has been resolved. | 3h 42m | Resolved |
| Jan 24, 2026 | Agent Mode returning “Rate limit exceeded” errorsBetween 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. | -87 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Warp incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Warp Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Warp acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Warp outage in this window ran 7h 26m, against a mean recovery of 2h 56m. If you depend on Warp in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.