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-13 14:30:00 | 3 | 883 ms | 961 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 4 | 959 ms | 1 183 ms | 0 | 0 |
| 2026-11-13 15:30:00 | 4 | 1 332 ms | 2 838 ms | 0 | 0 |
| 2026-11-13 16:00:00 | 4 | 862 ms | 965 ms | 0 | 0 |
| 2026-11-13 16:30:00 | 3 | 950 ms | 996 ms | 0 | 0 |
| 2026-11-13 17:00:00 | 4 | 923 ms | 1 060 ms | 0 | 0 |
| 2026-11-13 17:30:00 | 4 | 1 010 ms | 1 200 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 4 | 770 ms | 785 ms | 0 | 0 |
| 2026-11-13 18:30:00 | 3 | 1 008 ms | 1 334 ms | 0 | 0 |
| 2026-11-13 19:00:00 | 4 | 753 ms | 833 ms | 0 | 0 |
| 2026-11-13 19:30:00 | 4 | 820 ms | 1 076 ms | 0 | 0 |
| 2026-11-13 20:00:00 | 4 | 1 164 ms | 2 267 ms | 0 | 0 |
| 2026-11-13 20:30:00 | 3 | 817 ms | 899 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 4 | 817 ms | 888 ms | 0 | 0 |
| 2026-11-13 21:30:00 | 4 | 836 ms | 1 034 ms | 0 | 0 |
| 2026-11-13 22:00:00 | 4 | 771 ms | 793 ms | 0 | 0 |
| 2026-11-13 22:30:00 | 3 | 801 ms | 865 ms | 0 | 0 |
| 2026-11-13 23:00:00 | 4 | 884 ms | 1 067 ms | 0 | 0 |
| 2026-11-13 23:30:00 | 4 | 739 ms | 814 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 4 | 737 ms | 757 ms | 0 | 0 |
| 2026-11-14 00:30:00 | 3 | 805 ms | 906 ms | 0 | 0 |
| 2026-11-14 01:00:00 | 4 | 809 ms | 910 ms | 0 | 0 |
| 2026-11-14 01:30:00 | 4 | 746 ms | 778 ms | 0 | 0 |
| 2026-11-14 02:00:00 | 4 | 778 ms | 818 ms | 0 | 0 |
| 2026-11-14 02:30:00 | 4 | 1 224 ms | 2 730 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 3 | 789 ms | 868 ms | 0 | 0 |
| 2026-11-14 03:30:00 | 4 | 749 ms | 805 ms | 0 | 0 |
| 2026-11-14 04:00:00 | 4 | 734 ms | 772 ms | 0 | 0 |
| 2026-11-14 04:30:00 | 3 | 746 ms | 773 ms | 0 | 0 |
| 2026-11-14 05:00:00 | 4 | 751 ms | 779 ms | 0 | 0 |
| 2026-11-14 05:30:00 | 4 | 735 ms | 756 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 4 | 738 ms | 753 ms | 0 | 0 |
| 2026-11-14 06:30:00 | 3 | 830 ms | 967 ms | 0 | 0 |
| 2026-11-14 07:00:00 | 4 | 778 ms | 852 ms | 0 | 0 |
| 2026-11-14 07:30:00 | 4 | 1 310 ms | 2 740 ms | 0 | 0 |
| 2026-11-14 08:00:00 | 4 | 752 ms | 786 ms | 0 | 0 |
| 2026-11-14 08:30:00 | 4 | 780 ms | 856 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 3 | 736 ms | 791 ms | 0 | 0 |
| 2026-11-14 09:30:00 | 4 | 1 040 ms | 1 860 ms | 0 | 0 |
| 2026-11-14 10:00:00 | 1 | 792 ms | 792 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.