Augment Code

Affected: Cosmos, Customer Dashboard, API

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 14:30 UTC

   We are currently investigating an issue that's impacting multiple services.

2. identified 2026-10-09 16:26 UTC

   We’ve identified the issue impacting service availability and are actively working with our cloud partners to resolve it. The issue is related to permissions following a recent infrastructure migration. We’ll share another update as soon as we have more information.

3. identified 2026-10-09 16:51 UTC

   Availability of Cosmos and our core API has improved. Some features remain affected, and we're continuing to work on restoring them. We'll share another update as recovery progresses.

4. identified 2026-10-09 17:45 UTC

   Cosmos and Core API services are mostly resolved. We are continuing to restore the remaining services. We'll share another update as recovery progresses.

5. resolved 2026-10-09 20:06 UTC

   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.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Cosmos, Customer Dashboard, API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. investigating 2026-09-01 15:15 UTC

   We are currently investigating this issue.

2. investigating 2026-09-01 15:19 UTC

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

3. investigating 2026-09-01 15:36 UTC

   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.

4. resolved 2026-09-01 15:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Cosmos

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-27 18:41 UTC

   We have discovered that Cosmos session terminal tab doesn't render and work correctly for some users. Agent sessions still function correctly. We are looking into the root cause and fix.

2. resolved 2026-08-27 20:40 UTC

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

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-08-26 01:00 UTC

   Between 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 an endpoint recursively. At around 1:30AM PT, we deployed...

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Cosmos

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-21 20:15 UTC

   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 2026-08-21 20:39 UTC

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

3. resolved 2026-08-21 20:45 UTC

   This incident has been resolved.

4. postmortem 2026-08-26 21:31 UTC

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

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-19 16:15 UTC

   We observed Cosmos agent MCP calls failing with 401 errors.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-14 22:23 UTC

   We're investigating elevated error rates.

2. monitoring 2026-05-14 22:58 UTC

   Error rates have recovered and we're continuing to monitor.

3. resolved 2026-05-14 23:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-08 00:36 UTC

   We are currently investigating an issue with our upstream provider failing to start Cosmos environments

2. identified 2026-05-08 00:44 UTC

   The provider has acknowledged that they are having a problem and are working on mitigating the incident.

3. identified 2026-05-08 01:21 UTC

   Our provider is continuing to work on their mitigation. We will update the status as progress is made.

4. monitoring 2026-05-08 02:36 UTC

   The provider has put in mitigations and services are returning to normal. We'll continue monitoring Cosmos as agents come back online.

5. resolved 2026-05-08 03:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-29 11:00 UTC

   We are currently investigating an issue with Code Review.

2. resolved 2026-04-29 17:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-06 16:50 UTC

   We've identified an issue with Code Review and are investigating problems posting review comments.

2. identified 2026-04-06 18:38 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-04-06 22:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Customer Dashboard, API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-27 16:22 UTC

   High error rates across all endpoints (impact began at 8:55am PT)

2. identified 2026-03-27 16:23 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2026-03-27 16:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-03-24 22:00 UTC

   60+% of calls to Augment's public API failed for 20 minutes between 3pm and 3:20pm PT. All services were impacted.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-16 16:57 UTC

   We're investigating reports of elevated error rates using the Sonnet 4.5 model.

2. resolved 2026-03-16 17:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Customer Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-07 08:14 UTC

   Investigating — Billing / Subscription Activation Issues We are currently investigating an issue affecting billing. Some customers who upgrade to a paid plan may experience delays in their subscription being activated. In these cases, access to paid features may not be available...

2. identified 2026-03-07 08:16 UTC

   We have identified the cause of the billing issue affecting subscription activation. The problem is related to a third-party vendor, and we are actively working with the vendor to restore normal operation as quickly as possible.

3. resolved 2026-03-07 18:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-03-05 19:47 UTC

   We've identified a problem with the Augment Slackbot due to a Slack incident.

2. monitoring 2026-03-05 22:08 UTC

   The Slackbot is recovering and we're continuing to monitor the related Slack incident.

3. monitoring 2026-03-05 22:08 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-03-06 16:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. investigating 2026-03-04 19:30 UTC

   OpenAI models and Augment Code Review are currently unavailable. We're investigating the problem.

2. identified 2026-03-04 21:31 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-03-04 22:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-06 14:45 UTC

   We are currently investigating this issue.

2. resolved 2026-01-06 15:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Customer Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-29 17:30 UTC

   We are currently investigating this issue.

2. resolved 2025-12-29 20:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-23 06:00 UTC

   We are currently investigating this issue.

2. monitoring 2025-12-23 17:39 UTC

   Scaled up chat hosts around 5:40am on 12/22 to address elevated latencies and errors that impacted a segment of customers. Latencies and errors have reduced to prior baseline and the team is actively monitoring and investigating root cause.

3. resolved 2025-12-23 18:09 UTC

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

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. identified 2025-12-16 20:57 UTC

   We are seeing high error rate for OpenAI GPT5.* models, likely due to upstream model provider errors. Current mitigation is to switch to a non-OpenAI model.

2. monitoring 2025-12-16 23:06 UTC

   We don't see elevated error rates and are monitoring.

3. resolved 2025-12-17 00:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-12-09 17:11 UTC

   We've identified an issue with the Augment Slackbot and are working on restoring service.

2. monitoring 2025-12-09 19:00 UTC

   We believe issue this to be resolved and are monitoring.

3. resolved 2025-12-10 00:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-24 19:03 UTC

   Chat and agent chat requests are failing

2. monitoring 2025-11-24 19:39 UTC

   We are continuing to investigate and resolve a small amount of errors.

3. resolved 2025-11-24 20:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-11-24 15:00 UTC

   Elevated error rates for chat and agent chat requests.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2025-11-18 21:29 UTC

   We're investigating problems starting remote agents and completing code reviews, due to a GitHub outage.

2. monitoring 2025-11-18 21:54 UTC

   Remote agents and code review are recovering. We're continuing to monitor these systems.

3. resolved 2025-11-18 22:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Customer Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-11 13:25 UTC

   We are investigating this issue. Non-administrative service operations are not currently impacted.

2. investigating 2025-11-11 14:07 UTC

   We continue to investigate upstream failures on account information retrieval for self-serve customers.

3. identified 2025-11-11 16:54 UTC

   We've identified the problem and are implementing mitigation.

4. resolved 2025-11-11 16:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-10 18:25 UTC

   A delay in indexing newly uploaded files is affecting a small portion of self-serve customers. The team is investigating.

2. identified 2025-11-10 19:01 UTC

   Mitigation steps have been implemented. The indexing backlog is being processed, and we expect operations to return to normal within the next hour or so.

3. resolved 2025-11-10 19:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-04 16:47 UTC

   We are currently investigating reports of possible Haiku degradation and will post updates as we have them.

2. investigating 2025-11-04 19:18 UTC

   We believe the Haiku degradation to be resolved but are actively verifying

3. resolved 2025-11-04 20:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. investigating 2025-10-28 16:31 UTC

   Anthropic is reporting elevated error rates for requests to Claude 4.5 Haiku. Please follow status updates here: https://status.claude.com/incidents/bbk3s953nzvd

2. investigating 2025-10-28 16:45 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-10-28 17:18 UTC

   We believe Anthropic has a fix. We are monitoring the results.

4. resolved 2025-10-28 17:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-10-20 20:52 UTC

   Some customers are experiencing elevated error rates. We are working to resolve the problem and restore normal service to those impacted.

2. resolved 2025-10-21 00:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Customer Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 16:21 UTC

   We are investigation an issue on the customer portal w.r.t. to account management operations

2. investigating 2025-10-20 16:22 UTC

   We are continuing to investigate this issue.

3. identified 2025-10-20 16:24 UTC

   The issue as been identified. The root cause are increased error rates in a downstream metering and billing provider likely indirectly caused by issues in the AWS us-east-1

4. resolved 2025-10-20 18:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Customer Dashboard

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-17 16:25 UTC

   We are currently investigating the issue.

2. identified 2025-10-17 16:28 UTC

   The issue has been identified and a fix is being prepared.

3. monitoring 2025-10-17 17:09 UTC

   A fix has been deployed and we are monitoring.

4. resolved 2025-10-17 17:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. identified 2025-10-14 21:08 UTC

   We have identified an issue for the agent to access OpenAI APIs. Fix is in progress.

2. identified 2025-10-14 21:42 UTC

   We are continuing to work on the fix for this issue.

3. monitoring 2025-10-14 22:48 UTC

   A fix has been implemented and we are monitoring.

4. resolved 2025-10-14 22:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-09 00:17 UTC

   Root cause is under investigation

2. investigating 2025-10-09 00:48 UTC

   We are continuing to investigate this issue.

3. resolved 2025-10-09 00:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Customer Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-03 21:12 UTC

   We're investigating an issue with logout and analytics in the customer dashboard.

2. resolved 2025-10-03 21:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-03 02:14 UTC

   We're investigating elevated latency in chat and agent requests.

2. identified 2025-10-03 02:55 UTC

   We've identified an issue with one of our model providers causing elevated latency in chat and agent requests.

3. monitoring 2025-10-03 02:59 UTC

   Latency has returned to normal and we're continuing to monitor system health.

4. resolved 2025-10-03 03:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Customer Dashboard, API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-02 17:03 UTC

   We're investigating reports of a service disruption.

2. identified 2025-10-02 17:15 UTC

   We've identified a problem with customer dashboards and are implementing a fix. Other services are operating normally.

3. monitoring 2025-10-02 17:48 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-10-02 17:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-29 17:18 UTC

   We're currently investigating reports of missing request history. We believe this to be a temporary issue and are working on reverting. Thank you for your patience as we resolve this issue.

2. resolved 2025-09-29 18:28 UTC

   The incident has been resolved by reverting to a previous release.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Customer Dashboard, API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-09-26 09:02 UTC

   We are currently experiencing a major outage affecting multiple services. Our engineering teams are actively working with Google Cloud to diagnose and resolve the issue with the utmost urgency. We will post additional updates here as soon as we have them. Thank you for your...

2. investigating 2025-09-26 14:59 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-09-26 15:49 UTC

   Most of our services are operational. We are currently double checking and verifying that all systems are fully operational.

4. monitoring 2025-09-26 16:10 UTC

   We believe this incident to be over.

5. resolved 2025-09-26 16:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-09-05 21:38 UTC

   Some users are experiencing 404 errors when using Agent and Chat. We've identified the problem and are deploying a fix. Restarting your client will remediate the issue while a fix is deployed.

2. resolved 2025-09-05 22:32 UTC

   Error rates have returned to normal and all users should see normal responses.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: Customer Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-08-22 19:56 UTC

   The issue has been identified and a fix is being implemented.

2. resolved 2025-08-22 20:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-20 16:30 UTC

   We are currently investigating a full service disruption for EU customers.

2. resolved 2025-08-20 16:56 UTC

   Services have returned to normal for all users.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-15 18:21 UTC

   We are currently investing elevated error rates impacting some users across all products.

2. resolved 2025-07-15 18:38 UTC

   Services have returned to normal and we'll continue to monitor systems.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-01 16:39 UTC

   We are investigating an increase in error rates impacting some users. We'll update as soon as we have more information.

2. identified 2025-07-01 16:42 UTC

   We've identified the issue with the authentication system that is impacting all users, and are working to deploy an fix.

3. monitoring 2025-07-01 16:51 UTC

   Systems are recovering and returning to normal. We'll continue to monitor the issue.

4. resolved 2025-07-01 17:02 UTC

   Systems has fully recovered and are operating as normal.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-06-12 17:57 UTC

   An upstream service outage is impacting all services at Augment

2. monitoring 2025-06-12 21:09 UTC

   Completions, Next Edit, and Agent endpoints have fully recovered. Chat is actively recovering. We're monitoring for a full recovery for all users.

3. resolved 2025-06-12 21:58 UTC

   All services have been returned to operational for users in all regions.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-04-29 16:43 UTC

   Users on the Community plan may be experiencing increased errors and degraded performance due to capacity issues. We are working to provision additional resources to return the service to normal.

2. resolved 2025-04-29 21:35 UTC

   We've balanced the load for our Community plan users and service has returned to normal.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-16 20:49 UTC

   We're investigating an issue with our authentication services that is impacting all functionality.

2. resolved 2025-04-16 21:03 UTC

   Services have been restored.

Excerpts are shortened. Read the full incident on Augment Code's status page.

Affected: API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-04-03 14:54 UTC

   We are currently investigating an increase in error rates due to increased service load.

2. identified 2025-04-03 15:58 UTC

   We've identified the issue and are provisioning more resources to handle the additional capacity

3. resolved 2025-04-03 18:48 UTC

   We have now resolved the issue and all systems are operational.

Excerpts are shortened. Read the full incident on Augment Code's status page.