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.
Transport and travel
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
Мониторинг доступности сервиса РЖД, пользовательских сигналов и технических проверок 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-13 00:00:00 | 22 | 502 ms | 547 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 23 | 504 ms | 584 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 22 | 502 ms | 587 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 23 | 542 ms | 835 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 22 | 540 ms | 757 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 23 | 548 ms | 746 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 22 | 565 ms | 1 549 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 23 | 532 ms | 673 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 516 ms | 648 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 22 | 493 ms | 593 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 23 | 513 ms | 585 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 22 | 517 ms | 586 ms | 0 | 0 |
| 2026-11-14 12:00:00 | 22 | 541 ms | 768 ms | 0 | 0 |
| 2026-11-14 15:00:00 | 23 | 517 ms | 605 ms | 0 | 0 |
| 2026-11-14 18:00:00 | 22 | 519 ms | 678 ms | 0 | 0 |
| 2026-11-14 21:00:00 | 23 | 513 ms | 598 ms | 0 | 0 |
| 2026-11-15 00:00:00 | 22 | 509 ms | 620 ms | 0 | 0 |
| 2026-11-15 03:00:00 | 23 | 532 ms | 692 ms | 0 | 0 |
| 2026-11-15 06:00:00 | 22 | 509 ms | 644 ms | 0 | 0 |
| 2026-11-15 09:00:00 | 23 | 526 ms | 608 ms | 0 | 0 |
| 2026-11-15 12:00:00 | 22 | 527 ms | 652 ms | 0 | 0 |
| 2026-11-15 15:00:00 | 23 | 528 ms | 597 ms | 0 | 0 |
| 2026-11-15 18:00:00 | 22 | 534 ms | 638 ms | 0 | 0 |
| 2026-11-15 21:00:00 | 23 | 514 ms | 614 ms | 0 | 0 |
| 2026-11-16 00:00:00 | 22 | 513 ms | 677 ms | 0 | 0 |
| 2026-11-16 03:00:00 | 23 | 517 ms | 666 ms | 0 | 0 |
| 2026-11-16 06:00:00 | 22 | 508 ms | 660 ms | 0 | 0 |
| 2026-11-16 09:00:00 | 23 | 553 ms | 763 ms | 0 | 0 |
| 2026-11-16 12:00:00 | 22 | 558 ms | 765 ms | 0 | 0 |
| 2026-11-16 15:00:00 | 23 | 543 ms | 769 ms | 0 | 0 |
| 2026-11-16 18:00:00 | 23 | 521 ms | 694 ms | 0 | 0 |
| 2026-11-16 21:00:00 | 22 | 522 ms | 655 ms | 0 | 0 |
| 2026-11-17 00:00:00 | 23 | 518 ms | 728 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 22 | 531 ms | 683 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 24 | 513 ms | 612 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 23 | 550 ms | 653 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 23 | 616 ms | 1 591 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 22 | 567 ms | 718 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 22 | 520 ms | 591 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 15 | 498 ms | 533 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 РЖД, 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 РЖД 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.