Is Amp down? › Outage history › Sep 1, 2026

Amp outage on Sep 1, 2026: what happened

On Sep 1, 2026, the Amp status page reported "Amp unavailable due to Google Cloud incident". About 3 hours 38 min: from Sep 1, 2026, 14:49 UTC to Sep 1, 2026, 18:27 UTC, by the official start and resolution times.

Started

Sep 1, 2026, 14:49 UTC

Resolved

Sep 1, 2026, 18:27 UTC

Duration

3 hours 38 min

Official impact

Critical

Source

Amp unavailable due to Google Cloud incident on the Amp status page

The Amp status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness.

What caused the Amp outage?

"Additional issue is that storage disks have been malformed due to the outage and can't be used."

From the Amp status page, Sep 1, 2026, 16:13 UTC.

When was it fixed?

The Amp status page marked it resolved at Sep 1, 2026, 18:27 UTC, 3 hours 38 min after it started. A fix was in place and being monitored from Sep 1, 2026, 18:05 UTC. Its resolution note: "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 ..."

Timeline of official updates

Every update the Amp status page posted, oldest first. Times are UTC.

1. Sep 1, 2026, 14:49 UTC investigating

   We're seeing elevated error rates when creating to new threads. We're looking into it

2. Sep 1, 2026, 15:26 UTC investigating

   Google Cloud reports connectivity issues between VMs, which results in us not being able to scale resources up/down as necessary.

3. Sep 1, 2026, 16:13 UTC investigating

   Google Cloud has now officially opened an incident: [https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "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.

4. Sep 1, 2026, 17:12 UTC 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.

5. Sep 1, 2026, 18:05 UTC monitoring

   Availability is restored. We're adding back capacity and monitoring.

6. Sep 1, 2026, 18:27 UTC 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.

Amp outage questions

Other recent Amp incidents

• Thread creation and agent failures Oct 21, 2026, 22:35 UTC, 17 minutes
• Inference requests failing Oct 21, 2026, 16:38 UTC, 28 minutes
• Thread creation and agent failures Oct 21, 2026, 12:07 UTC, 23 minutes
• Slow loading on ampcode.com Oct 6, 2026, 15:55 UTC, 4 hours 6 min
• Agents fail to start for some threads Oct 1, 2026, 03:27 UTC, 32 minutes
• ChatGPT subscriptions failing Sep 25, 2026, 23:00 UTC, 1 hour 26 min

Full Amp outage history and biggest outages → · Recent outages across all services →

Quotes are the Amp status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with Amp. Times are UTC.