Augment Code Outage History

26 incidents recorded over the last 365 days, 26 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Augment Code status99.35% uptime history

Every Recorded Augment Code Incident

Augment Code incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 9, 2026Major Outage — Services UnavailableWe have successfully brought back all the services. We’ll be doing a detailed postmortem to better understand what caused the issue so that we can prevent this in the future.5h 36mResolved
Sep 1, 2026Major outage - Cosmos & CLI unavailableThis incident has been resolved.39 minResolved
Aug 27, 2026Cosmos session terminal tab doesn't render correctly for some usersWe have deployed a fix to prod and confirmed that Terminal inside sessions work as expected.1h 58mResolved
Aug 26, 2026Elevated levels of 429 errors on Cosmos for ~7 hoursBetween roughly 8/25 6PM to 8/26 2AM Pacific Time, some users were not able to access or use Cosmos due to seeing the 429 - Too Many Requests error. It was because of a bug that got deployed into production that called…-1098 minResolved
Aug 21, 2026Augment service is experiencing higher rate of 500# 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…30 minResolved
Aug 19, 2026MCP service disruptionWe observed Cosmos agent MCP calls failing with 401 errors.-155 minResolved
May 14, 2026Service disruptionThis incident has been resolved.48 minResolved
May 8, 2026Upstream Cosmos environment provider incidentThis incident has been resolved.2h 27mResolved
Apr 29, 2026Code review service disruptionThis incident has been resolved.6h 37mResolved
Apr 6, 2026Code Review service disruptionThis incident has been resolved.5h 39mResolved
Mar 27, 2026All services degradedThis incident has been resolved.5 minResolved
Mar 24, 2026Calls to Augment's public API failed for 20mins - all services impacted60+% of calls to Augment's public API failed for 20 minutes between 3pm and 3:20pm PT. All services were impacted.0 minResolved
Mar 16, 2026Service disruption affecting Sonnet 4.5This incident has been resolved.12 minResolved
Mar 7, 2026Billing 39760This incident has been resolved.10h 1mResolved
Mar 5, 2026Slackbot service disruptionThis incident has been resolved.20h 50mResolved
Mar 4, 2026OpenAI models & Code Review service disruptionThis incident has been resolved.3h 8mResolved
Jan 6, 2026Partial outage impacting completions and next edits for some usersThis incident has been resolved.1h 14mResolved
Dec 29, 2025Customer UI partial outageThis incident has been resolved.2h 59mResolved
Dec 23, 2025Investigating degraded performance on chatWe believe this issue to be resolved. Chat latencies and error rates are back within normal range. Team will investigate into root cause for the spike.12h 8mResolved
Dec 16, 2025High error rate for OpenAI (GPT5.* models)This incident has been resolved.3h 56mResolved
Dec 9, 2025Slackbot unresponsiveThis incident has been resolved.7h 7mResolved
Nov 24, 2025Chat/Agent Chat requests are failingThis incident has been resolved.1h 55mResolved
Nov 24, 2025Chat/Agent Chat requests are failingElevated error rates for chat and agent chat requests.-235 minResolved
Nov 18, 2025Remote agent and code review service disruptionThis incident has been resolved.31 minResolved
Nov 11, 2025Some users experiencing errors while retrieving account information.This incident has been resolved.3h 32mResolved
Nov 10, 2025A delay in indexing newly uploaded files is affecting a small portion of self-serve customers.This incident has been resolved.1h 5mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Augment Code incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Augment Code Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Augment Code acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Augment Code outage in this window ran 20h 50m, against a mean recovery of 4h 3m. If you depend on Augment Code in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.