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
Banks
Is ВТБ 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: 493 ms
Response time
493 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 12:00:00 | 22 | 539 ms | 1 509 ms | 0 | 0 |
| 2026-11-09 15:00:00 | 22 | 569 ms | 1 535 ms | 0 | 0 |
| 2026-11-09 18:00:00 | 23 | 594 ms | 1 235 ms | 0 | 0 |
| 2026-11-09 21:00:00 | 22 | 434 ms | 1 079 ms | 0 | 0 |
| 2026-11-10 00:00:00 | 23 | 405 ms | 609 ms | 0 | 0 |
| 2026-11-10 03:00:00 | 22 | 381 ms | 502 ms | 0 | 0 |
| 2026-11-10 06:00:00 | 23 | 467 ms | 1 174 ms | 0 | 0 |
| 2026-11-10 09:00:00 | 23 | 956 ms | 2 445 ms | 0 | 0 |
| 2026-11-10 12:00:00 | 22 | 939 ms | 2 177 ms | 0 | 0 |
| 2026-11-10 15:00:00 | 23 | 603 ms | 1 733 ms | 0 | 0 |
| 2026-11-10 18:00:00 | 22 | 571 ms | 1 085 ms | 0 | 0 |
| 2026-11-10 21:00:00 | 23 | 380 ms | 749 ms | 0 | 0 |
| 2026-11-11 00:00:00 | 22 | 389 ms | 532 ms | 0 | 0 |
| 2026-11-11 03:00:00 | 23 | 404 ms | 654 ms | 0 | 0 |
| 2026-11-11 06:00:00 | 22 | 450 ms | 1 333 ms | 0 | 0 |
| 2026-11-11 09:00:00 | 23 | 475 ms | 1 129 ms | 0 | 0 |
| 2026-11-11 12:00:00 | 22 | 528 ms | 1 158 ms | 0 | 0 |
| 2026-11-11 15:00:00 | 23 | 455 ms | 1 252 ms | 0 | 0 |
| 2026-11-11 18:00:00 | 22 | 628 ms | 1 952 ms | 0 | 0 |
| 2026-11-11 21:00:00 | 23 | 404 ms | 545 ms | 0 | 0 |
| 2026-11-12 00:00:00 | 22 | 378 ms | 551 ms | 0 | 0 |
| 2026-11-12 03:00:00 | 23 | 363 ms | 522 ms | 0 | 0 |
| 2026-11-12 06:00:00 | 22 | 492 ms | 1 263 ms | 0 | 0 |
| 2026-11-12 09:00:00 | 23 | 552 ms | 1 389 ms | 0 | 0 |
| 2026-11-12 12:00:00 | 22 | 657 ms | 1 395 ms | 0 | 0 |
| 2026-11-12 15:00:00 | 22 | 589 ms | 1 192 ms | 0 | 0 |
| 2026-11-12 18:00:00 | 23 | 432 ms | 1 213 ms | 0 | 0 |
| 2026-11-12 21:00:00 | 22 | 395 ms | 696 ms | 0 | 0 |
| 2026-11-13 00:00:00 | 23 | 409 ms | 480 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 22 | 374 ms | 497 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 23 | 373 ms | 1 012 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 22 | 726 ms | 4 627 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 23 | 545 ms | 1 382 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 22 | 627 ms | 1 325 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 23 | 549 ms | 1 280 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 22 | 441 ms | 950 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 370 ms | 520 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 22 | 396 ms | 733 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 23 | 472 ms | 1 215 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 8 | 502 ms | 1 253 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.
06:59
07:07
07:15
07:23
07:31
07:39
07:47
07:55
08:03
08:11
08:19
08:27
08:35
08:43
08:51
08:59
09:07
09:15
09:23
09:31
09:39
09:47
09:55
10:03
Last check
2026-11-14 10:03:38
HTTP
200
Response time
493 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 ВТБ down?
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.
Additional diagnostics
Ping · Website availability · Website monitoring · All service outages
Frequently asked questions
Is ВТБ down right now?
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.
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.