Telegram Connection Issues, Throttling and Proxy Speed Setup Guide

Basically no. Mainland carriers block Telegram at the network layer, so without a VPN/circumvention tool a direct connection usually fails, and registration, login, and messaging all stall at Connecting. On top of that, a mainland +86 number has its international verification SMS blocked by the carrier, so it never arrives no matter how long you wait, and registration mostly needs an overseas number or an SMS-receiving service. The workable approach: turn on a VPN/circumvention tool first, or set up a SOCKS5/official MTProto proxy under Use Proxy in Telegram (note it only routes Telegram traffic; on desktop match the port to the client local port and restart after setting it).

Fix it in this order: (1) change networks first, switch between Wi-Fi and 4G/5G, or toggle Airplane Mode off and on for a few minutes to reconnect. (2) On Desktop/Mac the most common cause of Connecting is a mismatched port: go to Settings > Advanced > Connection and proxy, set the proxy to SOCKS5, server 127.0.0.1, and the port to the actual local port of your circumvention client (Clash is commonly 7890, v2rayN SOCKS5 is commonly 10808, subject to the actual app). (3) Always restart Telegram after setting the proxy; if you are logged in but stuck and cannot send or receive, restarting the app or device usually fixes it. (4) Confirm the built-in proxy only routes Telegram; the browser being online does not mean Telegram can connect.

Fill it in the built-in proxy settings of Telegram (the paper-plane app): on Desktop > Settings > Advanced > Connection and proxy > Add proxy; on mobile > Settings > Data and Storage > Proxy. Under SOCKS5, if you use a local circumvention client, set the server IP to 127.0.0.1 and the port to the client actual local port (Clash is commonly 7890, v2rayN SOCKS5 is commonly 10808). If it is a remote SOCKS5 node someone gave you, fill in the IP and port they provided. An MTProto proxy is more often imported via a one-tap link (tap tg://proxy?server=...&port=...&secret=... and it fills in and enables automatically). Note the built-in box only accepts SOCKS5, not an HTTP proxy; restart Telegram after setting it.

First, to be clear: Telegram does not provide or endorse specific proxy nodes, and the built-in Use Proxy is just a tool with no free IP list attached. Free MTProto/SOCKS5 nodes out there are mostly distributed by third parties in channels (often given as tg://proxy?server=...&port=...&secret=... or t.me/proxy links, which import and enable with one tap, and a secret starting with dd means fake-TLS disguise is on). But free public nodes are unstable, security is at your own risk, and they may be abused or log traffic. The safer route is to self-host MTProxy (open-sourced officially on GitHub) or use a reliable VPN/circumvention client paired with built-in SOCKS5.

The built-in Use Proxy is an official feature, and on Android the path is Settings > Data and Storage > Proxy > Add proxy. It supports two protocols: SOCKS5 and official MTProto. The simplest is to tap a t.me/proxy one-tap link someone shared to import MTProto, and when the status shows Connected it worked. If you already run a circumvention tool locally: fill in SOCKS5, server 127.0.0.1, and the port set to the client actual local port (Clash is usually 7890). Note the built-in proxy only routes Telegram own traffic and does not affect other apps, and it is best to restart Telegram once after setting it. Node stability and security are at your own risk.

Two routes: one is to turn on a whole-device VPN/circumvention tool at the phone level to route all traffic, in which case you usually do not need to set a separate proxy inside Telegram; the other is the Telegram built-in proxy, with the path Settings > Data and Storage > Proxy, where you can fill in SOCKS5 (server 127.0.0.1, port set to the client actual port) or tap a t.me/proxy one-tap link to import the official MTProto. Note the built-in proxy only routes Telegram through the proxy and does not affect other apps, so the browser being online does not mean Telegram can connect. After setting the proxy, restart Telegram once and check whether it shows Connected.

Yes, changing networks is the first troubleshooting step. The community-accepted order is: change networks first (switch to 4G/5G mobile data or a different Wi-Fi) > then check the proxy settings (whether SOCKS5 has 127.0.0.1 plus the correct local port) > restart Telegram or the device after setting it. Keep two cases distinct: if it will not connect at all and cannot send or receive messages, it is mostly a network or proxy problem; if text messages are fine and only photos and videos keep spinning, that is not a connection failure but a download-side problem, and blindly changing proxy nodes helps little. Clear the network and proxy hurdles first.

Check in this order: (1) is the port right? On desktop the most common issue is that the circumvention client local port does not match the port filled in Telegram, so confirm SOCKS5, 127.0.0.1, and that the port matches the client actual listening port (Clash is commonly 7890, v2rayN 10808). (2) Do not pick the wrong protocol; the built-in box only takes SOCKS5, not HTTP. (3) Always restart Telegram after setting it; when not logged in, setting a proxy requires a restart to take effect, and if you are logged in but stuck at Connecting, restart Telegram or the whole device. (4) Switch lines: change networks (to 4G/5G) or try a different MTProto one-tap link. (5) If it still fails, confirm your circumvention tool itself works (get the local client connected to a node first).

For Telegram downloads, first distinguish: if text messages send and receive fine and only photos, videos, or files download slowly or keep spinning, that is usually not a connection problem but a download-side bottleneck, and frequently changing proxy nodes helps little. Practical optimizations: under Data and Storage, turn off Auto-download media and switch to manual, set video auto-download quality to Standard/Low, clear the cache periodically to free device space, and switch to Wi-Fi when the network is poor. Also do not believe the changing the data center (DC) speeds things up claim; the account DC is determined by the registration number and cannot be changed after registering, so that is a misconception. The fix is in download settings and proxy path quality, not the DC.

It depends on the actual local port your circumvention client listens on; on desktop, this mismatched port is the most common cause of constant Connecting. Common defaults: Clash / Clash Verge mixed port 7890, v2rayN SOCKS5 default 10808, Shadowsocks commonly 1080. In Telegram, set the proxy to SOCKS5, the server to 127.0.0.1, and the port to the client actual local port (subject to the app settings), then restart Telegram after setting it.

It depends on the protocol. With a SOCKS5 proxy, set the server to 127.0.0.1 and the port to the client local port; a local client usually needs no username or password (unless your proxy server requires authentication). With the official MTProto proxy you need a secret key, usually imported with one tap by tapping a tg://proxy or t.me/proxy link, with the secret already included in the link; a secret starting with dd means fake-TLS is on, disguising the traffic as ordinary HTTPS for better resistance to detection.

Our material records no nationwide Telegram block in Singapore, so on a local network you can generally connect directly with no proxy needed. If you hit slow loading, it is mostly not throttling but a media-download issue: text is fine and only photos and videos spin, usually due to the download queue or cache. Under Data and Storage, turn off auto-downloading media and switch to manual, clear the cache periodically, lower the video auto-download quality, and switch to Wi-Fi when the network is poor. Whether it is throttled is subject to real-world testing on your local carrier; confirm by testing.

Our material records no nationwide block in Myanmar, but as long as you genuinely cannot connect locally, the Telegram built-in proxy is designed precisely to counter blocks and can connect in most cases. How to use it: go to Telegram Settings > Data and Storage > Proxy, choose SOCKS5 and fill in 127.0.0.1 plus your circumvention client local port; or tap an official MTProto one-tap link someone shared (tg://proxy / t.me/proxy) to import it, and when the MTProto secret starts with dd it disguises the traffic as ordinary HTTPS for better resistance to detection. Restart Telegram after setting it, and when it shows Connected it worked. The exact block situation needs confirming by testing.

Free public proxy nodes are unstable by nature, and third-party MTProto nodes failing is common. To swap in a new one: get a new proxy one-tap link (tg://proxy or t.me/proxy), tap it in Telegram to import and enable it, and when the status shows Connected it worked. You can also delete the old one and add a new SOCKS5 under Settings > Data > Proxy. A reminder: node stability and security are at your own risk; and if your case is can connect but loads slowly, blindly changing nodes helps little, since that case calls for handling media download and the cache.

It is mostly not Telegram itself but the two networks being different: the mobile network on data may be treated as international traffic and blocked by the carrier, or your proxy only works on Wi-Fi. Try first: toggle Airplane Mode off and on for a few minutes, switch to 4G/5G mobile data, and reconnect; if you reach Telegram via a circumvention tool/proxy, confirm it also works on the data network and check whether the proxy port in Telegram matches. Remember to restart Telegram after setting the proxy.

Fix it in this order: change networks first (switch between Wi-Fi and mobile data, switch to 4G/5G, and you can toggle Airplane Mode off and on for a few minutes to reconnect); then check the proxy: the Telegram built-in proxy only routes Telegram traffic, so confirm SOCKS5 has 127.0.0.1 plus the client actual local port, since a mismatched port is the most common cause of Connecting, and always restart Telegram after changing it; if your location is blocked (Vietnam, for example), import an MTProto one-tap link. When stuck on the login screen, restarting the app or device often fixes it.

In most cases it is not a network or proxy problem. The number-one truth: if you logged in recently on another device, the login code switches to an in-app Telegram push instead of SMS, so look for the code in the Telegram chat on your signed-in computer or tablet. Next common causes: iOS spam SMS filter or the carrier treating international verification texts as spam (toggle Airplane Mode off and on, or switch to 4G/5G to reconnect to fix it); wrong number format (use international format and drop the leading 0); a mainland +86 number is technically blocked by the carrier and almost never receives it. You can also tap Did not receive the code to switch to voice-call verification.

Generally leave it at the default and do not turn it on specially. Whether a Telegram proxy works hinges on choosing the right protocol (SOCKS5 or official MTProto) and filling in the server and port correctly, not the IPv6 switch. Unless your network is pure IPv6, or the proxy node explicitly requires IPv6, turning it on may actually fail to connect because your local network does not support IPv6. Advice: configure SOCKS5 = 127.0.0.1 plus the client actual local port at the default (without specially enabling IPv6), and once connected leave it alone; if it will not connect, go back and troubleshoot item by item, since IPv6 is usually not the main cause. Confirm by testing.

This is common, and the reason is that the Telegram built-in proxy only routes its own message traffic, while voice/video calls run on a separate peer-to-peer (real-time audio/video) path that does not necessarily follow the proxy, so text and messages are all fine while only calls will not connect. The real fix to try: switch to a method that routes the whole device or specified apps (such as a system-level VPN or Clash global/rule mode) so call traffic goes through the proxy too, rather than only setting SOCKS5 inside Telegram; also confirm both parties networks are clear. Confirm by testing.

It depends on how your client routes traffic. If your airport client (Clash and so on) runs global mode or a rule mode that includes Telegram, it already proxies the whole device/Telegram traffic, so you do not need to set a separate proxy in Telegram and can just use it. Conversely, if you only want Telegram through the proxy and not other apps, or the client does not route Telegram, then set SOCKS5 = 127.0.0.1 plus the client local port (Clash is commonly 7890) in Telegram. Simple rule of thumb: if Telegram sends and receives fine, do not fiddle; if it stays at Connecting, go back and set the proxy with the port matched and restart.