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.
← All services
Social networks
Is VK down? Current status and outages
Доступен из точки NexIPHTTP-проверка из точки NexIP успешна. Доступность из всех регионов не подтверждена.
Understanding the metrics
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
Current state
Outage score
0/100
Statistical assessment
User signals
0
unique in the last 15 minutes
Automatic check
Available
Response: 405 ms
Response time
405 ms
Last local automatic check
User reports over the last 24 hours
Reports submitted to NexIP. One report does not prove a widespread outage.
Reports in selected period
0
No reports during this period.
30-minute intervals · Moscow time · actual dataLast 7 days
Recent incidents
No confirmed large-scale incidents were recorded during the last 7 days.
Observation points
Regional checks
Remote observation points are not connected yet.
Observation history
Latest automatic checks
OUTAGE INTELLIGENCE / SERVICE PROBES
Check history and reliability
Actual NexIP primary probe measurements, not user reports
Full-period overviewAll observations
Latest 40 intervals · CSV includes entire selection
| Time (server) | Checks | Average | Peak | Down | Blocked |
|---|---|---|---|---|---|
| 2026-11-09 06:00:00 | 22 | 430 ms | 483 ms | 0 | 0 |
| 2026-11-09 09:00:00 | 23 | 438 ms | 529 ms | 0 | 0 |
| 2026-11-09 12:00:00 | 22 | 438 ms | 543 ms | 0 | 0 |
| 2026-11-09 15:00:00 | 22 | 436 ms | 524 ms | 0 | 0 |
| 2026-11-09 18:00:00 | 23 | 460 ms | 736 ms | 0 | 0 |
| 2026-11-09 21:00:00 | 22 | 427 ms | 503 ms | 0 | 0 |
| 2026-11-10 00:00:00 | 23 | 414 ms | 457 ms | 0 | 0 |
| 2026-11-10 03:00:00 | 22 | 416 ms | 478 ms | 0 | 0 |
| 2026-11-10 06:00:00 | 23 | 428 ms | 583 ms | 0 | 0 |
| 2026-11-10 09:00:00 | 23 | 436 ms | 776 ms | 0 | 0 |
| 2026-11-10 12:00:00 | 22 | 425 ms | 491 ms | 0 | 0 |
| 2026-11-10 15:00:00 | 23 | 443 ms | 507 ms | 0 | 0 |
| 2026-11-10 18:00:00 | 22 | 430 ms | 539 ms | 0 | 0 |
| 2026-11-10 21:00:00 | 23 | 424 ms | 489 ms | 0 | 0 |
| 2026-11-11 00:00:00 | 22 | 401 ms | 481 ms | 0 | 0 |
| 2026-11-11 03:00:00 | 23 | 404 ms | 455 ms | 0 | 0 |
| 2026-11-11 06:00:00 | 22 | 421 ms | 520 ms | 0 | 0 |
| 2026-11-11 09:00:00 | 23 | 437 ms | 523 ms | 0 | 0 |
| 2026-11-11 12:00:00 | 22 | 427 ms | 511 ms | 0 | 0 |
| 2026-11-11 15:00:00 | 23 | 443 ms | 628 ms | 0 | 0 |
| 2026-11-11 18:00:00 | 22 | 436 ms | 592 ms | 0 | 0 |
| 2026-11-11 21:00:00 | 23 | 418 ms | 490 ms | 0 | 0 |
| 2026-11-12 00:00:00 | 22 | 399 ms | 447 ms | 0 | 0 |
| 2026-11-12 03:00:00 | 23 | 411 ms | 488 ms | 0 | 0 |
| 2026-11-12 06:00:00 | 22 | 413 ms | 493 ms | 0 | 0 |
| 2026-11-12 09:00:00 | 23 | 412 ms | 483 ms | 0 | 0 |
| 2026-11-12 12:00:00 | 22 | 433 ms | 526 ms | 0 | 0 |
| 2026-11-12 15:00:00 | 22 | 451 ms | 835 ms | 0 | 0 |
| 2026-11-12 18:00:00 | 23 | 437 ms | 520 ms | 0 | 0 |
| 2026-11-12 21:00:00 | 22 | 430 ms | 462 ms | 0 | 0 |
| 2026-11-13 00:00:00 | 23 | 418 ms | 470 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 22 | 412 ms | 449 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 23 | 422 ms | 483 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 22 | 447 ms | 563 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 23 | 441 ms | 526 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 22 | 436 ms | 493 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 23 | 455 ms | 546 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 22 | 431 ms | 508 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 416 ms | 475 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 9 | 417 ms | 451 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.
01:07
01:15
01:23
01:31
01:39
01:47
01:55
02:03
02:11
02:19
02:27
02:35
02:43
02:51
02:59
03:07
03:15
03:23
03:31
03:39
03:47
03:55
04:03
04:11
Last check
2026-11-14 04:11:30
HTTP
200
Response time
422 ms
Your signal
Having a problem with this service?
Tell us. Registration is not required. The same signal will not be counted repeatedly within a short period.
Community reviews
User opinions are separate from the technical outage status.
Your rating
No ratings yet
Leave a comment
Published comments
No comments yet.
Is VK down?
This page tracks the current observed status of VK, recent incidents, automated availability checks and available user reports. NexIP does not treat a single failed check as proof of a global outage.
Additional diagnostics
Ping · Website availability · Website monitoring · All service outages
Frequently asked questions
Is VK down right now?
NexIP shows the current observed status of VK using automated checks, incident data and available user signals. A local connection problem may differ from a large-scale outage.
Why can the service work for some users but not others?
Availability can differ by provider, region, DNS, routing, application version or service component. NexIP therefore separates observed signals from confirmed large-scale incidents.
How can I check whether the problem is on my side?
Check the host with Ping, website availability and your own connection. Comparing several independent checks helps distinguish a local problem from a wider outage.