Mysteries of Telegram Data Centers (2022)
https://dev.moe/en/3025It's a capital T.
Also, it looks like it's easy enough to ID your DC on their API, though I haven't tried it yet (more of a Matrix Stan personally): https://core.telegram.org/method/help.getConfig
If you're feeling any better latency on the west coast it's more likely to be placebo than real.
Any DC may refuse a request and force the client to switch DC.
Profile URL doesn't show where messages/chats/channels are stored, as telegram has two dedicated DCs mostly for media. The rest DCs allow media with bandwidth being throttled.
Why not a sticky master election per user, and have no special data centers?
You are suggesting to develop a compicated solution (spend money) when current simple one is working ok without any elections.
Something like this:
DC1 politically belongs to UK which "spies" on CA/US but physical servers are located in US so US ultimately retains control.
DC2 politically belongs to France which "spies" on RUS/UKR/DE but physical servers are located in NL (e.g. in UK because one wouldn't be able to spot difference in ping). Maybe it's politically owned by UK/NZ or UK/AUS because France can't be publicly caught spying on Germany. But France wouldn't risk public arrest of Telegram CEO and the spectacle with russia if there is nothing to gain.
DC4 politically belongs to USA which "spies" on UK/Israel but physical servers are in NL/UK
DC5 politically belongs to UK/USA which "spies" on AUS/China/India but physical servers are in Singapore (e.g. former UK colony)
I love mentioning the UK in these kind of discussions because the pushback is biggest every time the Crown is mentioned, and ultimately US/CA/NZ/AUS are all colonies under the King.Really cool to see realpolitik mapped out like this. It also highlights the problem of metadata with these kind of topics.
[1] https://dev.moe/wp-content/uploads/2022/05/image-14.png
[2] https://en.wikipedia.org/wiki/Arrest_and_indictment_of_Pavel...
(and a follow-up: https://istories.media/en/news/2025/06/10/telegram-responds-... )