What does reachable from NexIP mean?
The monitored web endpoint returned a successful HTTP response from the NexIP location. This does not guarantee that messaging, calls, login or other features work for every user or region.
AI services
HTTP-проверка из точки NexIP успешна. Доступность из всех регионов не подтверждена.
The monitored web endpoint returned a successful HTTP response from the NexIP location. This does not guarantee that messaging, calls, login or other features work for every user or region.
Reports over 24 hours, signals over 15 minutes and the outage index measure different periods and conditions. Their values may differ without being contradictory.
Service monitoring
Мониторинг доступности сервиса Claude, пользовательских сигналов и технических проверок NexIP.
Reports submitted to NexIP. One report does not prove a widespread outage.
No reports during this period.
30-minute intervals · Moscow time · actual dataLast 7 days
Observation points
Observation history
Actual NexIP primary probe measurements, not user reports
| Time (server) | Checks | Average | Peak | Down | Blocked |
|---|---|---|---|---|---|
| 2026-11-15 03:00:00 | 22 | 414 ms | 591 ms | 0 | 0 |
| 2026-11-15 06:00:00 | 22 | 486 ms | 1 899 ms | 0 | 0 |
| 2026-11-15 09:00:00 | 23 | 508 ms | 796 ms | 0 | 0 |
| 2026-11-15 12:00:00 | 22 | 541 ms | 1 188 ms | 0 | 0 |
| 2026-11-15 15:00:00 | 23 | 597 ms | 848 ms | 0 | 0 |
| 2026-11-15 18:00:00 | 22 | 630 ms | 1 207 ms | 0 | 0 |
| 2026-11-15 21:00:00 | 23 | 539 ms | 866 ms | 0 | 0 |
| 2026-11-16 00:00:00 | 22 | 432 ms | 553 ms | 0 | 0 |
| 2026-11-16 03:00:00 | 23 | 412 ms | 506 ms | 0 | 0 |
| 2026-11-16 06:00:00 | 22 | 481 ms | 820 ms | 0 | 0 |
| 2026-11-16 09:00:00 | 23 | 507 ms | 712 ms | 0 | 0 |
| 2026-11-16 12:00:00 | 23 | 528 ms | 924 ms | 0 | 0 |
| 2026-11-16 15:00:00 | 22 | 571 ms | 778 ms | 0 | 0 |
| 2026-11-16 18:00:00 | 23 | 547 ms | 942 ms | 0 | 0 |
| 2026-11-16 21:00:00 | 23 | 512 ms | 764 ms | 0 | 0 |
| 2026-11-17 00:00:00 | 22 | 462 ms | 746 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 23 | 425 ms | 764 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 23 | 555 ms | 1 376 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 23 | 553 ms | 1 005 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 23 | 617 ms | 1 069 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 22 | 607 ms | 1 218 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 22 | 550 ms | 905 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 23 | 494 ms | 686 ms | 0 | 0 |
| 2026-11-18 00:00:00 | 22 | 444 ms | 706 ms | 0 | 0 |
| 2026-11-18 03:00:00 | 23 | 453 ms | 800 ms | 0 | 0 |
| 2026-11-18 06:00:00 | 23 | 497 ms | 994 ms | 0 | 0 |
| 2026-11-18 09:00:00 | 23 | 543 ms | 1 162 ms | 0 | 0 |
| 2026-11-18 12:00:00 | 22 | 531 ms | 844 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 23 | 643 ms | 3 775 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 22 | 499 ms | 769 ms | 0 | 0 |
| 2026-11-18 21:00:00 | 23 | 496 ms | 715 ms | 0 | 0 |
| 2026-11-19 00:00:00 | 22 | 465 ms | 576 ms | 0 | 0 |
| 2026-11-19 03:00:00 | 23 | 405 ms | 516 ms | 0 | 0 |
| 2026-11-19 06:00:00 | 23 | 470 ms | 1 039 ms | 0 | 0 |
| 2026-11-19 09:00:00 | 22 | 763 ms | 4 437 ms | 0 | 0 |
| 2026-11-19 12:00:00 | 22 | 552 ms | 785 ms | 0 | 0 |
| 2026-11-19 15:00:00 | 22 | 537 ms | 960 ms | 0 | 0 |
| 2026-11-19 18:00:00 | 23 | 565 ms | 1 276 ms | 0 | 0 |
| 2026-11-19 21:00:00 | 22 | 640 ms | 2 412 ms | 0 | 0 |
| 2026-11-20 00:00:00 | 6 | 460 ms | 520 ms | 0 | 0 |
Success is up or degraded among recorded primary probe checks. This is not a public uptime SLA. Available history can be shorter than the selected range.
Your signal
Tell us. Registration is not required. The same signal will not be counted repeatedly within a short period.
User opinions are separate from the technical outage status.
No ratings yet
No comments yet.
This page tracks the current observed status of Claude, recent incidents, automated availability checks and available user reports. NexIP does not treat a single failed check as proof of a global outage.
Ping · Website availability · Website monitoring · All service outages
NexIP shows the current observed status of Claude using automated checks, incident data and available user signals. A local connection problem may differ from a large-scale outage.
Availability can differ by provider, region, DNS, routing, application version or service component. NexIP therefore separates observed signals from confirmed large-scale incidents.
Check the host with Ping, website availability and your own connection. Comparing several independent checks helps distinguish a local problem from a wider outage.