outages.live
Live
Augment CodeIncident ·

Major outage - Cosmos & CLI unavailable

ResolvedOfficial update

This incident has been resolved.

The latest update from Augment Code.

State

Resolved

Started

Lasted

39 min

Worst impact

Major outage

Timeline

4 updates
15:1515:2515:3515:4415:54
Major outageUpdate postedTimes in UTC

Investigating

39 min 100%

Updates

Times in UTC

As posted by Augment Code

Resolved

This incident has been resolved.

Investigating

Google Cloud is experiencing elevated networking issues: Intra region VM to VM communication through an external IP address is experiencing high packet loss. We are working closely with Google for resolution.

Investigating

We're experiencing a major outage affecting Cosmos and CLI. We're actively investigating and will post an update by 9am PT.

Investigating

We are currently investigating this issue.

Affected components

3
CosmosCustomer DashboardAPI

Augment Code in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

4

Median duration

1 h 19 min

This incident

50% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

5 h 36 min
median 1 h 19 min
90 days agoToday

Other Augment Code incidents

All incidents

Augment Code·Major Outage — Services Unavailable

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.

Resolved

Augment Code·Cosmos session terminal tab doesn't render correctly for some users

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

Resolved

Augment Code·Augment 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 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.

Resolved

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane