Telegram’s DC5 Is Down

Users are currently reporting issues when connecting to DC5 or when interacting with users and chats located in DC5.

This datacenter in Singapore serves users from Asia, Oceania, and Australia.

UPD. 10:15 UTC: Problem seems to be fixed now.

#outages

Outage in Telegram

According to Downdetector platform, users started reporting problems after 18:00 UTC.

The messenger has been unavailable for over an hour. After 19:50 UTC, Telegram started to restore service.

#outages

People Nearby and Groups Nearby No Longer Visible

Our subscribers report that both People Nearby and Groups Nearby have disappeared from the "People Nearby" section.

The @tginfo team does not have any information on whether this is related to the recent events in Paris.

UPD at 20:23 UTC
You still can see users nearby if they are added to your contact list. Of course only if they tapped "Make myself visible" there.

UPD September 5th
People Nearby was removed completely from Telegram Beta 11.1

#outages #peoplenearby

Telegram Data Center Is Unstable

According to our subscribers' reports, some data centers are have been unstable starting 17:00 UTC. Sending messages, loading pinned messages and media have been taking long.

UPD 17:25 UTC: Performance significantly improved, lags still remain.

UPD 17:35 UTC: Problems still remain, with performance deteriorating or improving at different times; Media loading issues seem to be fixed.

UPD 17:42 UTC: Issues seem to be fully fixed.

UPD 17:46 UTC: DC4 still unstable.

#outages

Telegram Is Unstable

Since 10:50 UTC, users face malfunctions in the Telegram platform. Delays occur when sending messages and when switching between application screens.

UPD 12:10 UTC
Issue is resolved

#outages

Issue with Link Snippets in Telegram

Users report that messages containing links are no longer generating preview cards or Instant View articles.

When composing a message, instead of displaying link information, the messenger shows an indefinite loading status. The issue only affects links that have not been previously shared on Telegram and are not cached on Telegram's servers.

UPD. Some developers also report issues with sending files and media in bots.

UPD 20:30 UTC: Link previews and media in bots are functioning again. Some messages sent during the outage have been retroactively updated with preview cards.

#outages

[Fixed] Direct Version of Telegram for Android Offered Incorrect Update

The Telegram app for Android, installed directly from telegram.org, is prompting users to install an update. Users report that after installing the update, the direct version of the app does not update, but a second instance of Telegram appears in the app menu.

Ignore this update: It appears that the Telegram team mistakenly distributed the Google Play version as an update for the direct version.

If you have already installed the update, you can delete the second Telegram app where you are not logged in. Deleting the duplicate will not remove your accounts from the direct version.

As soon as the issue is resolved, we will update this post.

UPD. 10:00 UTC
Situation has been fixed

#outages

Voice chats are unstable

According to information from users, on December 7, voice chats in Telegram have been unstable since the beginning of the day. Problems are observed both when connecting to existing chats and when creating new ones.

We do not know when the problem will be fixed. The post will be updated as new information appears.

UPD 12/08/2024
The issue appears to be resolved, and there have been no further reports about it.

#outages

Temporary Slowdown in Telegram DC2

Between 14:25 and 14:40 UTC, Telegram users experienced temporary disruptions in the DC2 data center (Europe), with messages loading and sending slowly.

The likely cause of this brief malfunction appears to be a major internet outage across Russia, during which Telegram remained one of the few major platforms still operational.

#outages #Russia

Outages in many Telegram services

Our subscribers report that Telegram's data center in Europe (DC2) has been experiencing interruptions since 20:15 UTC.

Symptoms: groups and channels are slow to open, messages and pictures are not being sent in large chats.

Upd 17.05.2025 08:33 UTC
Issue is fixed

#outages

Malfunction of Message Translation

Users report that when they try to translate messages or chats they get a dialog saying that "Translations are currently disabled".

Upd 26.06.2025 19:29 UTC
Telegram has confirmed the issue on X and stated that the feature will remain temporarily unavailable while they are making "some technical fixes".

#outages

Telegram.org Unavailable

Currently, the websites telegram.org and fragment.com are unavailable for at least some users.

Updated at 9:46 UTC
The issue is fixed

#outages

Bot Outages

Bot owners and users are now reporting issues with bot functionality.

UPD at 20:16 UTC
Fixed

#outages

t․me Link Previews Aren't Working

UPD 12:00 UTC. The problem has been resolved

In Telegram, preview cards are no longer being generated under messages with Telegram's t․me links.

The links still open, even if they don't have a preview. Previews for old links continue to work.

The problem has been observed since at least 3 AM UTC and affects links to chats, channels, messages, stickers, stories, and profiles, among other things.

#outages

Deceptive Website Warning on macOS: Apple Falsely Blocks Instant View

Users of Telegram Desktop for macOS are facing a false "Deceptive Website Warning" when trying to open an Instant View for any site.

Most likely, Apple has mistakenly blocked the technical address that the messenger app uses to display Instant View articles.

Don't panic: this is a false warning. If you are impacted by the problem, here is what you can do:

One-time solution
In the warning window itself, click "Show Details", and then click the "visit this unsafe website" link, after which the article will open.

If the warning annoys you too much (unrecommended, not safe)
You can temporarily disable this check in macOS itself:
• Open Safari.
• In the top menu bar, select Safari › Settings › Security.
• Uncheck the "Warn when visiting a fraudulent website" option.

The @tginfo team will announce when the problem is resolved, so you don't forget to turn this setting back on.

#outages

Telegram Is Banned in India, Deleted from App Stores, Suffered a Global Outage

The Indian government ordered a temporary ban on Telegram due to mass leaks of NEET-UG exam questions. However, a local telecom‘s attempt to restrict access led to interceptions far beyond the country. Editors at @tginfo explain how local censorship turned into a global outage.

What Happened in India

The formal reason for the ban was leaked questions for the national medical exam in Telegram channels. Currently, the official Telegram client has been removed from the Indian App Store and Google Play storefronts.

Pavel Durov points out that this move punishes 150 million users in India, while the leaks simply migrated to a different app, and that Telegram cooperated with regulators by deleting “hundreds of channels sharing leaked exam materials and related scams in India”. The CEO also adds that the messenger team has “been making the ‘edited’ label more visible to prevent backdating scams”, although it is not clear whether this change hasn't shipped yet or is some local change that our editors couldn‘t confirm independently. The “edited” indicator changes are said to be done to fight backdating scams.

For context, India is one of the biggest Telegram markets. The Indian government tried to pressure Telegram before: in 2022, a court demanded the disclosure of pirate channel owners‘ personal data. At that time, Telegram only complied on paper, stating that it didn‘t store the requested data on its servers. It is clear that this time the government is trying to act with more force.

From a Local Ban to a Global Outage

Trying to restrict Telegram inside the country, an Indian telecom company used a BGP routing hijacking trick.

• The Internet is made up of many interconnected networks that tell each other the data paths using the BGP protocol.
• An Indian telecom company announced to the whole world that it owns Telegram's IP addresses, forcing part of the global traffic to be sent through the false route, which blocks access to the messenger.
• Since many service providers around the world still don‘t verify the authenticity of the routes they receive, the false routes spread around the globe.

As a result, connectivity issues could be observed even outside India, including regions like the UAE. Similar incidents happened before: for example, in 2023, the Iraqi government used a similar trick to ban Telegram.

Industry experts point out that the Indian telecom even got into a brief network war with Telegram, in which one company tried to overwrite the opponent‘s routing directions. Pavel Durov announced that Reliance stopped malicious routing four hours after his post.

Erroneous Accusations Against Meta Trying to Blame for All Their Problems

Pavel Durov called the service provider‘s actions intentional sabotage and assumed that it might be part of the competitive war that WhatsApp is leading against Telegram, based on a claim that Reliance is partially owned by Meta (parent company of WhatsApp and Facebook).

Despite this, community and media research shows that Pavel Durov confused two companies. The network system that was hijacking the traffic is owned by Reliance Communications, an old telecom asset midway through bankruptcy, while Meta invested in a completely unrelated company — Jio Platforms (which also owns Reliance Jio, a large Indian service provider).

The theory about WhatsApp‘s corporate conspiracy couldn‘t be backed by any technical data. It is likely that the global traffic hijacking was caused by incompetence among the engineers at the Indian company responsible for configuring the hardware to block Telegram. It is not the first time that Pavel Durov has publicly accused WhatsApp of attacking Telegram, explaining unfavorable events with conspiracy theories.

#India #censorship #outages

The .me registry has blocked the t.me domain

UPD July 14, 13:00 UTC: The domain was restored.

Telegram users worldwide have encountered an outage: short t.me links have stopped opening in regular browsers. The problem affects users in the entire world.

At the same time, within the mobile and desktop Telegram clients themselves, clicks on links are processed correctly, and redirects work without any problems. As a temporary alternative for posting on external resources, you can use telegram.me links.

Technical details

At the moment, the exact causes of the incident remain unknown.

According to WHOIS data, the t.me domain has been completely removed from the DNS zone by the administration of the .me domain registry.

This status is set not by the registrar (GoDaddy), but directly by the main operator of the domain zone — the Montenegrin company doMEn d.o.o., which manages the entire .me zone. This organization is a joint venture of Identity Digital, GoDaddy, and ME-net.

#outages #bans

Telegram Is Still Working on Restoring the t.me Domain

UPD July 14, 13:00 UTC: The domain was restored.

The t.me domain is still down for users worldwide, as it was disabled by the administration of the .me domain zone. The messenger's team has not commented on the matter.

As a temporary measure, users are advised to replace t.me links with telegram.me or telegram.dog — the messenger's official domains.

The @tginfo editors note that Instagram blocks links to telegram.me in profiles, but links to telegram.dog work. Some users report that Instagram bans users from using the “link in bio” feature if the domain is changed, so the best course of action is to wait for the t.me domain to be restored.

Shortly after the news about the domain being disabled, Telegram began replacing t.me links in Telegram apps and on the official telegram.org website. Pavel Durov attempted to contact the .me registry administration via their official Twitter account.

Possible reason for the block

The .me zone belongs to Montenegro, and the infrastructure is managed by a joint venture of Identity Digital, GoDaddy, and the local company ME-net.

The owner of the TeleLakel channel received a response from Identity Digital's support team, which claims that the domain was disabled due to the “need to comply with OFAC-related requirements”.

OFAC is a division of the US Department of the Treasury that administers and enforces economic and trade sanctions.

OFAC has not added Telegram to its sanctions lists. However, an action statement dated July 13, 2026, regarding newly sanctioned companies mentions a service called "FIRST VPN SERVICE". Users noticed that one of the links to its website is a Telegram channel address on the t.me domain.

This could mean that the .me domain operator saw the t.me domain in the sanctions lists and quickly blocked it without further research.

The @tginfo team noticed that this morning the messenger deleted the Telegram channel that was mentioned in this sanctions list. It is unknown whether this channel was actually the reason for the block, or if Telegram did this on their own as a precaution.

A popular rumor about the reason for the block

A version is spreading in the community that the t.me domain was revoked because the official Telegram Twitter account joked about the September 11th terrorist attack.

The @tginfo editors consider this version unlikely: if it were true, the .me domain zone administration would likely have blocked all Telegram domains, including telegram.me. Furthermore, the published image was not a joke invented by the company itself, but one of the most popular entries submitted by users as part of a contest.

#outages #bans

The t.me Domain Has Been Restored by the .me Registry

Checks by the @tginfo editors show that the .me zone's main server has returned the DNS records for the t.me domain.

Since DNS records are cached at the level of various DNS services and providers, it may take up to 24 hours for service to be restored on users' devices.

#outages #bans

The .me registry commented on the suspension of the t.me domain

A representative of the .me domain zone administration commented on Twitter about the situation regarding the ban of the t.me domain, which belongs to Telegram:

The .ME Registry works closely with law enforcement to monitor and mitigate issues across the .ME domain in accordance with applicable laws, including sanctions requirements.

On 13 July, First VPN Service (1VPNS) was included as a sanctioned entity by the U.S. Department of the Treasury. A Telegram channel using the t.me domain was among 1VPNS identified infrastructure. Accordingly, the t.me domain was suspended.

On 14 July, Telegram provided confirmation that it had removed its links and affiliations with 1VPNS. Once the confirmation was reviewed and verified, the suspension was removed from the t.me domain.

We appreciate Telegram’s prompt cooperation in resolving this matter.

It is unclear from the comment whether the .me administration evaluated the appropriateness of blocking the entire domain of a major social platform and whether the registry will resort to such methods in the future.

As a reminder, on July 13, the .me registry disabled the DNS records for the t.me domain without any public statements from the zone administration or Telegram. On July 14, Identity Digital support explained the ban as compliance with OFAC requirements, and a link to a Telegram channel was found in the service's sanctions lists, which the messenger soon deleted, after which the domain was restored.

The .me zone is allocated to the government of Montenegro, but on its behalf, the infrastructure is managed by a joint venture between Identity Digital, GoDaddy, and the local company ME-net.

#outages #bans