Telegram services gradually resume after thousands report outage

Nearly 4,000 reports just after 10:30am, then a sharp decline
Telegram's outage in Singapore peaked within minutes and began recovering by late morning.
Mark

So nearly 4,000 people couldn't use Telegram at the same time—that's a lot. Do we know how many Telegram users are actually in Singapore?

Mimi

The article doesn't give us that context, so we can't say whether 4,000 is a small fraction or a significant chunk of the user base. Downdetector only captures people who actively report problems, so the real number affected could be higher.

Luke

Right—and that's the key limitation here. Downdetector is a crowdsourced tracker, not an official count from Telegram. Some people might not bother reporting, others might report multiple times. We're looking at a floor, not a ceiling.

Mark

What about the breakdown—half the app, 40 percent messaging, 5 percent login. Does that tell us anything about what went wrong?

Mimi

It suggests the problem wasn't uniform. If it were a total outage, you'd expect those percentages to be much more even. The fact that different functions were affected differently hints at something more granular—maybe a server issue, maybe a deployment gone wrong.

Luke

But we don't actually know. Telegram hasn't said anything about the cause, so we're just pattern-matching. The article is honest about that gap.

Mark

And by 11:30am it was mostly resolved?

Mimi

The reports dropped to 350, which is a steep decline from the peak. That suggests services were coming back online, though "resolved" might be generous—some people were still having trouble.

Luke

And we don't know if that was the end of it. The article stops at 11:30am. Did it get worse again? Did it take another hour to fully clear? We just don't know.

  • Just after 10:20am, a wave of disruption reports began flooding Downdetector, crossing 1,500 complaints within ten minutes — a rapid signal that something had gone seriously wrong.
  • The outage peaked at nearly 4,000 reports by 10:30am, with users split between a broken app, failed messaging, and complete login lockouts.
  • The breakdown exposed how fragile digital dependency can be — half of those affected couldn't use the app at all, while 40% lost the ability to send or receive messages.
  • By 11:30am, reports had fallen sharply to around 350, suggesting Telegram's infrastructure was quietly healing itself without public acknowledgment.
  • No official statement from Telegram explained the cause or offered a restoration timeline, leaving users to monitor the situation through third-party trackers and their own screens.

On the morning of September 8, thousands of Singapore users found themselves suddenly cut off from Telegram, the messaging platform many rely on for daily connection and commerce. At its height, nearly 4,000 people registered their frustration through disruption-tracking services — a small but telling reminder of how deeply woven digital communication has become into the fabric of modern life. By late morning, the silence began to lift, though the cause of the interruption remained unspoken, leaving users to navigate uncertainty without explanation.

Telegram went dark for thousands of Singapore users on the morning of September 8, with disruption reports emerging around 10:20am on Downdetector — a platform that aggregates user-submitted outage signals from across the internet. Within ten minutes, more than 1,500 complaints had been logged, and the numbers kept climbing.

By just after 10:30am, the outage had reached its peak: nearly 4,000 reports painted a picture of a service under significant strain. Roughly half the affected users were experiencing problems with the mobile app itself, 40 percent found they could no longer send or receive messages, and a smaller group — around 5 percent — were locked out entirely and unable to log in at all.

The situation began to ease by late morning. Reports declined sharply, falling to approximately 350 by 11:30am, suggesting that Telegram's systems were recovering incrementally rather than suffering a total collapse. Yet even as access returned for many, Telegram offered no public explanation for what had caused the disruption or when full service would be restored — leaving users to piece together the picture themselves.

Telegram went dark for thousands of Singapore users on the morning of September 8, with the disruption peaking just after 10:30am when nearly 4,000 people reported problems accessing the messaging platform. The outage began surfacing around 10:20am on Downdetector, a website that aggregates service disruption reports from users across the internet. Within ten minutes, over 1,500 complaints had been logged. The platform's tracking data painted a picture of a service struggling under strain: roughly half the reports pointed to problems with Telegram's mobile app itself, while 40 percent of users couldn't send or receive messages, and a smaller group—about 5 percent—found themselves locked out entirely, unable to log in.

By late morning, the situation had begun to stabilize. The number of incoming reports dropped sharply, falling to around 350 by 11:30am, suggesting that Telegram's infrastructure was recovering and users were regaining access. The gradual decline in reports indicated the outage was not a complete collapse but rather a degradation that the platform was working through, though the underlying cause remained unexplained. No official statement from Telegram addressed what had triggered the disruption or provided a timeline for full restoration.

Contattaci Domande frequenti