T-Bank Hit by Outage: DownDetector Logs 3.3K Complaints in 24 Hours

T-Bank suffered an outage on Thursday, 8 October. According to DownDetector, users filed more than 3.3K complaints about problems over the past 24 hours, and 3.1K of them fell within the last hour. About 94% of the reports are concentrated in a short window. A chart shaped like this is typically a sign of a sudden collapse in availability: everything was working, then it suddenly stopped.

What is known so far

There is a single data source: DownDetector, a service that aggregates user complaints about online services. The source data contains no official comment from the bank, no technical description of the incident and no estimate of when service will be restored. All that is clear for now is that thousands of people noticed problems accessing the app, and that their number grew very quickly.

Key figures:

• data source: DownDetector;
• complaints over the past 24 hours: more than 3.3K;
• complaints over the last hour: 3.1K;
• share of the last hour in the daily total: about 94%;
• time of publication: 8 October 2026, 13:49 UTC (16:49 Moscow time);
• cause of the outage, its duration and the affected functions: not disclosed.

How to read these numbers

DownDetector counts not the people affected, but the people who complained. Those are different quantities. Some users simply restart the app and wait, some call support, and many have never heard of an aggregator service at all. For a bank with a customer base in the millions, 3.3K complaints alone do not prove a mass failure. The dynamics, however, say a lot: when almost all reports arrive within an hour, we are most likely looking at a single event rather than an accumulation of minor faults.

What exactly happened is anyone's guess for now. A mobile bank is a long chain: authentication, core access, anti-fraud, push notifications, CDN, third-party providers. A failure in any link looks the same to the customer: the app won't open or won't let them in. That is why complaints alone cannot distinguish a bad release from an overload or a failure at an external contractor. It is worth waiting for the bank's official account.

The incident is especially visible for T-Bank because of its business model. The bank has no traditional branch network, and its app and website serve as the main service channel. When that channel is unavailable, customers have nothing to replace it with on the spot. They are left with phone calls and chat, which are themselves overloaded at such moments.

What customers and businesses should do until the outage is fixed

For an ordinary user, the checklist is simple. Check whether card payments work in stores and through SBP (the Faster Payments System): sometimes an outage affects only app login while payment transactions go through. Don't enter your password or code many times in a row, so you don't get locked out. If you urgently need money, another bank's card or a little cash will come in handy. Look for information about the outage only in the bank's official channels. Scammers tend to become active during such hours, sending out "access recovery instructions" with links.

For companies that accept payments or pay salaries through T-Bank, the incident is a reminder of basic hygiene. You need a backup settlement account at another bank, a clear procedure for when the main channel is unavailable, and pre-agreed timeframes after which a payment delay counts as an abnormal situation.

For the bank itself, the test starts now: how quickly it names the cause, which functions were affected, and whether customers' money was touched. A transparent post-incident review often preserves trust better than silence, even when the outage turns out to be short.