How to interpret the monitoring status
Technical measurements reflect observations from the NexIP monitoring location. A failed or restricted request alone does not confirm a widespread outage.
Telecom operators
Автоматический запрос из точки NexIP ограничен. Массовый сбой не подтверждён.
Technical measurements reflect observations from the NexIP monitoring location. A failed or restricted request alone does not confirm a widespread outage.
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-17 03:00:00 | 4 | 114 ms | 118 ms | 0 | 4 |
| 2026-11-17 03:30:00 | 4 | 115 ms | 119 ms | 0 | 4 |
| 2026-11-17 04:00:00 | 3 | 111 ms | 114 ms | 0 | 3 |
| 2026-11-17 04:30:00 | 4 | 115 ms | 121 ms | 0 | 4 |
| 2026-11-17 05:00:00 | 4 | 112 ms | 114 ms | 0 | 4 |
| 2026-11-17 05:30:00 | 4 | 114 ms | 115 ms | 0 | 4 |
| 2026-11-17 06:00:00 | 3 | 112 ms | 115 ms | 0 | 3 |
| 2026-11-17 06:30:00 | 4 | 115 ms | 120 ms | 0 | 4 |
| 2026-11-17 07:00:00 | 4 | 115 ms | 123 ms | 0 | 4 |
| 2026-11-17 07:30:00 | 4 | 114 ms | 118 ms | 0 | 4 |
| 2026-11-17 08:00:00 | 4 | 115 ms | 120 ms | 0 | 4 |
| 2026-11-17 08:30:00 | 4 | 113 ms | 114 ms | 0 | 4 |
| 2026-11-17 09:00:00 | 4 | 113 ms | 115 ms | 0 | 4 |
| 2026-11-17 09:30:00 | 4 | 119 ms | 125 ms | 0 | 4 |
| 2026-11-17 10:00:00 | 4 | 117 ms | 118 ms | 0 | 4 |
| 2026-11-17 10:30:00 | 3 | 118 ms | 126 ms | 0 | 3 |
| 2026-11-17 11:00:00 | 4 | 114 ms | 116 ms | 0 | 4 |
| 2026-11-17 11:30:00 | 4 | 115 ms | 121 ms | 0 | 4 |
| 2026-11-17 12:00:00 | 4 | 117 ms | 119 ms | 0 | 4 |
| 2026-11-17 12:30:00 | 4 | 120 ms | 124 ms | 0 | 4 |
| 2026-11-17 13:00:00 | 3 | 115 ms | 119 ms | 0 | 3 |
| 2026-11-17 13:30:00 | 4 | 117 ms | 123 ms | 0 | 4 |
| 2026-11-17 14:00:00 | 4 | 116 ms | 118 ms | 0 | 4 |
| 2026-11-17 14:30:00 | 4 | 118 ms | 126 ms | 0 | 4 |
| 2026-11-17 15:00:00 | 3 | 117 ms | 120 ms | 0 | 3 |
| 2026-11-17 15:30:00 | 4 | 114 ms | 119 ms | 0 | 4 |
| 2026-11-17 16:00:00 | 4 | 114 ms | 117 ms | 0 | 4 |
| 2026-11-17 16:30:00 | 4 | 119 ms | 133 ms | 0 | 4 |
| 2026-11-17 17:00:00 | 3 | 117 ms | 126 ms | 0 | 3 |
| 2026-11-17 17:30:00 | 4 | 117 ms | 121 ms | 0 | 4 |
| 2026-11-17 18:00:00 | 4 | 116 ms | 117 ms | 0 | 4 |
| 2026-11-17 18:30:00 | 4 | 118 ms | 122 ms | 0 | 4 |
| 2026-11-17 19:00:00 | 3 | 121 ms | 121 ms | 0 | 3 |
| 2026-11-17 19:30:00 | 4 | 117 ms | 124 ms | 0 | 4 |
| 2026-11-17 20:00:00 | 4 | 116 ms | 119 ms | 0 | 4 |
| 2026-11-17 20:30:00 | 3 | 115 ms | 119 ms | 0 | 3 |
| 2026-11-17 21:00:00 | 4 | 116 ms | 124 ms | 0 | 4 |
| 2026-11-17 21:30:00 | 4 | 113 ms | 116 ms | 0 | 4 |
| 2026-11-17 22:00:00 | 3 | 118 ms | 125 ms | 0 | 3 |
| 2026-11-17 22:30:00 | 4 | 117 ms | 122 ms | 0 | 4 |
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.