21–25 окт. 2026 г.
99 ч 44 мин
A provider-quality filter switched itself on at its default date and emptied two selection pools, and our hosted proxy service began churning through short-lived connections faster than the database could serve them. For two days connections failed or stalled for many people while database storage grew with the churn, until on Oct 23 a logging fault filled the disk and the platform was down for 16 hours, then 6 more for the storage expansion. That evening the same churn jammed payment reservations, and for about five hours apps could find providers but not send traffic.
Начало 21 окт., 00:00 UTCКонец 25 окт., 03:44 UTC
- Полный сбой23 ч 32 мин
- Крупный сбой14 ч 04 мин
- Частичный сбой43 ч 27 мин
- Ухудшение17 ч 38 мин
Читать разбор →19 окт. 2026 г.
9 ч 16 мин
The pools that connect our servers to the database stalled and could not refill. A cleanup job then mistook the stalled servers for dead ones and removed them, and 97% of providers dropped off the network for almost three hours.
Начало 19 окт., 09:56 UTCКонец 19 окт., 19:12 UTC
- Полный сбой2 ч 47 мин
- Крупный сбой16 мин
- Частичный сбой26 мин
- Ухудшение4 ч 05 мин
Читать разбор →10–13 окт. 2026 г.
80 ч 19 мин
Our main database ran at its limit for three days, and every timeout added retries and more load. While it was overloaded, four separate failures hit users: a new connection check that disconnected healthy providers, a load-balancer collapse, a key rotation that broke new sign-ins, and a stalled connection pooler.
Начало 10 окт., 00:22 UTCКонец 13 окт., 08:41 UTC
- Полный сбой2 ч 10 мин
- Крупный сбой35 ч 35 мин
- Частичный сбой19 ч 34 мин
- Ухудшение23 ч
Читать разбор →