As I promised above, I’m posting more details about how relying on third party CDN caching nodes can securely increase download speed of viral public content in places where Telegram wouldn’t want to place its own servers.

Overview: https://telegram.org/blog/encrypted-cdns
Technical info for client devs: https://core.telegram.org/cdn
CDN FAQ: https://core.telegram.org/techfaq#encrypted-cdns
CDN FAQ in Persian: https://core.telegram.org/cdn/faq_ir

As you can see, CDN caching nodes have nothing to do with relocating Telegram servers or complying with unreasonable local laws. CDNs are merely tools to upgrade connectivity for millions of users in a secure way. We treat these CDN nodes just like we treat the nodes of your internet provider – they only ever get encrypted junk they can't decipher.

What is best about Telegram is that you don’t have to take my word when in comes to security – everyone is welcome to verify the implementation of CDN nodes in the updated Telegram clients for iOS and Android https://telegram.org/apps#source-code. In addition, you might want to have a look at our docs above to check that all is safe.

We rely on an international CDN provider which helps us with caching nodes all over the world. Telegram has nothing to lose if a local government decides to disrupt a caching node on their territory, since the CDN is not our property, and no private data can even in theory be affected. Thus we don’t get into dependance from local governments and laws, have no legal or financial risks, but significantly improve speed of downloads for public content.

If, despite of all of the above, some media come out with clickbait titles like “Telegram moved their servers to North Korea”, please help us by spreading the word about the real situation described in the links in this message. Thanks for reading this, and – as always – I'll keep you updated on everything that goes on around Telegram globally here in my channel.