pingoru pingoru Amp Code had 27 outages in the last 2 years totaling 41h 33m of downtime, averaging 1.1 incidents per month.
There were 27 Amp Code outages since July 23, 2026 totaling 41h 33m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Status: Investigating We're seeing some degraded performance on ampcode.com "ampcode.com": http://ampcode.com. We are seeing intermittent timeouts when loading pages and threads.
Status: Resolved We've resolved the increased load, and latencies are back down to normal levels. Apologies if you saw some slowdowns!
Status: Investigating 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. Affected components Amp Agent (Partial outage)
Status: Monitoring 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. Affected components Amp Agent (Operational)
Status: Resolved This issue is resolved. Affected components Amp Agent (Operational)
Status: Identified 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 Affected components OpenAI (Partial outage)
Status: Identified 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' Affected components OpenAI (Partial outage)
Status: Identified OpenAI has updated their status page now, so you can find the most up-to-date info there: https://status.openai.com/incidents/01M3DCNWMW57HYK8FJ5FBFPA39 Affected components OpenAI (Partial outage)
Status: Resolved OpenAI has resolved the Codex outage Affected components OpenAI (Operational)
Status: Investigating We are seeing a higher failure rate for orbs when starting up. Existing orbs appear to be unaffected. Affected components Amp Agent (Degraded performance)
Status: Monitoring We have identified the problem and are rolling back the problematic deployment that is preventing new orbs from being created. Affected components Amp Agent (Partial outage)
Status: Monitoring During the rollback, some other non-orb threads started to experience higher error rates due to high load in the rollback. Affected components Amp Agent (Partial outage)
Status: Resolved Orbs and threads are working again. Affected components Amp Agent (Operational)
Status: Identified Our authentication provider (WorkOS) is down which is preventing logged in sessions from connecting.
Status: Monitoring Authentication is working again, we are continuing to monitor availability
Status: Monitoring Authentication is working again, we are continuing to monitor availability Affected components WorkOS AuthKit (Partial outage) WorkOS Admin Portal (Partial outage) WorkOS Directory Sync (Partial outage) WorkOS SSO (Partial outage)
Status: Resolved Our authentication provider has recovered service. Affected components WorkOS AuthKit (Operational) WorkOS Admin Portal (Operational) WorkOS Directory Sync (Operational) WorkOS SSO (Operational)
Status: Investigating During a deployment, there is an issue where some threads are temporarily unable to be interacted with. Affected components Amp Agent (Partial outage)
Status: Identified Many threads are unavailable on the web. The Amp CLI is still working. Affected components Amp Agent (Partial outage)
Status: Monitoring We have rolled back the problematic web change, and threads on the web are loading again. Affected components Amp Agent (Operational)
Status: Resolved We've confirmed the issue is resolved and has been for the last 25 minutes. Affected components Amp Agent (Operational)
Status: Investigating We're seeing general performance degradation across most thread operations. Affected components Amp Agent (Degraded performance)
Status: Resolved 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. Affected components Amp Agent (Operational)
Status: Investigating We're seeing elevated error rates when creating and resuming threads. Will update as soon as we have more information.
Status: Resolved We had a deployment out with a bug that caused our server to crash in some situations, causing intermittent errors while using amp. We've rolled back and the errors have dropped to zero. Sorry for the noise! Affected components Amp Agent (Operational)
Status: Identified Using ChatGPT subscriptions in Amp is failing due to an upstream incident. Follow https://status.openai.com/ for updates Affected components OpenAI (Partial outage)
Status: Resolved OpenAI has resolved their incident, and ChatGPT subs appear to be working well again. Affected components OpenAI (Operational)
Status: Investigating Orbs are seeing a higher error rate when starting. Affected components Amp Agent (Degraded performance)
Status: Monitoring Orb start and resume rates have returned to normal, and we're continuing to monitor. Affected components Amp Agent (Operational)
Status: Resolved Orb creation rates have fully stabilised, and all systems are normal. We're sorry for the interruption, and we'll continue to investigate ways to make Amp more resilient to this going forward. Affected components Amp Agent (Operational)
Status: Investigating We're seeing elevated error rates when creating to new threads. We're looking into it
Status: Investigating Google Cloud reports connectivity issues between VMs, which results in us not being able to scale resources up/down as necessary.
Status: Investigating Google Cloud has now officially opened an incident: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev We're in the process of recovering from our lost nodes. In order to prevent data loss, the recovering takes precedence over availability. We hope the recovery will finish soon, once Google Cloud has stabilized. Additional issue is that storage disks have been malformed due to the outage and can't be used.
Status: Identified The issues we observed related to the GCP outage appear to be resolved, but our services are still recovering. We're currently working on restoring full data replication, which we estimate will complete around 11am PT, at which point service should be fully restored. Affected components Amp Agent (Full outage)
Status: Monitoring Availability is restored. We're adding back capacity and monitoring. Affected components Amp Agent (Operational)
Status: Resolved Service is fully restored, and all our systems have stabilized. We know outages like this hurt, and we have work in progress that will mean we're more resilient when faced with infrastructure instability like this. Unfortunately, this incident hit before that work was complete. Sorry again for the downtime. We'll do better next time. Affected components Amp Agent (Operational)
Status: Investigating ampcode.com "ampcode.com": http://ampcode.com and the native app are returning 500 errors for some users. Still investigating, but will update soon
Status: Resolved The browser application was crashing with a 500 error after page load. We've rolled back the change and a hard refresh should fix any remaining issues.
Status: Investigating The Amp application and API are unreachable.
Status: Identified We have found the cause and are rolling back to a good version. Amp is partially available again.
Status: Resolved We found the source of the issue (a very inefficient PostgreSQL query) and have rolled back and have deployed a fix for future deploys.
Status: Investigating We are seeing elevated error rates from OpenAI for requests using OpenAI-backed models (e.g. GPT-5.x). Affected requests fail with "Invalid prompt: your prompt was flagged as potentially violating our usage policy", even for normal coding prompts. This is an upstream issue with OpenAI's API, and we are in contact with them. Other models are unaffected. Retrying may succeed, or you can switch to a non-OpenAI model in the meantime.
Status: Monitoring Error rates from OpenAI have started recovering and requests are succeeding again. We are monitoring error rates to confirm full recovery before resolving this incident.
Status: Resolved OpenAI requests are completing successfully again. We're still working with OpenAI to identify the underlying cause of the prompt-flagging errors. Affected components OpenAI (Operational)
Status: Identified A recent change to the Orb base image lead to Orbs not starting up for fresh instances. We're rolling it back.
Status: Identified We've identified the issue, rolled out a fix, and are now restarting all Orbs that previously failed to start.
Status: Monitoring Restarting failed orbs and watching them restart.
Status: Resolved Orbs that were created in a ~1hr window failed to start up. We restarted them. No data was lost. After a fix rolled out, new orbs would start up without problems.
Status: Investigating ampcode.com "ampcode.com": http://ampcode.com, the CLI, and the API are all unreachable. Affected components Amp Agent (Full outage)
Status: Investigating Creating and using threads is working again but is very slow. The API is available. We are investigating. Affected components Amp Agent (Degraded performance)
Status: Investigating We are seeing the error rate increase even from the Amp CLI now. Affected components Amp Agent (Partial outage)
Status: Resolved We found the source of the high load on our database and have resolved the issue. Affected components Amp Agent (Operational)
Status: Investigating Thread creation is taking up to 60 seconds and archiving and other operations are slow.
Status: Monitoring We have rolled out a fix and error rates are declining rapidly.
Status: Resolved This issue has been resolved.
Status: Identified A deploy went out with a poorly shaped query plan for listing threads, which is adding large amounts of load to the DB and slowing down many operations. We've rolled back that deploy and should be back soon.
Status: Resolved We've rolled back the bad change and everything is healthy again. Sorry for the blip.
Status: Investigating Executors are failing to start for new orbs
Status: Monitoring The underlying issue has ben resolved and new orbs are starting successfully again. Some existing orbs affected by this incident are still stuck, and we are working on resolution for these.
Status: Monitoring New and existing orbs are in a healthy state. There is a small set of existing threads still in an unhealthy state.
Status: Resolved All new orbs are operational.
Status: Investigating A fraction of Amp runners are not able to connect to our servers. We are investigating the issue.
Status: Monitoring We've run our repair for all impacted users, so creating threads on runners is now working for everyone. There are still a few threads from the incident that are left in bad state, so we are shifting our focus to repairing those.
Status: Resolved We've repaired all the threads which were unable to connect because of this incident, so all known issues have been resolved. Thanks for your patience!
Status: Investigating Thread creation and connection is failing Affected components Amp Agent (Full outage)
Status: Monitoring We ran into some GCE capacity issues which meant that a routine node update was suddenly not routine. Thread creation is working again, but you may still notice some slowness as we fully recover. Affected components Amp Agent (Full outage)
Status: Resolved Service has stabilized for new threads. We are still investigating some reports of threads which experienced errors during the incident staying stuck. Affected components Amp Agent (Operational)
Status: Investigating We are currently investigating an outage in our infrastructure, which makes thread creation slow or causes time out.
Status: Monitoring We have identified the cause. A bug in undici, the HTTP library bundled with Node.js, prevented new outgoing requests from being dispatched while a long-lived streaming request was open on the same HTTP/2 connection. Under high load, new requests queued behind those streams and timed out. We deployed Node.js 26.5.1, which includes the upstream undici fix. Thread creation has been stable since the deploy. We are continuing to monitor and will post another update once we are confident the issue is resolved.
Status: Resolved A bug in undici, the HTTP library bundled with Node.js, prevented new outgoing requests from being dispatched while a long-lived streaming request was open on the same HTTP/2 connection. Under high load, new requests queued behind those streams and timed out. We deployed Node.js 26.5.1, which includes the upstream undici fix. Thread creation has been stable since the deploy.
Status: Investigating Threads are failing to connect to Amp server
Status: Investigating New and existing threads are failing to connect to Amp Server
Status: Investigating New and existing threads are failing to connect to the Amp server
Status: Resolved Threads are connecting now.
Status: Resolved Threads are connecting again.
Status: Monitoring Some threads are failing to connect.
Status: Resolved Threads are now connecting normally.
Status: Investigating Some users are seeing an issue where active threads are not appearing in the thread sidebar
Status: Identified We've identified and fixed the primary bug, so threads should be visible in your sidebar again. We are still working on fixing a few related bugs with archiving and pinning threads, will update soon.
Status: Monitoring Archiving, pinning, and the activity feed are now working correctly. We'll continue to monitor to ensure no further degradation.
Status: Resolved All features working correctly now