outages.live
Live

Augment Code

Augment Code is operational

Checked Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Augment Code status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Augment Code since . The days before that show only what Augment Code published.

Incidents in 90 days

4

Days with an incident

4

Median duration

1 h 19 min

Longest incident

5 h 36 min

Components

3
Cosmos Operational
90 days ago4 days with an incidentToday
Customer Dashboard Operational
90 days ago2 days with an incidentToday
API Operational
90 days ago2 days with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 9, 2026

Duration5 h 36 min to Major Outage — Services UnavailableNotice

We 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.

Sep 1, 2026

Duration39 min to Major outage - Cosmos & CLI unavailableMajor outage

This incident has been resolved.

Aug 27, 2026

Duration1 h 58 min to Cosmos session terminal tab doesn't render correctly for some usersDegraded

We have deployed a fix to prod and confirmed that Terminal inside sessions work as expected.

Aug 21, 2026

Duration30 min to Augment service is experiencing higher rate of 500Partial outage

# 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.

Follow Augment Code

Your coding agent knows when Augment Code is down, and tells you when a failure is theirs, not yours. You can also get Augment Code incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "augment" and tell me if Augment Code has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=augment
Slack
/feed subscribe https://outages.live/feed.xml?providers=augment

Go from tracking outages to fixing production issues with Polylane.

Try Polylane