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-14 04:50:00 | 1 | 707 ms | 707 ms | 0 | 0 |
| 2026-11-14 05:00:00 | 1 | 712 ms | 712 ms | 0 | 0 |
| 2026-11-14 05:05:00 | 1 | 779 ms | 779 ms | 0 | 0 |
| 2026-11-14 05:15:00 | 1 | 777 ms | 777 ms | 0 | 0 |
| 2026-11-14 05:20:00 | 1 | 736 ms | 736 ms | 0 | 0 |
| 2026-11-14 05:30:00 | 1 | 755 ms | 755 ms | 0 | 0 |
| 2026-11-14 05:35:00 | 1 | 756 ms | 756 ms | 0 | 0 |
| 2026-11-14 05:45:00 | 1 | 722 ms | 722 ms | 0 | 0 |
| 2026-11-14 05:55:00 | 1 | 707 ms | 707 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 1 | 752 ms | 752 ms | 0 | 0 |
| 2026-11-14 06:10:00 | 1 | 753 ms | 753 ms | 0 | 0 |
| 2026-11-14 06:20:00 | 1 | 711 ms | 711 ms | 0 | 0 |
| 2026-11-14 06:25:00 | 1 | 734 ms | 734 ms | 0 | 0 |
| 2026-11-14 06:35:00 | 1 | 822 ms | 822 ms | 0 | 0 |
| 2026-11-14 06:40:00 | 1 | 967 ms | 967 ms | 0 | 0 |
| 2026-11-14 06:50:00 | 1 | 700 ms | 700 ms | 0 | 0 |
| 2026-11-14 07:00:00 | 1 | 800 ms | 800 ms | 0 | 0 |
| 2026-11-14 07:05:00 | 1 | 852 ms | 852 ms | 0 | 0 |
| 2026-11-14 07:15:00 | 1 | 725 ms | 725 ms | 0 | 0 |
| 2026-11-14 07:20:00 | 1 | 733 ms | 733 ms | 0 | 0 |
| 2026-11-14 07:30:00 | 1 | 1 009 ms | 1 009 ms | 0 | 0 |
| 2026-11-14 07:40:00 | 1 | 767 ms | 767 ms | 0 | 0 |
| 2026-11-14 07:45:00 | 1 | 725 ms | 725 ms | 0 | 0 |
| 2026-11-14 07:55:00 | 1 | 2 740 ms | 2 740 ms | 0 | 0 |
| 2026-11-14 08:00:00 | 1 | 786 ms | 786 ms | 0 | 0 |
| 2026-11-14 08:10:00 | 1 | 765 ms | 765 ms | 0 | 0 |
| 2026-11-14 08:15:00 | 1 | 738 ms | 738 ms | 0 | 0 |
| 2026-11-14 08:25:00 | 1 | 717 ms | 717 ms | 0 | 0 |
| 2026-11-14 08:35:00 | 1 | 856 ms | 856 ms | 0 | 0 |
| 2026-11-14 08:40:00 | 1 | 735 ms | 735 ms | 0 | 0 |
| 2026-11-14 08:50:00 | 1 | 778 ms | 778 ms | 0 | 0 |
| 2026-11-14 08:55:00 | 1 | 749 ms | 749 ms | 0 | 0 |
| 2026-11-14 09:05:00 | 1 | 692 ms | 692 ms | 0 | 0 |
| 2026-11-14 09:15:00 | 1 | 726 ms | 726 ms | 0 | 0 |
| 2026-11-14 09:20:00 | 1 | 791 ms | 791 ms | 0 | 0 |
| 2026-11-14 09:30:00 | 1 | 772 ms | 772 ms | 0 | 0 |
| 2026-11-14 09:35:00 | 1 | 1 860 ms | 1 860 ms | 0 | 0 |
| 2026-11-14 09:45:00 | 1 | 754 ms | 754 ms | 0 | 0 |
| 2026-11-14 09:55:00 | 1 | 775 ms | 775 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.