Resolved incident

Augment service is experiencing higher rate of 500

Augment Code · Major · Started

Duration
30m
Severity
Major
Status
Postmortem

Summary

Major · Postmortem

# 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 disruption, and we thank the customers who reported the issue. Please reach out to your account contact or support if you have questions.

View official incident ↗

Event timeline

How this incident unfolded, from the official status page.

  1. Identified

    Augment Code

    We have identified an issue that causing an elevated rate of 500s errors in all Augment agent surfaces, including Cosmos, CLI, and IDE extensions. The issue started around 12:15pm PDT today. We are working on mitigating the issue.

  2. Monitoring

    Augment Code

    A fix has been deployed and issues should stop happening. We are seeing recovery of error rates.

  3. Resolved

    Augment Code

    This incident has been resolved.

  4. Postmortem

    Augment Code

    # 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 disruption, and we thank the customers who reported the issue. Please reach out to your account contact or support if you have questions.