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-13 14:30:00 | 4 | 330 ms | 433 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 3 | 407 ms | 473 ms | 0 | 0 |
| 2026-11-13 15:30:00 | 4 | 708 ms | 1 189 ms | 0 | 0 |
| 2026-11-13 16:00:00 | 4 | 596 ms | 1 209 ms | 0 | 0 |
| 2026-11-13 16:30:00 | 4 | 701 ms | 1 215 ms | 0 | 0 |
| 2026-11-13 17:00:00 | 3 | 599 ms | 658 ms | 0 | 0 |
| 2026-11-13 17:30:00 | 4 | 687 ms | 1 325 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 4 | 546 ms | 914 ms | 0 | 0 |
| 2026-11-13 18:30:00 | 4 | 826 ms | 1 280 ms | 0 | 0 |
| 2026-11-13 19:00:00 | 3 | 556 ms | 935 ms | 0 | 0 |
| 2026-11-13 19:30:00 | 4 | 358 ms | 496 ms | 0 | 0 |
| 2026-11-13 20:00:00 | 4 | 570 ms | 1 107 ms | 0 | 0 |
| 2026-11-13 20:30:00 | 4 | 440 ms | 622 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 3 | 561 ms | 950 ms | 0 | 0 |
| 2026-11-13 21:30:00 | 4 | 432 ms | 481 ms | 0 | 0 |
| 2026-11-13 22:00:00 | 4 | 485 ms | 742 ms | 0 | 0 |
| 2026-11-13 22:30:00 | 4 | 320 ms | 432 ms | 0 | 0 |
| 2026-11-13 23:00:00 | 3 | 397 ms | 467 ms | 0 | 0 |
| 2026-11-13 23:30:00 | 4 | 469 ms | 767 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 4 | 419 ms | 486 ms | 0 | 0 |
| 2026-11-14 00:30:00 | 4 | 261 ms | 274 ms | 0 | 0 |
| 2026-11-14 01:00:00 | 3 | 405 ms | 475 ms | 0 | 0 |
| 2026-11-14 01:30:00 | 4 | 397 ms | 520 ms | 0 | 0 |
| 2026-11-14 02:00:00 | 4 | 381 ms | 493 ms | 0 | 0 |
| 2026-11-14 02:30:00 | 4 | 366 ms | 467 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 3 | 409 ms | 467 ms | 0 | 0 |
| 2026-11-14 03:30:00 | 4 | 395 ms | 439 ms | 0 | 0 |
| 2026-11-14 04:00:00 | 4 | 321 ms | 444 ms | 0 | 0 |
| 2026-11-14 04:30:00 | 4 | 441 ms | 733 ms | 0 | 0 |
| 2026-11-14 05:00:00 | 3 | 458 ms | 474 ms | 0 | 0 |
| 2026-11-14 05:30:00 | 4 | 372 ms | 477 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 4 | 346 ms | 438 ms | 0 | 0 |
| 2026-11-14 06:30:00 | 4 | 273 ms | 285 ms | 0 | 0 |
| 2026-11-14 07:00:00 | 3 | 479 ms | 512 ms | 0 | 0 |
| 2026-11-14 07:30:00 | 4 | 641 ms | 1 215 ms | 0 | 0 |
| 2026-11-14 08:00:00 | 4 | 444 ms | 661 ms | 0 | 0 |
| 2026-11-14 08:30:00 | 4 | 650 ms | 1 192 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 3 | 699 ms | 1 253 ms | 0 | 0 |
| 2026-11-14 09:30:00 | 4 | 357 ms | 474 ms | 0 | 0 |
| 2026-11-14 10:00:00 | 1 | 493 ms | 493 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.