Amp logo

Is Amp Down?

Developer ToolsLive status, outages, and incident history

No. Amp is up right now.

Every monitored Amp system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Amp breaks

Amp is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

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

Official Amp status page
How we know: the official Amp status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Amp Status Summary

As of 13:15 UTC on 14 November 2026, Amp is operational. PulsAPI checked Amp's official status page and found 25 of 25 components operational, with no active incidents. The latest incident, "Claude Code Subscription errors", was on Oct 27, 2026 and lasted 7 min.

Cite as: PulsAPI, “Amp status”, checked 14 November 2026, 13:15 UTC. https://www.pulsapi.com/services/amp

Amp Component Status

The main Amp systems on this page. All 25 are operational right now.

25operational
Amp Agent
Operational
ampcode.com
Operational
Anthropic
Operational

22 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Cloudflare Authoritative DNS, Cloudflare DNS Root Servers, Cloudflare Secondary DNS, Gemini Enterprise Agent Platform, GitHub Actions, GitHub API Requests, GitHub Git Operations, Google Apps Gmail, Google Cloud Platform Google BigQuery, Google Cloud Platform Google Cloud Networking, Google Cloud Platform Google Cloud SQL, Google Cloud Platform Google Container Engine, and 10 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Amp Outages & Incidents

Incident history from the official Amp status page, including resolution updates.

Claude Code Subscription errorsResolved Oct 27, 2026 · 7 minResolved

We traced this back to some errors on our end which could block creation of new threads. The issue resolved itself, and error rates returned to normal. --- [2026-10-27T17:42:06Z] (investigating) We're seeing high error rates for Claude Code subscription usage. Looking into it

Some threads are stuck in reconnectingResolved Oct 23, 2026 · 8 minResolved

Threads are reconnecting and starting successfully again. --- [2026-10-23T19:02:33Z] (investigating) A portion of threads are stuck in reconnecting status or failing to start.

Slowness on ampcode.com and clientsResolved Oct 22, 2026 · 1h 50mResolved

We fixed shed load from the database, it's now in a healthier state. We also ran into an issue with an upstream provider and received a patch from them that we'll apply to avoid the problem in the future. --- [2026-10-22T16:37:13Z] (monitoring) We managed to shed load (we identified a user's plugin causing a lot of load without being rate limited; fixing) and optimized queries. The database performance is back to normal. --- [2026-10-22T16:09:06Z] (identified) We identified a bad query that creates unexpected high load on the database. Reverting. --- [2026-10-22T15:47:44Z] (identified) We're hitting some resource limits from increased load on our database, but need to wait for compute so we can resize. Shedding load right now. Clients (macOS, iOS, TUI) and [ampcode.com](http://ampcode.com "ampcode.com") might be slow. --- [2026-10-22T15:26:00Z] (identified) We're hitting some resource limits from increased load, so some users are seeing period slowness when loading [ampcode.com](http://ampcode.com "ampcode.com"). We're working on scaling up, will keep you updated.

Amp Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Amp incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Amp Outage Reports

Problems reported by engineers using Amp. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Amp problems reported yet.

Something wrong with Amp on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Amp

Amp's status page at ampcodestatus.com lists 25 components, such as Amp Agent, Anthropic and Cloudflare Authoritative DNS. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Amp's side or yours.

Amp Status FAQ

Is Amp down right now?

The verdict at the top of this page comes from the latest poll of the official Amp status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Amp is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Amp recovers.

How do I check Amp uptime history?

PulsAPI tracks Amp uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Amp changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Amp outages?

PulsAPI reads the official Amp status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Amp components?

Yes. PulsAPI monitors 25 individual Amp components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Amp goes down?

Yes. Create a free account and subscribe to Amp: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Amp to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Amp problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Amp?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Amp plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Amp with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services