DC2 Media Downloading Issues
Our users are reporting that DC2 is currently experiencing issues related with downloading media, whereas the download speed has dropped significantly due to issues on the server.
Updated 03/23/2024 09:54 UTC
On March 23th DC2 works properly.
#outages
Our users are reporting that DC2 is currently experiencing issues related with downloading media, whereas the download speed has dropped significantly due to issues on the server.
Updated 03/23/2024 09:54 UTC
On March 23th DC2 works properly.
#outages
π56π±15π€‘7π€―5π5β€2π2
Issues with Downloading Media
Our subscribers are reporting that they are experiencing problems when downloading media, voice messages, and video messages.
UPD. 16:24 UTC: The issue was resolved.
#outages
Our subscribers are reporting that they are experiencing problems when downloading media, voice messages, and video messages.
UPD. 16:24 UTC: The issue was resolved.
#outages
π±37π23β€8π€‘3π2π1π€―1
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. 17:30 UTC: Service seems to be stabilizing after an hour and a half outage.
#outages
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. 17:30 UTC: Service seems to be stabilizing after an hour and a half outage.
#outages
π±53π€‘25π12π12π9β€3π‘1
Telegramβs DC5 Is Down Again
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.
#outages
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.
#outages
π€‘95π³16π7π±7β€5π5π€―4π2π2π‘1
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
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
π€‘43π±28π13β€3π2π‘1
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
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
π€―31π21π€‘15β€12π±3π3
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
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
π82π51π±21π‘13π9β€7π€‘4π3
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
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
π€‘38π30π€―8π8π5β€2
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
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
π31π€‘16π‘13β€7π³5π2π±1π1
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
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
1π39π±13π€‘12β€5π‘5π3π€―2
[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
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
π€‘54π19π€―8β€4π³3π‘3
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
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
π46π€‘13π5π³4π3π‘3π€―2π±2π1
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
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
π27β€10π€‘10π8π‘5
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
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
π29π€‘18π17π€―14π6π4π4β€3π³3π‘3π±2
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
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
π680π469π90π‘86π€‘58π23β€11π±7π³3π€―2π2
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
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
π27π³12π€―9π€‘3β€2
Bot Outages
Bot owners and users are now reporting issues with bot functionality.
UPD at 20:16 UTC
Fixed
#outages
Bot owners and users are now reporting issues with bot functionality.
UPD at 20:16 UTC
Fixed
#outages
π±35π17π12π€―9β€7π5π€‘3π³2π2
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
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
π‘38π26π12β€11
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
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
1π€‘29π13β€8π€―4π‘3π2π³1
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 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
π€‘52π24β€17π€―4π3π2