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.
Government 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
Мониторинг доступности сервиса Росреестр, пользовательских сигналов и технических проверок 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 | 616 ms | 640 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 23 | 619 ms | 649 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 22 | 613 ms | 637 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 23 | 623 ms | 649 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 22 | 630 ms | 757 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 23 | 591 ms | 622 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 22 | 593 ms | 612 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 23 | 596 ms | 639 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 588 ms | 622 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 22 | 593 ms | 613 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 23 | 592 ms | 607 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 22 | 594 ms | 609 ms | 0 | 0 |
| 2026-11-14 12:00:00 | 22 | 588 ms | 606 ms | 0 | 0 |
| 2026-11-14 15:00:00 | 23 | 641 ms | 1 846 ms | 0 | 0 |
| 2026-11-14 18:00:00 | 22 | 587 ms | 609 ms | 0 | 0 |
| 2026-11-14 21:00:00 | 23 | 676 ms | 2 593 ms | 0 | 0 |
| 2026-11-15 00:00:00 | 22 | 588 ms | 604 ms | 0 | 0 |
| 2026-11-15 03:00:00 | 23 | 589 ms | 609 ms | 0 | 0 |
| 2026-11-15 06:00:00 | 22 | 588 ms | 601 ms | 0 | 0 |
| 2026-11-15 09:00:00 | 23 | 588 ms | 604 ms | 0 | 0 |
| 2026-11-15 12:00:00 | 22 | 590 ms | 633 ms | 0 | 0 |
| 2026-11-15 15:00:00 | 23 | 591 ms | 607 ms | 0 | 0 |
| 2026-11-15 18:00:00 | 22 | 593 ms | 615 ms | 0 | 0 |
| 2026-11-15 21:00:00 | 23 | 590 ms | 605 ms | 0 | 0 |
| 2026-11-16 00:00:00 | 22 | 589 ms | 607 ms | 0 | 0 |
| 2026-11-16 03:00:00 | 23 | 607 ms | 694 ms | 0 | 0 |
| 2026-11-16 06:00:00 | 22 | 616 ms | 668 ms | 0 | 0 |
| 2026-11-16 09:00:00 | 23 | 652 ms | 1 057 ms | 0 | 0 |
| 2026-11-16 12:00:00 | 22 | 653 ms | 1 159 ms | 0 | 0 |
| 2026-11-16 15:00:00 | 23 | 638 ms | 785 ms | 0 | 0 |
| 2026-11-16 18:00:00 | 23 | 619 ms | 642 ms | 0 | 0 |
| 2026-11-16 21:00:00 | 22 | 613 ms | 633 ms | 0 | 0 |
| 2026-11-17 00:00:00 | 23 | 614 ms | 634 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 22 | 612 ms | 629 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 24 | 627 ms | 872 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 23 | 626 ms | 677 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 23 | 623 ms | 694 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 22 | 625 ms | 728 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 22 | 618 ms | 654 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 15 | 616 ms | 633 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.