Live / Incidents / Augment Code
Augment Code: Augment service is experiencing higher rate of 500
Augment Code · augmentcode.comImpact: majorResolved2026-08-26 21:31 UTC
Public — what happened
Summary
# Service Disruption on August 21 — What Happened
On August 21, between 12:12 and 13:40 PDT, some customers experienced failed Chat and Agent requests. A routine software update exposed a dormant bug in how certain conversation histories were processed, causing roughly 12% of conversations to return errors; new conversations were largely unaffected. We rolled back the update within the hour and deployed a permanent fix the same day.
Our internal review identified where our safeguards fell short, and our team is already putting in place a combination of agentic, programmatic, and human safeguards to ensure an issue like this cannot reach customers again.
We're sorry for the disrup
Timeline
- Started — 2026-08-21 20:15 UTC
- Last update — 2026-08-26 21:31 UTC
- Resolved — 2026-08-21 20:45 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Augment Code against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Augment Code: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Augment Code report →