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.
Messengers
Техническая проверка выявила ошибку или задержку. Массовый сбой не подтверждён.
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
Мониторинг доступности сервиса Viber, пользовательских сигналов и технических проверок 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 19:20:00 | 1 | 2 293 ms | 2 293 ms | 0 | 0 |
| 2026-11-17 19:30:00 | 1 | 6 038 ms | 6 038 ms | 0 | 0 |
| 2026-11-17 19:40:00 | 1 | 6 251 ms | 6 251 ms | 0 | 0 |
| 2026-11-17 19:45:00 | 1 | 5 976 ms | 5 976 ms | 0 | 0 |
| 2026-11-17 19:55:00 | 1 | 5 004 ms | 5 004 ms | 0 | 0 |
| 2026-11-17 20:05:00 | 1 | 2 370 ms | 2 370 ms | 0 | 0 |
| 2026-11-17 20:10:00 | 1 | 2 106 ms | 2 106 ms | 0 | 0 |
| 2026-11-17 20:20:00 | 1 | 2 192 ms | 2 192 ms | 0 | 0 |
| 2026-11-17 20:25:00 | 1 | 2 217 ms | 2 217 ms | 0 | 0 |
| 2026-11-17 20:35:00 | 1 | 5 005 ms | 5 005 ms | 0 | 0 |
| 2026-11-17 20:45:00 | 1 | 2 262 ms | 2 262 ms | 0 | 0 |
| 2026-11-17 20:50:00 | 1 | 5 988 ms | 5 988 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 1 | 2 220 ms | 2 220 ms | 0 | 0 |
| 2026-11-17 21:10:00 | 1 | 5 006 ms | 5 006 ms | 0 | 0 |
| 2026-11-17 21:15:00 | 1 | 2 453 ms | 2 453 ms | 0 | 0 |
| 2026-11-17 21:25:00 | 1 | 2 243 ms | 2 243 ms | 0 | 0 |
| 2026-11-17 21:30:00 | 1 | 6 000 ms | 6 000 ms | 0 | 0 |
| 2026-11-17 21:40:00 | 1 | 2 202 ms | 2 202 ms | 0 | 0 |
| 2026-11-17 21:50:00 | 1 | 2 184 ms | 2 184 ms | 0 | 0 |
| 2026-11-17 21:55:00 | 1 | 5 003 ms | 5 003 ms | 0 | 0 |
| 2026-11-17 22:05:00 | 1 | 2 250 ms | 2 250 ms | 0 | 0 |
| 2026-11-17 22:10:00 | 1 | 5 005 ms | 5 005 ms | 0 | 0 |
| 2026-11-17 22:20:00 | 1 | 5 965 ms | 5 965 ms | 0 | 0 |
| 2026-11-17 22:30:00 | 1 | 2 451 ms | 2 451 ms | 0 | 0 |
| 2026-11-17 22:35:00 | 1 | 5 996 ms | 5 996 ms | 0 | 0 |
| 2026-11-17 22:45:00 | 1 | 2 233 ms | 2 233 ms | 0 | 0 |
| 2026-11-17 22:55:00 | 1 | 5 990 ms | 5 990 ms | 0 | 0 |
| 2026-11-17 23:00:00 | 1 | 6 073 ms | 6 073 ms | 0 | 0 |
| 2026-11-17 23:10:00 | 1 | 2 277 ms | 2 277 ms | 0 | 0 |
| 2026-11-17 23:15:00 | 1 | 2 192 ms | 2 192 ms | 0 | 0 |
| 2026-11-17 23:25:00 | 1 | 5 005 ms | 5 005 ms | 0 | 0 |
| 2026-11-17 23:35:00 | 1 | 2 262 ms | 2 262 ms | 0 | 0 |
| 2026-11-17 23:40:00 | 1 | 5 982 ms | 5 982 ms | 0 | 0 |
| 2026-11-17 23:50:00 | 1 | 5 966 ms | 5 966 ms | 0 | 0 |
| 2026-11-17 23:55:00 | 1 | 2 173 ms | 2 173 ms | 0 | 0 |
| 2026-11-18 00:05:00 | 1 | 2 207 ms | 2 207 ms | 0 | 0 |
| 2026-11-18 00:15:00 | 1 | 2 189 ms | 2 189 ms | 0 | 0 |
| 2026-11-18 00:20:00 | 1 | 2 240 ms | 2 240 ms | 0 | 0 |
| 2026-11-18 00:30:00 | 1 | 2 246 ms | 2 246 ms | 0 | 0 |
| 2026-11-18 00:35:00 | 1 | 5 004 ms | 5 004 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 Viber, 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 Viber 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.