Telegram faces major outage affecting Asia and Oceania

Telegram’s DC5 data center in Singapore went down on September 8, disrupting service for users spread across East Asia, Southeast Asia, and Oceania. The outage started around 10:20 AM local time and peaked with nearly 4,000 issue reports from Singapore alone.

The company has not issued any official statement about what caused the failure.

Who got hit and how hard

Singapore bore the brunt of the disruption, but the damage spread well beyond the city-state. Indonesia logged roughly 1,284 reports at peak, the Philippines saw 933, India recorded 725, Malaysia contributed 544, Vietnam added 530, and Thailand rounded things out with 253.

The nature of the problems broke down roughly along these lines: about 50% of reports pointed to general app functionality failures, 40% involved messaging not working, and around 5% were login issues. In practical terms, that meant users couldn’t send or receive messages, couldn’t load conversations, or in some cases couldn’t even get into the app at all.

Services started recovering by approximately 11:30 AM, putting the total disruption window at just over an hour.

Critically, this was not a global event. Telegram’s other four data centers continued operating normally, which points squarely at DC5-specific infrastructure as the culprit rather than any platform-wide issue.

DC5 has a reputation problem

Telegram operates five main data centers globally, and DC5, the Singapore facility, serves as the primary hub for East and Southeast Asia along with Oceania.

DC5 also has a well-documented history of instability. The data center has been observed experiencing regional connectivity problems with enough frequency that dedicated monitoring has sprung up in various user communities. Chinese-language Telegram groups, in particular, have developed informal tracking systems to keep tabs on DC5’s status, a sign that outages are common enough to warrant standing vigilance.

Accounts registered with certain regional phone prefixes have reportedly been disproportionately affected by past DC5 disruptions, suggesting that the routing architecture may create uneven vulnerability depending on where a user originally signed up.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.