Is Augment Code Down?

No — Augment Code is up

Augment Code's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 437 ms

Right now

The verdict is the worse of these two. How we decide

Augment Code's status page

status.augmentcode.com · read 3 minutes ago · checked every 3 minutes

Operational

Augment Code's components, as its status page reports them
Component	Status
Cosmos	Operational
Customer Dashboard	Operational
API	Operational

Open their status page

FlareWarden checks

augmentcode.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 437 ms
Checked: 2 hours ago

By region

Amsterdam reachable, 135 ms
Dallas reachable, 465 ms
Frankfurt reachable, 106 ms
Newark reachable, 333 ms
Paris reachable, 362 ms
Stockholm reachable, 330 ms
Sydney reachable, 1316 ms
Toronto reachable, 452 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	39 ms	4 ms	16 ms	119 ms
Dallas	182 ms	25 ms	29 ms	347 ms
Frankfurt	45 ms	1 ms	11 ms	99 ms
Newark	206 ms	9 ms	12 ms	304 ms
Paris	98 ms	9 ms	18 ms	309 ms
Stockholm	72 ms	1 ms	8 ms	324 ms
Sydney	328 ms	1 ms	6 ms	1307 ms
Toronto	180 ms	17 ms	20 ms	340 ms

We check that augmentcode.com loads, not every feature behind it. Test it yourself

History

Incidents Augment Code reported

Since Oct 22, 20 days · from status.augmentcode.com

Incidents: 1
Major or critical: 1
Median to resolve: 46m

OpenAI models are experiencing elevated errrors
major · Nov 9
lasted 46m

Augment Code website availability

Measured by FlareWarden · augmentcode.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 495ms

Last 30 days

26-day clean streak

Oct 12 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of augmentcode.com from multiple regions every 6 hours. Augment Code's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 26 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Augment Code does

Augment Code is an AI coding platform built around its Context Engine, which indexes a codebase so agents and chat answer from it. Developers use it as an extension in VS Code and JetBrains IDEs, through the Auggie CLI, in Cosmos, its web platform for cloud agents and automations, and as a pull request reviewer on GitHub. Each of those depends on Augment's sign-in and tenant API services.

What an outage looks like

Chat and Agent requests fail with 500 errors across Cosmos, the CLI and the IDE extensions, or completions and next edits stop for some users. Cosmos has shown 429 Too Many Requests errors, and its agents' MCP calls have failed with 401 errors. Code Review stops posting comments on pull requests. When an upstream model fails, only that family errors, as when GPT-5 models failed while others worked.

What to do about it

Check status.augmentcode.com, which has rows for Cosmos, the Customer Dashboard and the API, and whose incidents name upstream causes such as GitHub, Slack, Google Cloud, OpenAI or Anthropic. If one model family fails, Augment has advised switching models, in Cosmos or with /model in Auggie. If you use the message queue, it pauses on an error, so review it before resuming. Report lasting problems at support.augmentcode.com with the request ID.

Is it down for everyone, or just you?

If this page says Augment Code is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Augment Code outage FAQ

Is Augment Code down for everyone or just me?

Check status.augmentcode.com first: if it is green and teammates are working, the problem is likely local. Augment's network guide says the extension and Auggie must reach *.augmentcode.com, including auth, login, cosmos and your tenant's api subdomain, so a firewall or proxy such as Zscaler can block them. The checks on this page probe www.augmentcode.com, the public website, so a tenant API fault can happen while they stay green.

Does a GitHub or model provider outage affect Augment Code?

Yes, and Augment's own incident history shows it. A November 2025 GitHub outage stopped remote agents and code reviews, a Slack incident took down the Augment Slackbot, and Anthropic and OpenAI errors have broken specific models. A Google Cloud networking fault made Cosmos and the CLI unavailable in September 2026. When an incident names an upstream provider, that provider's status page usually shows recovery first.

Can I keep coding while Augment Code is down?

Your editor itself is separate software. Augment installs as an extension in VS Code, JetBrains IDEs and Vim, and its completions, chat, next edits and agent all depend on Augment's sign-in and API services, so those features stop until the service recovers. Cosmos sessions run on Augment-hosted cloud environments and stop during a Cosmos incident. If an agent stopped midway through a task, review its changes before asking it to continue.

How long do Augment Code outages usually last?

Most are short. Of 47 resolved incidents on Augment's status page between April 2025 and October 2026, the median lasted a little over an hour and 37 were resolved within four hours. The longest, a Slackbot disruption caused by a Slack incident, ran about 21 hours. An October 2026 outage of Cosmos, the Customer Dashboard and the API lasted about five and a half hours.

Does Augment Code have an uptime SLA?

Yes, for customers whose agreement includes its SLA and Support Policy. That policy sets a 99.5% monthly availability standard, offers service credits on request when it is missed, and targets a response within 2 hours, around the clock, for a critical incident. It excludes trials and beta use, and says updates on incidents affecting many customers may be posted on the status page rather than in each ticket.

How we measure this

We request Augment Code's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Augment Code publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Augment Code itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Augment Code goes down

We check Augment Code every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required