Is Amp down right now?
No, it is up
Operational · All systems operational
Components
All 25 components operational.
Show all 25 components
- Amp AgentOperational
- ampcode.comOperational
- Payment ProcessingOperational
- Inference Providers · OpenAIOperational
- Inference Providers · AnthropicOperational
- Inference Providers · Gemini Enterprise Agent PlatformOperational
- Authentication · WorkOS AuthKitOperational
- Authentication · WorkOS SSOOperational
- Authentication · WorkOS Directory SyncOperational
- Authentication · WorkOS Admin PortalOperational
- Core Infrastructure · Cloudflare DNS Root ServersOperational
- Core Infrastructure · Cloudflare Authoritative DNSOperational
- Core Infrastructure · Cloudflare Secondary DNSOperational
- Core Infrastructure · Google Cloud Platform Google Cloud NetworkingOperational
- Core Infrastructure · Google Cloud Platform Google BigQueryOperational
- Core Infrastructure · Google Cloud Platform Google Cloud SQLOperational
- Core Infrastructure · Google Cloud Platform Google Container EngineOperational
- Internal Infrastructure · GitHub Git OperationsOperational
- Internal Infrastructure · npm Package installationOperational
- Internal Infrastructure · npm Package publishingOperational
- Internal Infrastructure · Google Cloud Platform Identity & Access ManagementOperational
- Product Integrations · GitHub API RequestsOperational
- Product Integrations · GitHub ActionsOperational
- Product Integrations · Slack Apps/Integrations/APIsOperational
- Support · Google Apps GmailOperational
User reports
Having trouble with Amp? Reports are anonymous and only counted, no cookies.
Amp uptime, last 90 days
Each bar is one UTC day, coloured by the worst state we saw on the official status page.
Recent Amp incidents
Claude Code Subscription errors · 27 Oct 2026, 17:42 UTC · 8 min · major
resolved · 27 Oct 2026, 17:50 UTC
We traced this back to some errors on our end which could block creation of new threads. The issue resolved itself, and error rates returned to normal.
investigating · 27 Oct 2026, 17:42 UTC
We're seeing high error rates for Claude Code subscription usage. Looking into it
Some threads are stuck in reconnecting · 23 Oct 2026, 19:02 UTC · 9 min · major
resolved · 23 Oct 2026, 19:11 UTC
Threads are reconnecting and starting successfully again.
investigating · 23 Oct 2026, 19:02 UTC
A portion of threads are stuck in reconnecting status or failing to start.
Slowness on ampcode.com and clients · 22 Oct 2026, 15:26 UTC · 1 h 51 min · minor
resolved · 22 Oct 2026, 17:16 UTC
We fixed shed load from the database, it's now in a healthier state. We also ran into an issue with an upstream provider and received a patch from them that we'll apply to avoid the problem in the future.
monitoring · 22 Oct 2026, 16:37 UTC
We managed to shed load (we identified a user's plugin causing a lot of load without being rate limited; fixing) and optimized queries. The database performance is back to normal.
identified · 22 Oct 2026, 16:09 UTC
We identified a bad query that creates unexpected high load on the database. Reverting.
identified · 22 Oct 2026, 15:47 UTC
We're hitting some resource limits from increased load on our database, but need to wait for compute so we can resize. Shedding load right now. Clients (macOS, iOS, TUI) and [ampcode.com](http://ampcode.com "ampcode.com") might be slow.
identified · 22 Oct 2026, 15:26 UTC
We're hitting some resource limits from increased load, so some users are seeing period slowness when loading [ampcode.com](http://ampcode.com "ampcode.com"). We're working on scaling up, will keep you updated.
Thread creation and agent failures · 21 Oct 2026, 22:35 UTC · 17 min · major
resolved · 21 Oct 2026, 22:52 UTC
The issues are resolved. We're continuing to root-cause the incidents today, which are related. Most threads were unaffected during this outage, but affected threads could have taken ~2-3min to reconnect.
investigating · 21 Oct 2026, 22:41 UTC
We are seeing agents take 5-20 seconds to connect.
investigating · 21 Oct 2026, 22:35 UTC
We are seeing some agents and threads be unable to connect.
Inference requests failing · 21 Oct 2026, 16:38 UTC · 28 min · minor
resolved · 21 Oct 2026, 17:06 UTC
One our storage nodes saturated and was not replaced fast enough to keep up with ongoing traffic. We have identified the issue and mitigated it. We are working on a fix to prevent this in the future.
investigating · 21 Oct 2026, 16:38 UTC
Inference requests are failing intermittently. We're investigating.
Thread creation and agent failures · 21 Oct 2026, 12:07 UTC · 23 min · critical
resolved · 21 Oct 2026, 12:29 UTC
Creating threads and running inference is now working as expected
identified · 21 Oct 2026, 12:13 UTC
We've identified the issue and are deploying a fix. Creating new threads and sending thread messages are returning errors.
investigating · 21 Oct 2026, 12:07 UTC
We're investigating an issue creating new threads or processing thread messages
Slow loading on ampcode.com · 6 Oct 2026, 15:55 UTC · 4 h 6 min
resolved · 6 Oct 2026, 20:02 UTC
We've resolved the increased load, and latencies are back down to normal levels. Apologies if you saw some slowdowns!
investigating · 6 Oct 2026, 15:55 UTC
We're seeing some degraded performance on [ampcode.com](http://ampcode.com "ampcode.com"). We are seeing intermittent timeouts when loading pages and threads.
Agents fail to start for some threads · 1 Oct 2026, 03:27 UTC · 32 min · major
resolved · 1 Oct 2026, 04:00 UTC
This issue is resolved.
monitoring · 1 Oct 2026, 03:49 UTC
Some CPU metrics remain above the ideal range, but we are seeing a broad recovery. The impact of this incident was limited to a small number of threads and caused agent unavailability of up to a few minutes. We are still monitoring the metrics.
investigating · 1 Oct 2026, 03:27 UTC
We're seeing some agents fail to start or reconnect for some threads. Thread data is still loading. Only a subset of threads are affected. We are seeing high CPU usage on some nodes during a deploy that we believe to be causing this.
ChatGPT subscriptions failing · 25 Sept 2026, 23:00 UTC · 1 h 26 min · major
resolved · 26 Sept 2026, 00:26 UTC
OpenAI has resolved the Codex outage
identified · 25 Sept 2026, 23:07 UTC
OpenAI has updated their status page now, so you can find the most up-to-date info there: [https://status.openai.com/incidents/01M3DCNWMW57HYK8FJ5FBFPA39](https://status.openai.com/incidents/01M3DCNWMW57HYK8FJ5FBFPA39 "https://status.openai.com/incidents/01M3DCNWMW57HYK8FJ5FBFPA39")
identified · 25 Sept 2026, 23:04 UTC
Small update: it appears that API traffic is unaffected, so if you disable your ChatGPT sub, you can fall back to using Amp credits to continue your orbin'
identified · 25 Sept 2026, 23:00 UTC
Using OpenAI models through a ChatGPT subscription is failing with websocket errors. This appears to be an upstream issue. We will update once it's confirmed by OpenAI
Orbs are failing to start · 24 Sept 2026, 07:59 UTC · 45 min · major
resolved · 24 Sept 2026, 08:44 UTC
Orbs and threads are working again.
monitoring · 24 Sept 2026, 08:38 UTC
During the rollback, some other non-orb threads started to experience higher error rates due to high load in the rollback.
monitoring · 24 Sept 2026, 08:04 UTC
We have identified the problem and are rolling back the problematic deployment that is preventing new orbs from being created.
investigating · 24 Sept 2026, 07:59 UTC
We are seeing a higher failure rate for orbs when starting up. Existing orbs appear to be unaffected.
Amp won't load when logged in · 18 Sept 2026, 22:54 UTC · 18 min · major
resolved · 18 Sept 2026, 23:12 UTC
Our authentication provider has recovered service.
monitoring · 18 Sept 2026, 23:09 UTC
Authentication is working again, we are continuing to monitor availability
monitoring · 18 Sept 2026, 22:59 UTC
Authentication is working again, we are continuing to monitor availability
identified · 18 Sept 2026, 22:54 UTC
Our authentication provider (WorkOS) is down which is preventing logged in sessions from connecting.
Some threads are unavailable on the web · 9 Sept 2026, 21:37 UTC · 43 min · major
resolved · 9 Sept 2026, 22:20 UTC
We've confirmed the issue is resolved and has been for the last 25 minutes.
monitoring · 9 Sept 2026, 21:56 UTC
We have rolled back the problematic web change, and threads on the web are loading again.
identified · 9 Sept 2026, 21:51 UTC
Many threads are unavailable on the web. The Amp CLI is still working.
investigating · 9 Sept 2026, 21:37 UTC
During a deployment, there is an issue where some threads are temporarily unable to be interacted with.
Thread creation and connection failures · 8 Sept 2026, 11:18 UTC · 42 min · critical
resolved · 8 Sept 2026, 14:55 UTC
This morning's incident left 369 user connections to threads in a degraded state. They are now restored and working.
investigating · 8 Sept 2026, 14:31 UTC
We are experiencing database issues again and are investigating.
resolved · 8 Sept 2026, 12:33 UTC
Fully recovered, monitoring, and rolling out fixes for the problems we found
monitoring · 8 Sept 2026, 12:12 UTC
Updating the priority classes for our storage nodes lead to a re-deployment at the same time as another deployment was going on. We're disabling auto-deployments now while incidents are going on.
investigating · 8 Sept 2026, 12:05 UTC
Some threads fail to connect sporadically
resolved · 8 Sept 2026, 12:01 UTC
Database recovered, limits adjusted. What we're going to do: • Audit all of our resource priority classes • Introduce more spare capacity for storage nodes so that we don't have to wait for new nodes to come online • Revise alerts so it's faster than 5min for us to pinpoint where the failure comes from
monitoring · 8 Sept 2026, 11:41 UTC
**Prometheus autoscaling caused database pod eviction** A Google managed Prometheus collector autoscaler increased the collectors’ resource requests and restarted collectors across the cluster. The collector pods had a wrongly configured too-high priority, higher than our FoundationDB storage pods. Kubernetes preempted FoundationDB pods to make room for the collectors. Replacement storage pods then had to wait for new nodes compatible with their storage and compute requirements. This took long enough for FoundationDB to begin data recovery, which extended the outage. The service recovered and was fully available again after about 20 minutes. We are changing the scheduling and capacity configuration so that monitoring workloads cannot evict database storage pods again.
monitoring · 8 Sept 2026, 11:30 UTC
Thread error rates are back to normal, and we'll continue to monitor.
Thread creation and connection failures · 6 Sept 2026, 16:22 UTC · 6 h 10 min · major
resolved · 6 Sept 2026, 22:32 UTC
We have been at zero errors/failures for 3 hours now. We will continue to monitor it and will be shipping longer-term improvements over the next few hours to prevent this from happening again.
monitoring · 6 Sept 2026, 20:16 UTC
The mitigation is working and errors/delays are still at zero. We are continuing to monitor it and will deploy the longer-term fix soon.
monitoring · 6 Sept 2026, 19:48 UTC
We've found the issue and failures are down to zero right now, but we are still working on a more permanent fix. For the last few hours roughly 5-10% of thread creations and reconnects were failing.
investigating · 6 Sept 2026, 16:22 UTC
We're seeing elevated error rates and delays when creating and connecting to threads.
Slow to connect to threads · 5 Sept 2026, 17:24 UTC · 31 min · minor
resolved · 5 Sept 2026, 17:55 UTC
A confluence of a few different deploys caused our load balancers started misbehaving and overloading a few of our servers. We've adjusted the balancing so if you saw threads failing, they should all be healthy now.
investigating · 5 Sept 2026, 17:24 UTC
We're seeing general performance degradation across most thread operations.
Amp is listed under Dev tools. Status data comes from the official status page and is checked every 5 minutes.All AI service statuses