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-12 19:00:00 | 7 | 469 ms | 983 ms | 0 | 0 |
| 2026-11-12 20:00:00 | 8 | 501 ms | 1 213 ms | 0 | 0 |
| 2026-11-12 21:00:00 | 7 | 377 ms | 696 ms | 0 | 0 |
| 2026-11-12 22:00:00 | 8 | 438 ms | 486 ms | 0 | 0 |
| 2026-11-12 23:00:00 | 7 | 365 ms | 533 ms | 0 | 0 |
| 2026-11-13 00:00:00 | 8 | 383 ms | 469 ms | 0 | 0 |
| 2026-11-13 01:00:00 | 7 | 421 ms | 471 ms | 0 | 0 |
| 2026-11-13 02:00:00 | 8 | 426 ms | 480 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 7 | 369 ms | 476 ms | 0 | 0 |
| 2026-11-13 04:00:00 | 8 | 375 ms | 497 ms | 0 | 0 |
| 2026-11-13 05:00:00 | 7 | 378 ms | 450 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 8 | 365 ms | 503 ms | 0 | 0 |
| 2026-11-13 07:00:00 | 7 | 341 ms | 456 ms | 0 | 0 |
| 2026-11-13 08:00:00 | 8 | 410 ms | 1 012 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 7 | 500 ms | 848 ms | 0 | 0 |
| 2026-11-13 10:00:00 | 8 | 416 ms | 498 ms | 0 | 0 |
| 2026-11-13 11:00:00 | 7 | 1 308 ms | 4 627 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 8 | 701 ms | 1 042 ms | 0 | 0 |
| 2026-11-13 13:00:00 | 7 | 586 ms | 1 382 ms | 0 | 0 |
| 2026-11-13 14:00:00 | 8 | 354 ms | 474 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 7 | 579 ms | 1 189 ms | 0 | 0 |
| 2026-11-13 16:00:00 | 8 | 649 ms | 1 215 ms | 0 | 0 |
| 2026-11-13 17:00:00 | 7 | 649 ms | 1 325 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 8 | 686 ms | 1 280 ms | 0 | 0 |
| 2026-11-13 19:00:00 | 7 | 443 ms | 935 ms | 0 | 0 |
| 2026-11-13 20:00:00 | 8 | 505 ms | 1 107 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 7 | 487 ms | 950 ms | 0 | 0 |
| 2026-11-13 22:00:00 | 8 | 402 ms | 742 ms | 0 | 0 |
| 2026-11-13 23:00:00 | 7 | 438 ms | 767 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 8 | 340 ms | 486 ms | 0 | 0 |
| 2026-11-14 01:00:00 | 7 | 401 ms | 520 ms | 0 | 0 |
| 2026-11-14 02:00:00 | 8 | 374 ms | 493 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 7 | 401 ms | 467 ms | 0 | 0 |
| 2026-11-14 04:00:00 | 8 | 381 ms | 733 ms | 0 | 0 |
| 2026-11-14 05:00:00 | 7 | 409 ms | 477 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 8 | 310 ms | 438 ms | 0 | 0 |
| 2026-11-14 07:00:00 | 7 | 572 ms | 1 215 ms | 0 | 0 |
| 2026-11-14 08:00:00 | 8 | 547 ms | 1 192 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 7 | 503 ms | 1 253 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.