Skip to main content

Live - 300+ check locations

Is Claude Code down right now?

HostTracker's monitoring network reached api.anthropic.com and completed a full check without errors. It has been up for 40d 2h.

Stop finding out from a search - HostTracker's website monitoring checks the services you depend on from 300+ locations and alerts you the moment one changes.

api.anthropic.com checked every 10m

Up

for 40d 2h

Last check
just now
Next check
-
HTTP
OK

Checking api.anthropic.com right now

A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.

Claude Code status

What Claude's status page reports about Claude Code - separate from HostTracker's own checks above. Claude Code is part of Claude, so the parts listed are all of Claude's.

Operational according to Claude's status page, updated just now

How Claude Code has behaved

Every figure here comes from HostTracker's own checks of api.anthropic.com, not from the vendor's status page.

Response time

33ms avg · 315ms peak

What we check

  • HTTP33 ms average, every 10 minutes
    OK
  • Ping9 ms average, every 10 minutes
    OK

90-day uptime

100.000% over 41 measured days · 0 incidents

  • Operational
  • Degraded
  • Down
  • No data
90 days agoToday

Incident history

Last 90 days

No incidents recorded in the last 90 days.

Get alerted the next time Claude Code goes down

One alert per incident, on Slack, Teams, SMS or email, and only for the parts you use. To start, we pre-select Claude API (api.anthropic.com) and Claude Code.

  • Claude's own post, linked and quoted
  • Problem reports from people checking Claude on HostTracker
  • Our own check of the Claude API

Claude Code is part of Claude, so the watch is on Claude - you choose which of its parts to follow.

30-day trial, no card. Claude comes pre-selected - nothing is watched until you press Start watching.

Already have an account? Sign in

HostTracker is not affiliated with Claude.

Is Claude Code not working for you?

Tell us what is broken. One click, no account.

One report per visitor per hour. We keep only the country and the problem type, never your IP address.

Problem reports, last 24 hours

Reports come from visitors of this page. A sharp rise above the usual level, together with failed checks in the live check below, means the problem is on Claude Code's side, not yours.

Top reported problems

    100.00%Uptime in the last 24 hours, 0 incidents, 0 min down
    100.00%Uptime over the last 7 days
    100.00%Uptime over the last 30 days
    33 msAverage response over 30 days

    About Claude Code outages

    Written by the HostTracker monitoring team · updated from live probe data.

    Claude Code is Anthropic's command-line coding assistant, and unlike the claude.ai web chat it has no browser tab to glance at - it lives inside a terminal, talking directly to the Anthropic API to plan changes, edit files and run commands inside a real development session. Because the CLI has no front-end status page of its own, this page watches api.anthropic.com, the same endpoint Claude Code calls for every request, so a failing check here is Claude Code's problem too, not a separate site. The web chat at claude.ai runs on related but distinct infrastructure and has its own page at /en/is-claude-down - if you use both, check the one you actually depend on, since one can be healthy while the other is degraded.

    Common causes of Claude Code downtime

    Not sure whether it's Claude Code or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.

    API rate limits or a 529 "overloaded" response from Anthropic's servers, which pauses or fails requests mid-session rather than dropping the connection

    Model-serving incidents on Anthropic's backend that slow or block responses across every client that calls the API, Claude Code included

    Authentication or OAuth login failures that lock the CLI out of a session while the API itself is reachable

    CLI version issues after an update, where an outdated client sends requests the current API no longer accepts

    Regional network or routing problems that make api.anthropic.com unreachable from a specific country or ISP while it works everywhere else

    Other services we track

    See every service on one page
    C ChatGPTOperational C Claude (Anthropic)Operational G GitHubOperational C CloudflareOperational A AWSOperational G GoogleOperational S SlackOperational D DiscordOperational Z ZoomOperational F FacebookOperational I InstagramOperational X X (Twitter)Operational N NetflixOperational S SteamOperational S SnapchatOperational S SpotifyOperational Y YouTubeOperational W WhatsAppOperational A AmazonOperational T T-MobileOperational A AT&TOperational S SpectrumOperational V VerizonOperational X XfinityCheck status R RobloxOperational F FortniteOperational H HuluOperational R RedditOperational T TikTokOperational L LinkedInOperational B BlueskyOperational A AO3 (Archive of Our Own)Operational C CrunchyrollOperational D Disney+Operational P Paramount+Operational e eBayOperational G GmailOperational O OutlookOperational Y Yahoo MailOperational G GeminiOperational G GrokOperational C Character.AIOperational J Janitor AIOperational C CanvasOperational V VenmoOperational Z ZelleOperational C Cash AppOperational C ChimeOperational S ShopifyOperational D DoorDashOperational L League of LegendsOperational E Epic GamesOperational G GitHub CopilotOperational C CursorOperational J JiraOperational D DeepSeekOperational S SupabaseOperational P PerplexityOperational O OpenAI APIOperational O OpenAI CodexOperational V VercelOperational G GitLabOperational T TwilioOperational D DatadogOperational B BitbucketOperational R ReplitOperational F FigmaOperational N NotionOperational L LinearOperational S StripeOperational P PayPalOperational C ChaseOperational B Bank of AmericaOperational R RobinhoodOperational C CoinbaseOperational U UberOperational P PinterestOperational C CanvaOperational H HBO MaxOperational M MessengerOperational D DropboxOperational S SalesforceOperational O OktaOperational M MailchimpOperational A AzureOperational P PlayStation NetworkOperational X Xbox LiveOperational M MinecraftOperational B Battle.netOperational V ValorantOperational E EAOperational T TwitchOperational E ESPNOperational

    HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 14 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.

    Questions people ask during an outage

    The live probe run on this page tests api.anthropic.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than Claude Code being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.

    Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

    No - as of the most recent check, api.anthropic.com is responding normally to HostTracker's monitoring network, and has been up for 40d 2h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

    No - as of the most recent check, api.anthropic.com is responding normally to HostTracker's monitoring network, and has been up for 40d 2h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

    A 529 response means Anthropic's API is overloaded and can't accept your request right now, which is a capacity signal rather than a sign anything is broken on your machine. It's distinct from a network failure or an auth error - the connection succeeded and reached Anthropic's servers, and those servers are the ones under pressure. It usually clears within minutes during a demand spike, and retrying after a short pause is normally enough. If it persists for an extended period, the live check on this page confirms whether it's a wider incident.

    Not necessarily either way - Claude Code and the claude.ai web app both call Anthropic's API, but often through different paths and limits, so one can be degraded while the other is healthy. A CLI session failing while the website loads normally usually points at something specific to API access - a token, a rate limit, a regional route - rather than a platform-wide incident. Check /en/is-claude-down for the web app specifically; this page tracks the API endpoint Claude Code itself depends on.

    Usually not. An authentication or OAuth failure blocks your session from reaching the API but doesn't necessarily mean the API is unreachable - it's more often a stale token, an expired login, or a permissions problem on the account side. Signing out and back in through the CLI resolves most of these. If sign-in fails for many people at once and this page also shows the API unreachable, that points at a genuine authentication-service incident instead.

    Regional routing is a real cause of intermittent failures separate from any incident at Anthropic. A misconfigured DNS resolver, a corporate proxy, or a routing problem between your ISP and Anthropic's infrastructure can make api.anthropic.com unreachable from one location while it works normally elsewhere. Testing the endpoint from multiple independent locations, which is what this page does, is the fastest way to tell a local network problem from a real outage affecting everyone.