Is Anthropic down?
Anthropic is up.
Our last check reached anthropic.com and got a healthy response.
Anthropic's own status page agrees — all systems operational. View it
The numbers
Availability and response time for Anthropic over the last 24 hours.
Availability
100%
143 checks, none failed
Avg response
116 ms
Mean of every check
Slowest
741 ms
Worst single check
Incidents
0
Runs of failing checks
Downtime
None
Estimated from samples
Downtime is estimated from 10-minute samples, so figures are accurate to within one check interval.
Over time
Every check we ran, and how long each one took.
Availability
- All checks passed
- Some checks failed
- All checks failed
Response time
Where the time goes
"Is it down?" is usually really "it feels broken — what's wrong with it?" This is the answer: every millisecond of a request to anthropic.com, broken into the four phases it actually spends time in.
- DNS
- 5 ms5%
- TCP + TLS
- 13 ms11%
- Time to first byte
- 84 ms72%
- Download
- 14 ms12%
Resolving the hostname to an IP address.
Opening the connection and completing the TLS handshake.
Waiting for the server to start responding. Usually the server thinking.
Transferring the response body.
Averaged over the last 24 hours. The four phases add up to the total response time of 116 ms.
What it's like to load
Everything above is a lightweight HTTP check: did anthropic.com answer? This is a real Chromium browser actually loading the page — which is the only way to know whether a human would call it working.
Anthropic renders in a real browser.
A real Chromium browser loaded anthropic.com, the page painted, and the JavaScript ran. A server can return a healthy 200 while showing a user a blank screen — this is how we know it didn’t.
Largest Contentful Paint (LCP)
How long until the main content appears.
First Contentful Paint (FCP)
How long until anything at all appears.
Total Blocking Time (TBT)
How long the page was frozen and unable to respond to you.
Cumulative Layout Shift (CLS)
How much the page jumped around while loading.
Time to First Byte (TTFB)
How long the server took to start answering.
1 error while loading
- Console
- 1
- Network
- 0
- Document
- 0
- Script
- 0
Measured with a real browser every hour from N. Virginia and Frankfurt, averaged over the last 7 days (168 runs). This is a different instrument from the uptime above, which is a lightweight HTTP check running every 10 minutes. Loading speed is a trend; being down is an event. Neither of these numbers affects the other, and a slow page is never reported as an outage.
Incidents
Every time a check against anthropic.com failed in the last 30 days, grouped into incidents.
No incidents recorded for Anthropic.
Every check we’ve run against Anthropic has passed.
This page is a Checkly monitor.
Not a mockup of one. Everything above is produced by the monitor below, running every 10 minutes from N. Virginia and Frankfurt. It lives in a repo, gets code-reviewed, and deploys from CI — the same way you would monitor your own service.
That’s the whole product. Monitoring you can read, diff, and version.
How we check Anthropic
A real request to the endpoint that matters, every 10 minutes — measured, not crowd-sourced.
What we actually do
- We send a real HTTP GET to
https://www.anthropic.comevery 10 minutes. - We run it from two datacenters: N. Virginia and Frankfurt.
- It passes if the endpoint answers with a status below 400 within 10 seconds. Slower than 3 seconds is “degraded”, not down.
- A single failed check isn’t a verdict. We retry it from the other region before recording anything, so a transient blip never shows here as an outage.
What a green check means
- Anthropic answered a real request from both N. Virginia and Frankfurt — an actual measurement, not complaints counted from a crowd.
- We probe the endpoint that fails when Anthropic fails, so a green check tracks the part you depend on, not a marketing page that stays up regardless.
- Checks run around the clock, every 10 minutes, on the same infrastructure Checkly customers monitor production with.
Frequently asked
No. Our most recent check reached https://www.anthropic.com and got a healthy response. We check every 10 minutes from N. Virginia and Frankfurt.
We run a real HTTP request against https://www.anthropic.com every 10 minutes from N. Virginia and Frankfurt, using Checkly's synthetic monitoring. A check passes when the endpoint returns a status below 400 within 10 seconds. We are not counting user reports — we are measuring the actual response.
We probe https://www.anthropic.com because it is the endpoint that best reflects whether Anthropic is actually usable.
We check Anthropic from N. Virginia and Frankfurt. If it answers us but not you, the problem is usually specific to your network, ISP, region, or account rather than Anthropic itself.
Downdetector counts user reports — how many people are complaining. We run an actual synthetic check against the service and report what the wire says. Reports lag the outage and can be noisy; a probe either gets a response or it doesn't. For Anthropic we also read its own status page, so if the service reports an incident while our probe still reaches it, we surface that too.