Skip to content

Outage tracker / Anthropic

Is Anthropic down?

I'm having a problem

Vendor reports no incidentWhat Anthropic reports

Anthropic reports no incident on its status page.

As of the last successful poll, 2026-10-19 20:46 UTC.

Anthropic's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Partially degradedchecked moments ago

Anthropic is answering our probes, but its sign-in surface is running at least 3.6x its 7-day median from US-Central. Everything else we check answered at its usual speed.

As of Oct 19, 2026, 8:55 PM UTC, RealUptime's checks of Anthropic passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 19, 2026, 8:55 PM UTC
US-East592 msChecks passing
US-West1054 msChecks passing
Europe391 msChecks passing
Asia-Pacific1327 msChecks passing
US-Central497 msDegraded
Canada161 msChecks passing
UK123 msChecks passing
Southeast Asia259 msChecks passing
Australia243 msChecks passing
South America163 msChecks passing
their status pagetheir claim, not our reading

Anthropic reports: All systems operational (“All Systems Operational”)

from Anthropic's own status page, checked Oct 19, 2026, 8:49 PM UTC
Anthropic's own status page shows no incident, and our checks of Anthropic pass right now.

Anthropic's own component breakdown, as they publish it

  • claude.aiOperational
  • Claude Console (platform.claude.com)Operational
  • Claude API (api.anthropic.com)Operational
  • Claude CodeOperational
  • Claude CoworkOperational
  • Claude for GovernmentOperational

These are Anthropic's components, named and scored by Anthropic. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Anthropic's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Anthropic response time, by region

US-East
496msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 269ms2026-09-21 UTC: p95 395ms2026-09-22 UTC: p95 332ms2026-09-23 UTC: p95 382ms2026-09-24 UTC: p95 378ms2026-09-25 UTC: p95 365ms2026-09-26 UTC: p95 343ms2026-09-27 UTC: p95 355ms2026-09-28 UTC: p95 420ms2026-09-29 UTC: p95 370ms2026-09-30 UTC: p95 293ms2026-10-01 UTC: p95 440ms2026-10-02 UTC: p95 364ms2026-10-03 UTC: p95 311ms2026-10-04 UTC: p95 253ms2026-10-05 UTC: p95 272ms2026-10-06 UTC: p95 316ms2026-10-07 UTC: p95 322ms2026-10-08 UTC: p95 394ms2026-10-09 UTC: p95 437ms2026-10-10 UTC: p95 401ms2026-10-11 UTC: p95 325ms2026-10-12 UTC: p95 392ms2026-10-13 UTC: p95 435ms2026-10-14 UTC: p95 450ms2026-10-15 UTC: p95 470ms2026-10-16 UTC: p95 404ms2026-10-17 UTC: p95 982ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 496ms
Sep 20Oct 4Oct 19
US-West
1.1sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 447ms2026-09-21 UTC: p95 412ms2026-09-22 UTC: p95 485ms2026-09-23 UTC: p95 396ms2026-09-24 UTC: p95 416ms2026-09-25 UTC: p95 477ms2026-09-26 UTC: p95 519ms2026-09-27 UTC: p95 387ms2026-09-28 UTC: p95 350ms2026-09-29 UTC: p95 513ms2026-09-30 UTC: p95 409ms2026-10-01 UTC: p95 418ms2026-10-02 UTC: p95 340ms2026-10-03 UTC: p95 409ms2026-10-04 UTC: p95 227ms2026-10-05 UTC: p95 289ms2026-10-06 UTC: p95 369ms2026-10-07 UTC: p95 412ms2026-10-08 UTC: p95 365ms2026-10-09 UTC: p95 477ms2026-10-10 UTC: p95 395ms2026-10-11 UTC: p95 357ms2026-10-12 UTC: p95 401ms2026-10-13 UTC: p95 472ms2026-10-14 UTC: p95 453ms2026-10-15 UTC: p95 489ms2026-10-16 UTC: p95 533ms2026-10-17 UTC: p95 947ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.1s
Sep 20Oct 4Oct 19
Europe
1.2sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 464ms2026-09-21 UTC: p95 561ms2026-09-22 UTC: p95 488ms2026-09-23 UTC: p95 370ms2026-09-24 UTC: p95 387ms2026-09-25 UTC: p95 394ms2026-09-26 UTC: p95 421ms2026-09-27 UTC: p95 443ms2026-09-28 UTC: p95 360ms2026-09-29 UTC: p95 348ms2026-09-30 UTC: p95 327ms2026-10-01 UTC: p95 511ms2026-10-02 UTC: p95 581ms2026-10-03 UTC: p95 531ms2026-10-04 UTC: p95 500ms2026-10-05 UTC: p95 326ms2026-10-06 UTC: p95 319ms2026-10-07 UTC: p95 420ms2026-10-08 UTC: p95 374ms2026-10-09 UTC: p95 356ms2026-10-10 UTC: p95 355ms2026-10-11 UTC: p95 327ms2026-10-12 UTC: p95 352ms2026-10-13 UTC: p95 348ms2026-10-14 UTC: p95 326ms2026-10-15 UTC: p95 400ms2026-10-16 UTC: p95 325ms2026-10-17 UTC: p95 754ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s
Sep 20Oct 4Oct 19
Asia-Pacific
2.2sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 581ms2026-09-21 UTC: p95 652ms2026-09-22 UTC: p95 570ms2026-09-23 UTC: p95 592ms2026-09-24 UTC: p95 546ms2026-09-25 UTC: p95 702ms2026-09-26 UTC: p95 626ms2026-09-27 UTC: p95 669ms2026-09-28 UTC: p95 614ms2026-09-29 UTC: p95 751ms2026-09-30 UTC: p95 750ms2026-10-01 UTC: p95 671ms2026-10-02 UTC: p95 554ms2026-10-03 UTC: p95 556ms2026-10-04 UTC: p95 447ms2026-10-05 UTC: p95 504ms2026-10-06 UTC: p95 602ms2026-10-07 UTC: p95 627ms2026-10-08 UTC: p95 639ms2026-10-09 UTC: p95 559ms2026-10-10 UTC: p95 577ms2026-10-11 UTC: p95 596ms2026-10-12 UTC: p95 634ms2026-10-13 UTC: p95 639ms2026-10-14 UTC: p95 716ms2026-10-15 UTC: p95 864ms2026-10-16 UTC: p95 809ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.2s
Sep 20Oct 4Oct 19
US-Central
1.1sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 564ms2026-09-21 UTC: p95 553ms2026-09-22 UTC: p95 467ms2026-09-23 UTC: p95 458ms2026-09-24 UTC: p95 426ms2026-09-25 UTC: p95 502ms2026-09-26 UTC: p95 371ms2026-09-27 UTC: p95 343ms2026-09-28 UTC: p95 348ms2026-09-29 UTC: p95 401ms2026-09-30 UTC: p95 432ms2026-10-01 UTC: p95 286ms2026-10-02 UTC: p95 314ms2026-10-03 UTC: p95 549ms2026-10-04 UTC: p95 333ms2026-10-05 UTC: p95 435ms2026-10-06 UTC: p95 408ms2026-10-07 UTC: p95 493ms2026-10-08 UTC: p95 325ms2026-10-09 UTC: p95 416ms2026-10-10 UTC: p95 431ms2026-10-11 UTC: p95 342ms2026-10-12 UTC: p95 356ms2026-10-13 UTC: p95 363ms2026-10-14 UTC: p95 412ms2026-10-15 UTC: p95 348ms2026-10-16 UTC: p95 394ms2026-10-17 UTC: p95 927ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.1s
Sep 20Oct 4Oct 19
Canada
1.5sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 380ms2026-09-21 UTC: p95 377ms2026-09-22 UTC: p95 426ms2026-09-23 UTC: p95 478ms2026-09-24 UTC: p95 485ms2026-09-25 UTC: p95 461ms2026-09-26 UTC: p95 744ms2026-09-27 UTC: p95 535ms2026-09-28 UTC: p95 611ms2026-09-29 UTC: p95 511ms2026-09-30 UTC: p95 408ms2026-10-01 UTC: p95 517ms2026-10-02 UTC: p95 432ms2026-10-03 UTC: p95 482ms2026-10-04 UTC: p95 486ms2026-10-05 UTC: p95 670ms2026-10-06 UTC: p95 460ms2026-10-07 UTC: p95 351ms2026-10-08 UTC: p95 313ms2026-10-09 UTC: p95 327ms2026-10-10 UTC: p95 425ms2026-10-11 UTC: p95 437ms2026-10-12 UTC: p95 424ms2026-10-13 UTC: p95 592ms2026-10-14 UTC: p95 656ms2026-10-15 UTC: p95 568ms2026-10-16 UTC: p95 438ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s
Sep 20Oct 4Oct 19
UK
1.1sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 347ms2026-09-21 UTC: p95 407ms2026-09-22 UTC: p95 456ms2026-09-23 UTC: p95 433ms2026-09-24 UTC: p95 390ms2026-09-25 UTC: p95 410ms2026-09-26 UTC: p95 499ms2026-09-27 UTC: p95 356ms2026-09-28 UTC: p95 485ms2026-09-29 UTC: p95 380ms2026-09-30 UTC: p95 364ms2026-10-01 UTC: p95 413ms2026-10-02 UTC: p95 346ms2026-10-03 UTC: p95 308ms2026-10-04 UTC: p95 303ms2026-10-05 UTC: p95 301ms2026-10-06 UTC: p95 295ms2026-10-07 UTC: p95 341ms2026-10-08 UTC: p95 291ms2026-10-09 UTC: p95 291ms2026-10-10 UTC: p95 355ms2026-10-11 UTC: p95 323ms2026-10-12 UTC: p95 346ms2026-10-13 UTC: p95 276ms2026-10-14 UTC: p95 281ms2026-10-15 UTC: p95 259ms2026-10-16 UTC: p95 299ms2026-10-17 UTC: p95 707ms2026-10-18 UTC: p95 994ms2026-10-19 UTC: p95 1.1s
Sep 20Oct 4Oct 19
Southeast Asia
1.6sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 937ms2026-09-24 UTC: p95 830ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 982ms2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 942ms2026-09-30 UTC: p95 859ms2026-10-01 UTC: p95 794ms2026-10-02 UTC: p95 788ms2026-10-03 UTC: p95 625ms2026-10-04 UTC: p95 781ms2026-10-05 UTC: p95 631ms2026-10-06 UTC: p95 684ms2026-10-07 UTC: p95 643ms2026-10-08 UTC: p95 665ms2026-10-09 UTC: p95 844ms2026-10-10 UTC: p95 909ms2026-10-11 UTC: p95 770ms2026-10-12 UTC: p95 726ms2026-10-13 UTC: p95 792ms2026-10-14 UTC: p95 892ms2026-10-15 UTC: p95 970ms2026-10-16 UTC: p95 885ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s
Sep 20Oct 4Oct 19
Australia
2.3sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 717ms2026-09-21 UTC: p95 975ms2026-09-22 UTC: p95 551ms2026-09-23 UTC: p95 644ms2026-09-24 UTC: p95 583ms2026-09-25 UTC: p95 634ms2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 480ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 932ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 746ms2026-10-02 UTC: p95 794ms2026-10-03 UTC: p95 784ms2026-10-04 UTC: p95 613ms2026-10-05 UTC: p95 669ms2026-10-06 UTC: p95 728ms2026-10-07 UTC: p95 623ms2026-10-08 UTC: p95 557ms2026-10-09 UTC: p95 683ms2026-10-10 UTC: p95 696ms2026-10-11 UTC: p95 728ms2026-10-12 UTC: p95 781ms2026-10-13 UTC: p95 759ms2026-10-14 UTC: p95 761ms2026-10-15 UTC: p95 940ms2026-10-16 UTC: p95 872ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.3s
Sep 20Oct 4Oct 19
South America
2.4sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 716ms2026-09-21 UTC: p95 810ms2026-09-22 UTC: p95 843ms2026-09-23 UTC: p95 670ms2026-09-24 UTC: p95 661ms2026-09-25 UTC: p95 732ms2026-09-26 UTC: p95 621ms2026-09-27 UTC: p95 702ms2026-09-28 UTC: p95 796ms2026-09-29 UTC: p95 716ms2026-09-30 UTC: p95 730ms2026-10-01 UTC: p95 645ms2026-10-02 UTC: p95 582ms2026-10-03 UTC: p95 884ms2026-10-04 UTC: p95 786ms2026-10-05 UTC: p95 690ms2026-10-06 UTC: p95 676ms2026-10-07 UTC: p95 972ms2026-10-08 UTC: p95 614ms2026-10-09 UTC: p95 961ms2026-10-10 UTC: p95 750ms2026-10-11 UTC: p95 767ms2026-10-12 UTC: p95 677ms2026-10-13 UTC: p95 739ms2026-10-14 UTC: p95 779ms2026-10-15 UTC: p95 737ms2026-10-16 UTC: p95 744ms2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.4s
Sep 20Oct 4Oct 19

Check your own site while you wait on Anthropic

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Anthropic. It cannot diagnose Anthropic's own systems.

What we measured, function by function

Anthropic answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIUS-East: Awaiting dataUS-West: Awaiting dataEurope: Awaiting dataAsia-Pacific: Awaiting dataUS-Central: Awaiting dataCanada: Awaiting dataUK: Awaiting dataSoutheast Asia: Awaiting dataAustralia: Awaiting dataSouth America: Awaiting data
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Degraded Answering, but 3.6x slower than its 7-day median.Canada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Anthropic reports an incident on its status page, and again when it reports it resolved.

Get an email when Anthropic reports an incident

Email me when Anthropic reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Anthropic's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    DegradedUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 592msstatus code: 401checked: Oct 19, 2026, 8:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Anthropic normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1054msstatus code: 401checked: Oct 19, 2026, 8:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Anthropic normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Degradedlatency: 497msstatus code: 401checked: Oct 19, 2026, 8:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Anthropic normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 161msstatus code: 401checked: Oct 19, 2026, 8:52 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Anthropic normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 163msstatus code: 401checked: Oct 19, 2026, 8:52 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Anthropic normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 391msstatus code: 401checked: Oct 19, 2026, 8:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Anthropic normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 123msstatus code: 401checked: Oct 19, 2026, 8:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Anthropic normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1327msstatus code: 401checked: Oct 19, 2026, 8:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Anthropic normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 259msstatus code: 401checked: Oct 19, 2026, 8:52 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Anthropic normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 243msstatus code: 401checked: Oct 19, 2026, 8:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Anthropic normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Anthropic, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We started counting reports for Anthropic on August 28, 2026.

Recent probe events

Issue with spend limits, 1mdeclared on their status page2026-10-07
Elevated errors on platform.claude.com, 148h 35mdeclared on their status page2026-10-07
Elevated errors loading usage data on platform.claude.com, 1h 13mdeclared on their status page2026-10-07
Elevated errors for Claude Opus 5.5, 19mdeclared on their status page2026-10-06
Elevated errors for Claude Mythos 5.1 and Claude Fable 5.1, 16mdeclared on their status page2026-10-05
Delayed credits on the Claude Platform, 6h 16mdeclared on their status page2026-10-01
Elevated errors on claude.ai, Claude Code, Claude Cowork and the Claude API, 2h 6mdeclared on their status page2026-09-29
Elevated errors for multiple models, 1h 38mdeclared on their status page2026-09-22

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Anthropic since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Anthropic covering any window you pick, with our check readings and Anthropic's own claim at the time, side by side.

Full check history for Anthropic: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Anthropic uptime by RealUptime's checksLive, from this page's own readings.
[![Anthropic uptime by RealUptime's checks](https://realuptime.io/outages/anthropic/badge.svg?days=30)](https://realuptime.io/outages/anthropic)
<a href="https://realuptime.io/outages/anthropic"><img src="https://realuptime.io/outages/anthropic/badge.svg?days=30" alt="Anthropic uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Anthropic down?", https://realuptime.io/outages/anthropic. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

Per-model status

No vendor publishes per-model status, so this is the closest thing available: a real, credentialed completion call to each model below, on our own schedule. A rejected credential of ours never renders as Anthropic failing here. See “Awaiting data” below.
claude-haiku-4-5Awaiting data
Europe · last completed call Oct 5, 2026, 9:10 PM UTC
claude-haiku-4-5Awaiting data
South America · last completed call Oct 5, 2026, 9:09 PM UTC
claude-haiku-4-5Awaiting data
US-East · last completed call Oct 5, 2026, 9:10 PM UTC
claude-haiku-4-5Awaiting data
UK · last completed call Oct 5, 2026, 9:10 PM UTC
claude-haiku-4-5Awaiting data
Asia-Pacific · last completed call Oct 5, 2026, 9:08 PM UTC
claude-haiku-4-5Awaiting data
US-Central · last completed call Oct 5, 2026, 9:09 PM UTC
claude-haiku-4-5Awaiting data
Southeast Asia · last completed call Oct 5, 2026, 9:09 PM UTC
claude-haiku-4-5Awaiting data
US-West · last completed call Oct 5, 2026, 9:10 PM UTC
claude-haiku-4-5Awaiting data
Australia · last completed call Oct 5, 2026, 9:07 PM UTC
claude-haiku-4-5Awaiting data
Canada · last completed call Oct 5, 2026, 9:10 PM UTC

What we check

primaryfunctional: auth surface
https://api.anthropic.com/v1/models
secondary
https://platform.claude.com/
secondaryfunctional: live API
https://api.anthropic.com/v1/messages

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.anthropic.com

RealUptime is not affiliated with Anthropic; the name identifies what we checked, and nothing here speaks for Anthropic's own team. We send a single web request to Anthropic from 10 regions on our own schedule and time the response. We do not see inside Anthropic's systems, do not use an account or real transaction, and are not the same signal Anthropic's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Anthropic is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.