Telegram Suffers Major Outage Across Singapore, India, and Southeast Asia

Messaging platform Telegram experienced a significant service disruption on Tuesday, leaving thousands of users across Singapore, India, and several Southeast Asian nations unable to send messages, load chats, or log into their accounts. The technical failure, which began during the early morning hours, triggered widespread tracking spikes on Downdetector as frustrated users encountered connection errors and apps stuck on loading screens.

While services gradually recovered for some regions by late morning, fluctuating connectivity patterns and secondary afternoon spikes demonstrated a prolonged unstable recovery phase. Independent user tracking and preliminary online reports connected the regional communications breakdown to potential instability surrounding Telegram’s DC5 data centre located in Singapore, though the company did not immediately issue an official technical explanation.

The service disruption manifested across multiple international time zones, prompting thousands of affected individuals to log status reports on Downdetector. Singapore bore the brunt of the initial wave, where problem reports climbed rapidly to nearly 4,000 at the peak shortly after 10:30 am local time, according to tracking data cited by The Straits Times. Earlier morning reports in Singapore had already crossed 1,500 complaints shortly after 10:20 am.

In India, outage numbers followed a distinct morning trajectory. According to NDTV Profit, the disruption in India began at approximately 7:58 am local time, with user complaints surging to a peak of 1,012 reports by 8:05 am. Jagran Josh documented a similar early morning high of 851 reports at 8:11 am, alongside international spillover that included 280 peak reports originating from the United States.

The technical malfunction extended far beyond Singapore and India, impacting broad swaths of Southeast Asia throughout the morning hours. According to Livemint and regional aggregation data, Indonesia recorded 1,284 peak problem reports, followed by the Philippines with 933 reports, and Malaysia with 544 complaints. Additional disruptions were logged in Vietnam with 530 reports and Thailand with 253 complaints at their respective peaks.

The widespread geographical footprint highlighted the heavy regional reliance on centralized server infrastructure. Because Telegram operates extensively via cloud-based architecture supporting group channels, direct messaging, and media sharing, a regional routing or server failure immediately cripples communication channels across multiple sovereign jurisdictions simultaneously.

Users grappling with the outage reported a consistent set of interface errors that rendered the application practically unusable for hours. According to NDTV Profit and Jagran Josh, approximately 57 percent of affected users experienced core application failures, while 31 percent specifically cited messaging transmission failures, and 7 to 9 percent encountered difficulties during the login process.

Commonly reported symptoms included failure to send or receive text and media files, chats failing to load, delayed notifications, and complete connection timeouts on Telegram Web. Many users took to social media platforms to report that the mobile application remained permanently stuck on an 'Updating…' screen while attempting to sync cloud data against unresponsive backend servers.

Amid the mounting communication blackout, technical observers and affected accounts on social media quickly pointed toward infrastructure nodes in Southeast Asia. An account named Defraud posted on X that Telegram's Asia servers, specifically designated as the DC5 infrastructure cluster in Singapore, had suffered a breakdown, preventing accounts originating from regions such as India from establishing a stable connection.

Despite the widespread speculation linking the downtime to the Singapore data hub, Telegram's corporate leadership and official communications channels did not provide an immediate technical explanation or public post-mortem detailing the root cause of the failure. The lack of an official statement left users dependent on crowdsourced tracking data to monitor the restoration of services.

Although initial repair efforts allowed services to claw back by late morning, the recovery was far from instantaneous or linear. The Straits Times noted that while Singapore reports dipped to about 350 by 11:30 am, a secondary wave of connectivity problems pushed complaints back up above 2,200 reports just before 2:00 pm before dropping sharply to 279 shortly thereafter.

By early evening, platform tracking indicated that the acute phase of the disruption had largely subsided. Downdetector metrics showed that Telegram service reports had fallen back to approximately 60 by 6:00 pm, signifying that normal messaging capabilities had returned for the vast majority of stranded users across Asia.

Services of messaging app Telegram have resumed in Singapore and neighboring markets following hours of technical uncertainty. While crowdsourced tracking metrics confirm that baseline connectivity has been restored for the majority of consumer accounts, the absence of a detailed corporate disclosure leaves open questions regarding infrastructure redundancy and the precise trigger behind the regional server failure.