Why Telegram Went Down: The Singapore Data Centre Behind the Outage and What SMEs Should Do Differently

By Ryan Lim · September 2026

Regional messaging traffic depends on a handful of data centre clusters — and one of them failed on 8 September.

When Telegram stopped working on the morning of 8 September, Malaysian users saw the familiar symptoms: messages stuck in transit, chats that would not load, and the app hovering on a connecting screen. What they could not see was why.

Days later, the picture is clearer. The outage did not begin in Malaysia, and it was not caused by local network problems. It began at DC5 — Telegram's data centre cluster in Singapore that handles users across Asia-Pacific.

What Actually Happened

Outage reports began building through the morning of 8 September and peaked around late morning Singapore time. According to outage-tracking data reported across the region, the scale looked like this:

Reports also came from the United States and parts of Oceania. Seven Asia-Pacific markets were named directly, and users reported problems with messaging, logins, chat loading and even Telegram shortlinks. Service resumed gradually over the following hours.

For many Malaysian businesses, this is the operations console: orders, supplier chats and customer groups.

Why One Data Centre Knocked Out Seven Countries

The mechanism behind the outage is the part worth understanding, because it explains why an incident in Singapore hit Malaysian businesses specifically.

Telegram assigns accounts to data centre clusters based on the country code of the phone number used to register. Those assignments are sticky: a Malaysian account generally remains on the cluster serving Malaysian numbers even when the owner travels or logs in from another country. When that cluster has a bad morning, everyone assigned to it has a bad morning — regardless of where they physically are, and regardless of how healthy their own internet connection is.

Telegram had not published a public explanation of the root cause at the time of reporting. There has been no indication that the outage was caused by a cyberattack, and the pattern — one regional cluster failing, service restored over hours — points to infrastructure rather than interference.

Desktop and web clients failed alongside the mobile app, because they depend on the same account cluster.

The Uncomfortable Lesson for Malaysian SMEs

Many small businesses in Malaysia now run real operations on Telegram: customer orders, supplier negotiations, delivery coordination, staff groups, even document sharing. The outage exposed three structural weaknesses in that arrangement.

First, there is no service level agreement. Telegram is a free consumer product. No uptime guarantee, no account manager, no contractual remedy, and no obligation to explain the failure afterwards. When other companies' communications platforms break, they publish a status page and an incident report. Here, businesses simply waited.

Second, your customer data lives in someone else's cluster. Contact lists, order histories and shared documents sit inside an app you do not control, on infrastructure you cannot inspect, with a retention model you did not negotiate.

Third, a single region can be enough to stop you. If three-quarters of your customers, suppliers and riders are reachable only through one app, then one data centre failure is a full business interruption, not an inconvenience.

Concentration risk is the quiet problem: one cluster, one region, many businesses dependent on it.

What to Do Differently: A Practical Checklist

1. Own your contact list. Export customer and supplier contacts out of the app at least quarterly and store them in a CRM, a spreadsheet or your invoicing system. If the app is down, your business should still know who to call.
2. Run a second channel by default. Keep WhatsApp Business or email active for the same customers, and publish both sets of contact details on your website, invoices and shopfront. A channel your customers already use is the cheapest redundancy you can buy.
3. Move documents out of chats. Quotations, purchase orders and delivery documents should live in cloud storage or on your own systems, with links shared in chat — never as the only copy.
4. Agree an outage drill with staff. Decide in advance: if messaging fails, staff switch to calls and email, and one person posts an update on your other channels within 30 minutes.
5. Tell customers before they ask. A short template — "our messaging platform is down, please reach us at this number or email" — protects trust and reduces the chance orders go to a competitor during the window.
6. Keep a paper trail for orders. Take orders by voice? Log them in your system immediately, not later in chat.
7. Check your critical tools separately. If an e-invoicing portal, payment gateway or delivery platform also depends on the same region, ask what its failover plan is.

There is a wider pattern here, too. Earlier this month, several major AI platforms failed on the same day. Within a week, Telegram's regional cluster went down. Neither was caused by anything a small business did — but both show how much everyday operation now rests on infrastructure that is shared, opaque and unaccountable to small customers.

Frequently Asked Questions