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: 792 ms
Response time
792 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 | 23 | 1 121 ms | 5 025 ms | 0 | 0 |
| 2026-11-09 15:00:00 | 22 | 1 092 ms | 2 860 ms | 0 | 0 |
| 2026-11-09 18:00:00 | 23 | 971 ms | 2 095 ms | 0 | 0 |
| 2026-11-09 21:00:00 | 22 | 854 ms | 1 007 ms | 0 | 0 |
| 2026-11-10 00:00:00 | 23 | 859 ms | 1 709 ms | 0 | 0 |
| 2026-11-10 03:00:00 | 22 | 893 ms | 2 799 ms | 0 | 0 |
| 2026-11-10 06:00:00 | 23 | 820 ms | 1 263 ms | 0 | 0 |
| 2026-11-10 09:00:00 | 22 | 927 ms | 1 281 ms | 0 | 0 |
| 2026-11-10 12:00:00 | 23 | 1 032 ms | 1 866 ms | 0 | 0 |
| 2026-11-10 15:00:00 | 22 | 1 113 ms | 4 838 ms | 0 | 0 |
| 2026-11-10 18:00:00 | 23 | 890 ms | 1 260 ms | 0 | 0 |
| 2026-11-10 21:00:00 | 22 | 875 ms | 1 104 ms | 0 | 0 |
| 2026-11-11 00:00:00 | 23 | 846 ms | 1 826 ms | 0 | 0 |
| 2026-11-11 03:00:00 | 22 | 765 ms | 1 001 ms | 0 | 0 |
| 2026-11-11 06:00:00 | 23 | 813 ms | 1 061 ms | 0 | 0 |
| 2026-11-11 09:00:00 | 22 | 1 035 ms | 2 971 ms | 0 | 0 |
| 2026-11-11 12:00:00 | 23 | 891 ms | 1 265 ms | 0 | 0 |
| 2026-11-11 15:00:00 | 22 | 924 ms | 1 360 ms | 0 | 0 |
| 2026-11-11 18:00:00 | 23 | 820 ms | 1 040 ms | 0 | 0 |
| 2026-11-11 21:00:00 | 23 | 816 ms | 1 742 ms | 0 | 0 |
| 2026-11-12 00:00:00 | 22 | 854 ms | 2 740 ms | 0 | 0 |
| 2026-11-12 03:00:00 | 23 | 776 ms | 1 177 ms | 0 | 0 |
| 2026-11-12 06:00:00 | 22 | 843 ms | 1 732 ms | 0 | 0 |
| 2026-11-12 09:00:00 | 22 | 936 ms | 1 958 ms | 0 | 0 |
| 2026-11-12 12:00:00 | 23 | 980 ms | 3 055 ms | 0 | 0 |
| 2026-11-12 15:00:00 | 22 | 865 ms | 1 098 ms | 0 | 0 |
| 2026-11-12 18:00:00 | 23 | 820 ms | 1 186 ms | 0 | 0 |
| 2026-11-12 21:00:00 | 22 | 802 ms | 1 038 ms | 0 | 0 |
| 2026-11-13 00:00:00 | 22 | 790 ms | 1 027 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 23 | 793 ms | 1 340 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 22 | 788 ms | 928 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 23 | 875 ms | 1 100 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 22 | 898 ms | 1 331 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 23 | 1 008 ms | 2 838 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 22 | 886 ms | 2 267 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 23 | 808 ms | 1 067 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 852 ms | 2 730 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 22 | 749 ms | 868 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 23 | 866 ms | 2 740 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 8 | 895 ms | 1 860 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.
07:00
07:08
07:16
07:24
07:32
07:40
07:47
07:56
08:03
08:11
08:19
08:27
08:36
08:44
08:51
08:59
09:07
09:15
09:24
09:31
09:39
09:47
09:56
10:03
Last check
2026-11-14 10:03:52
HTTP
200
Response time
792 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.