Singapore Mobile SOCKS5 for Telegram in Iran 2026

TL;DR

Order a dedicated SOCKS5 port at Singapore Mobile Proxy, paste the credential string 158.140.129.188:PORT:user:pass into Telegram’s native proxy settings, and your traffic exits through a real SingTel, StarHub, or M1 modem in Singapore. Setup takes under five minutes once you have your credentials from the dashboard. Plans run from $30 to $50 per month for a sticky port, and a no-card free trial is available at /client/trial. Crypto payments are accepted and no Iranian-country KYC is required. The guide below covers why mobile SOCKS5 outperforms MTProto in Iran’s current filtering environment, why Singapore is the best exit country for Telegram specifically, and step-by-step setup instructions for every Telegram client.

why mobile SOCKS5 over MTProto for Iran

Telegram has been blocked across all major Iranian ISPs since September 2018, but more than 50 million users inside Iran continue to access it daily through some form of proxy or circumvention tool. The cat-and-mouse dynamic between Iran’s filtering infrastructure and bypass methods has grown substantially more sophisticated over those years. What worked in 2019 often doesn’t work in 2026, and the specific mechanisms of failure matter when you’re picking a proxy type.

Iran’s three dominant ISPs, MCI (Hamrahe Aval), Irancell (MTN Iran), and Rightel, all run DPI (deep packet inspection) infrastructure on their core and peering links. Through 2024 and 2025, the most consequential upgrade was the widespread deployment of TPM-mod, a DPI module built specifically to kill FakeTLS. FakeTLS obfuscation was widely used by MTProto proxies to disguise Telegram traffic as ordinary HTTPS. It works by crafting TLS ClientHello packets that look superficially like browser traffic. TPM-mod fingerprints the TLS handshake in enough detail to expose this: it checks JA3 hashes, extension ordering, cipher suite selection, and session resumption behavior against a whitelist of known real clients. Traffic through an MTProto proxy with FakeTLS obfuscation fails the fingerprint check and gets dropped silently.

That would be damaging enough on its own, but the filtering system piles on with passive DNS tampering. Both MCI and Irancell have been documented poisoning DNS responses for domains tied to known proxy infrastructure providers. A fresh MTProto proxy server at a new IP, registered under a domain at a common registrar, can find that domain poisoned within hours of its address appearing in Telegram proxy-sharing channels. Rightel has gone further in some periods, deploying SNI sniffing on TLS connections to block any connection whose Server Name Indication field matches proxy-adjacent patterns. The result is a three-stage gauntlet: TPM-mod at the packet layer, DNS poisoning at the resolution layer, SNI sniffing at the TLS layer. New MTProto instances consistently struggle to survive all three. MTProto proxy lists are also public and scraped continuously by government-linked monitoring services. The IPs hosting them are overwhelmingly data-center addresses with high ASN-level visibility, making bulk blocking a low-cost task for an ISP NOC.

Against that background, a SOCKS5 proxy on a mobile carrier IP has a structural advantage that’s hard to replicate. A SOCKS5 connection doesn’t announce itself as a proxy in any protocol-visible way. A connection from an Iranian client to 158.140.129.188 on, say, port 4430 looks like a plain outbound TCP connection to a Singapore IP on a high port. The TLS that Telegram runs inside the SOCKS5 tunnel is real Telegram TLS, because the proxy isn’t intercepting or re-wrapping it. SNI sniffing at the Iranian border sees the outer connection, not the inner one. The outer connection’s fingerprint is indistinguishable from a legitimate HTTPS session to any Singaporean service.

The IP being connected to belongs to SingTel, StarHub, M1, or Vivivi’s consumer mobile address space. These ASNs aren’t on any Iranian blocklist. Blocking them would disrupt every legitimate Iranian business connection to Singapore’s financial and tech sector. The political calculus of that decision is very different from blocking a batch of data-center IPs registered to a VPN company, which is a zero-cost, zero-controversy action for an ISP NOC. Mobile carrier IPs also benefit from the fact that they are shared with millions of real Singapore residents making real connections every day , the collateral damage of blocking even a single /24 of SingTel mobile space would be enormous and immediately noticed by Singapore’s government and telecommunications regulator. For anyone who needs reliable, low-maintenance Telegram access in Iran in 2026, SOCKS5 on a mobile carrier IP has a substantially better expected durability than any form of MTProto on hosted infrastructure. For more background on how the censorship landscape evolved to this point, see the 2026 Telegram censorship resource center.

why Singapore exit over USA/EU

The choice of exit country matters as much as the choice of protocol. A SOCKS5 proxy on a US residential IP or a Frankfurt server might technically work on a good day, but Singapore offers three concrete advantages specific to Iranian Telegram users.

Telegram’s infrastructure is in Singapore. Telegram operates primary data centers in Singapore as part of its global distributed cluster alongside Frankfurt and Amsterdam. When your proxy exit IP is in Singapore, your client reaches Telegram’s Singapore data center directly, with one short hop from the proxy exit to the data center’s edge. Frankfurt and Amsterdam proxy exits route Telegram traffic back across the continent to those data centers, which is fine if you’re in Europe, but adds latency overhead that Iranian users have no reason to accept. For voice calls specifically, the round-trip through a Singapore exit from Tehran is typically 50 to 120ms shorter than through a Frankfurt exit. That difference is perceptible during voice calls and video chats, and it compounds across a long call.

Singapore is not on Iran’s active IP blocklist. Iran’s filtering authorities maintain tiered lists of IP ranges and autonomous systems. US-based cloud providers, including major US residential proxy services, have faced periodic block campaigns during politically sensitive periods, with entire /16 ranges going dark at the border. Singapore’s IP ranges sit in a different political category. Singapore is a major trade and financial hub with substantial Iranian business ties, and the National Information Network has consistently shown restraint about disrupting those economic channels. In practice, Singapore-exit proxies have stayed stable through the same filtering events that took out US-exit services. The Telegram in Iran 2026 guide includes a timeline of blocking events since 2018 that illustrates this pattern ISP by ISP.

Crypto payment rails clear without compliance friction. Services incorporated or operated in the United States fall under OFAC sanctions that create a compliance burden for Iranian customers. Many US-based proxy and VPN services nominally accept crypto but run their payment processing through infrastructure that flags Iranian-origin wallet activity. Singapore-incorporated services operate under different regulatory constraints, with substantially more flexibility to process transactions from customers in jurisdictions under US sanctions. Singapore Mobile Proxy accepts USDT (TRC-20 and ERC-20), Bitcoin, Ethereum, and USDC. No identity documents identifying you as an Iranian resident are required, and the checkout flow does not geoblock Iranian IP addresses.

We operate a physical rack of mobile modems in Singapore, each running on a consumer SIM card from SingTel, StarHub, M1, or Vivivi. I work with customers ranging from individual Telegram users in Tehran to media organizations that need to verify geolocation-dependent content from a Singapore IP. The consistent feedback across that range is that real carrier IPs survive filtering rounds that kill every other method, and Singapore specifically outperforms other APAC exit countries on Telegram latency. The physical-modem setup is more expensive to run than virtual residential proxies, which is why pricing starts higher than you’ll find for data-center SOCKS5, but the durability difference in an environment like Iran justifies the cost for users who depend on the connection.

step 1: buy the port

Visit Singapore Mobile Proxy plans and select the plan that fits your usage. For Telegram use in Iran, two parameters matter: session type (sticky or rotating) and bandwidth allocation.

For personal Telegram use, including voice calls, video, file sharing, and group chats, a 10 GB monthly allocation is sufficient for a typical heavy user. Users who run Telegram Desktop alongside a mobile client, share their proxy with a household, or use Telegram for high-volume file transfers should consider the 30 GB tier. Bandwidth overage doesn’t cut the connection; top-up blocks are available from the portal if you approach your limit.

Pricing in 2026:

The free trial at /client/trial provides a working SOCKS5 credential with 500 MB of bandwidth. No credit card is required, and no identity documents are collected at any tier. The trial draws from the same modem pool as paid plans, so the performance you observe on trial reflects what you’ll get on a paid port.

After purchasing, log into the portal at /client. Your assigned credentials appear on the dashboard immediately: a port number, a username, and a password. The full credential string in the format Telegram expects is 158.140.129.188:PORT:user:pass. Keep this string private. Sharing it allows others to consume your bandwidth allocation and may affect your session stability.

Payment options include USDT (TRC-20), USDT (ERC-20), Bitcoin, Ethereum, USDC, credit card, and PayPal. Crypto payments confirm after one network confirmation. USDT TRC-20 is recommended for speed (typically under two minutes) and low transaction fees. After payment confirmation, the port is active immediately.

step 2: enter creds in Telegram

on Android

1. Open Telegram and tap the three-line menu icon in the upper-left corner to open the side drawer.
2. Tap Settings, then scroll down to Data and Storage.
3. Tap Proxy Settings, then tap Add Proxy.
4. In the proxy type selector, choose SOCKS5.
5. In the Server field, enter 158.140.129.188.
6. In the Port field, enter the port number from your dashboard (a 4- or 5-digit number).
7. Enter your proxy username and password in their respective fields.
8. Tap the checkmark or save icon in the top-right corner.
9. Tap the proxy entry you just created to activate it. A green dot and a latency number in milliseconds will appear when the connection is active.

A latency reading under 250ms is normal from Tehran. Readings above 500ms are unusual on a stable LTE connection and may indicate routing interference. If you see a red dot, double-check the port number and credentials against your dashboard.

on iOS

1. Open Telegram and tap Settings in the bottom tab bar.
2. Scroll down and tap Privacy and Security.
3. Scroll to the bottom of that screen and tap Advanced.
4. Tap Proxy Settings, then tap Add Proxy.
5. Select SOCKS5 from the type options.
6. Fill in 158.140.129.188 as the server, then your port, username, and password.
7. Tap Save, then tap the proxy entry or toggle to activate it.

For a complete iOS walkthrough with screenshots, see the guide on iOS Telegram setup in Iran.

on Telegram Desktop (Windows / macOS / Linux)

Open Telegram Desktop, go to Settings, click Advanced, scroll to Connection Type, and click Use custom proxy. Select SOCKS5, then enter 158.140.129.188, your port, username, and password. Click Save.

testing the endpoint before configuring Telegram

Before entering credentials in Telegram, confirm the SOCKS5 endpoint is reachable from your network. From any terminal (Termux on Android, an SSH session, or a desktop machine), run the following. Use the socks5h:// scheme to route DNS through the proxy, which matters because MCI and Irancell both perform passive DNS tampering on Telegram-related domains:

curl -v \
  --proxy socks5h://user:pass@158.140.129.188:PORT \
  https://api.telegram.org

A working proxy returns a Telegram API response, typically {"ok":false,"error_code":400,"description":"Bad Request"}. This is expected and confirms the tunnel is functional. The 400 error means Telegram received the request and rejected it for missing parameters, not that the proxy failed. A connection timeout or SOCKS5 connection failed message means the port or credentials are wrong, or your local connection is blocking outbound traffic to Singapore on that port. If that’s the case, try port 443 if your plan supports it, since Irancell and MCI are less likely to filter outbound port 443 traffic to a Singapore IP. For more detail on the socks5h vs socks5 scheme difference and how Telegram handles SOCKS5 authentication, see socks5 auth modes telegram.

step 3: verify the IP

After activating the proxy in Telegram, confirm your traffic is actually exiting through Singapore. From a terminal:

curl --proxy socks5h://user:pass@158.140.129.188:PORT \
  https://ifconfig.io

This returns the public egress IP of your assigned modem. It will be a Singapore-geolocated mobile IP in a SingTel, StarHub, M1, or Vivivi ASN range, not 158.140.129.188 itself (that is the proxy ingress, distinct from the modem’s exit IP). To confirm geolocation and carrier details in a single call:

curl --proxy socks5h://user:pass@158.140.129.188:PORT \
  https://ipinfo.io/json

A correct result looks like this:

{
  "ip": "203.xxx.xxx.xxx",
  "city": "Singapore",
  "region": "Central Singapore",
  "country": "SG",
  "org": "AS9506 Singtel Mobile Internet"
}

The country field must be SG. The org field should name one of the four Singapore carriers. If either shows something unexpected, the port may be misconfigured or your traffic may be intercepted before reaching the proxy. Open a support ticket in the portal before relying on that port.

Within Telegram itself, the active proxy entry in Settings shows a latency figure consistent with a Singapore exit (50 to 200ms from Iran). One scope boundary worth knowing: the SOCKS5 proxy configured in Telegram routes only Telegram’s traffic. Other apps on your device keep using your MCI, Irancell, or Rightel connection directly. Telegram binds all its traffic to the configured proxy when one is active, so there’s no WebRTC or DNS leak surface inside Telegram itself, but your browser, email, and other apps remain on the Iranian ISP connection unless you separately configure a system-level VPN.

sticky vs rotating: which to pick for Telegram in Iran

For Telegram account use, sticky sessions are the right choice, and the reason comes down to how Telegram manages account security.

When you authorize a new Telegram session, Telegram records the IP address and approximate location of that login. If the IP associated with an active session changes abruptly, particularly across different countries or ASNs, Telegram’s security system flags the session as suspicious. In a low-stakes context this triggers a notification on your other devices, asking you to confirm the new session is legitimate. In a high-risk environment like Iran, where account access is critical and loss of access has real consequences, forced re-authentication is a serious inconvenience and a potential operational failure point. A sticky port holds the same Singapore mobile IP for your entire billing month, presenting a consistent session identity to Telegram’s backend. Once your initial session is established through that IP, the account security system has nothing to flag.

Rotating ports serve a different use case: security researchers, journalists doing source verification, OSINT analysts checking Telegram channels, and anyone running automated checks against the Telegram Bot API. For those workflows, rotating IPs reduce per-IP request frequency and lower the chance that Telegram’s anti-abuse system flags a single IP for high request volume. That kind of work also requires separate accounts per task rather than a primary personal account, and it demands careful session management.

It is also worth noting what happens during the transition between billing periods on a sticky plan. The same port and credentials remain active at renewal, and in most cases the underlying modem retains its IP assignment across the renewal boundary. If a modem is rotated or replaced during the billing period for maintenance reasons, the portal will display the new egress IP within minutes of the change taking effect, giving you time to re-verify before issues arise in Telegram. The overwhelming majority of Iranian Telegram users accessing the service for personal communication should choose the sticky plan. The free trial defaults to a sticky port so you can evaluate the experience before committing. For guidance on responsible use when running automated workflows through the proxy, see ethical mobile proxy use.

what to expect on speed and uptime

Measurable performance for Iranian users breaks across two dimensions: latency, which affects real-time communication like voice and video calls, and throughput, which affects media downloads and file transfers.

On latency, the Iran-to-Singapore round-trip time varies by ISP, time of day, and device location within Iran. Based on data from customers connecting from Tehran, Isfahan, Shiraz, and Mashhad through early 2026:

These are round-trip times to the proxy ingress at 158.140.129.188. The additional hop from the Singapore proxy egress to Telegram’s Singapore data center adds 5 to 15ms, since both are within Singapore’s low-latency intra-city network. Total end-to-end latency is the sum of your Iran-to-SG ingress RTT plus that short datacenter hop, and it’s substantially lower than routing to a US or European exit.

Telegram’s Opus voice codec handles jitter and packet loss gracefully up to about 200ms one-way delay and 5% packet loss. All three ISPs stay within these tolerances on LTE during off-peak hours. Rightel on 3G coverage can edge outside the acceptable window during evening peak congestion, but that reflects the underlying 3G connection’s limitations rather than anything proxy-specific.

On throughput, SingTel and StarHub LTE modems in the pool deliver 20 to 60 Mbps downstream through the proxy under typical load. Telegram never requires more than 2 Mbps even for HD video calls, so bandwidth isn’t a constraint. File downloads from Telegram are bottlenecked by the slower end of the connection, which in Iran is usually the LTE downlink to the device rather than the proxy itself. Group media and high-resolution sticker packs that would ordinarily load slowly or stall on a direct Iranian connection download smoothly through the proxy because the bottleneck shifts from the international peering layer to the local last-mile link, which is substantially better provisioned.

Singapore Mobile Proxy targets 99.5% monthly uptime per port. Because each port corresponds to a physical modem on a consumer SIM, brief signal-related interruptions do occur, typically resolved within 30 to 60 minutes. Scheduled maintenance windows are announced in the portal and happen no more than once per month. If your port goes down for longer than four hours outside a maintenance window, the portal support ticket system provides priority routing. For a side-by-side reliability comparison with MTProto proxy methods, see MTProto setup for Iran.

FAQ

Q: do I need to install any extra software to use SOCKS5 with Telegram in Iran?

A: No. Telegram’s Android, iOS, and desktop apps all have a built-in SOCKS5 proxy field. You enter the server address, port, username, and password directly in the app settings. No VPN client, browser extension, or third-party app is needed. The setup takes under two minutes once you have your credentials.

Q: does the proxy work with both the main Telegram app and Telegram X?

A: Yes. Telegram X on Android uses the same proxy configuration flow as the main Telegram app. On iOS, Telegram X has its own proxy settings screen but accepts the same SOCKS5 credentials. Telegram Desktop on Windows, macOS, and Linux also supports SOCKS5 natively under Settings > Advanced > Connection Type.

Q: if MCI or Irancell blocks the proxy IP, what happens?

A: The proxy ingress IP 158.140.129.188 is a Singapore address and is not subject to MCI or Irancell internal blocking. The only action Iranian ISPs can take is to block outbound connections from Iranian networks to that IP at the border. This is possible in principle but has not been applied to Singapore carrier IP ranges in practice, because doing so would disrupt legitimate business traffic at unacceptable political and economic cost. If a block did happen on your specific ISP, contact support through the portal to request a port re-assignment to an alternate ingress address.

Q: can I use one proxy port on multiple devices at the same time?

A: Yes. A sticky SOCKS5 port can be configured on multiple devices simultaneously. All connections from those devices exit through the same Singapore modem, so they appear to Telegram as coming from one consistent IP address. This is safe for account security and is a common setup for users running Telegram on a phone and Telegram Desktop on a laptop.

Q: is my message content visible to the proxy?

A: No. Telegram encrypts all traffic before it leaves your device. The proxy sees only encrypted blobs passing between your device and Telegram’s servers, not message content, contact lists, or account details. Singapore Mobile Proxy does not log traffic content. The proxy ingress logs connection timestamps and bandwidth consumed for billing purposes only.

Q: what if the free trial performance is lower than expected?

A: The trial uses the same modem pool as paid ports. If trial performance is lower than expected, it most likely reflects your local ISP’s routing quality to Singapore at that time of day. Try the connection during off-peak hours (early morning Tehran time) before drawing conclusions. If performance is consistently poor across multiple test windows, contact support before upgrading to a paid plan, as there may be routing-specific options available for your ISP.

Q: can I share the proxy credentials with family members in the same household?

A: Yes, within the limits of your bandwidth plan. All devices using the same credentials share one bandwidth pool and exit through the same Singapore modem IP. For a household of two or three people using Telegram for messaging, calls, and occasional file sharing, the 10 GB Starter plan is usually sufficient. Households with heavier usage patterns or more than three concurrent users should consider the 30 GB Standard plan to avoid running short toward the end of the billing month. Bandwidth top-ups are available from the portal if needed.

Q: how do I update the proxy if my credentials change or the port is re-assigned?

A: Log into the portal at /client to retrieve your current credentials at any time. If a port is re-assigned due to hardware maintenance, the portal will show the updated credentials and you will receive an email notification. To update the proxy in Telegram on Android or iOS, return to the Proxy Settings screen, tap the existing proxy entry to edit it, update the port or password field, and save. The change takes effect immediately without restarting the app.

disclaimer

This guide is informational only. Singapore Mobile Proxy’s terms of service require that all ports be used for lawful purposes. The legal status of proxy use and internet circumvention tools in Iran is governed by Iranian telecommunications law, which restricts unauthorized circumvention of national filtering systems. Users in Iran should obtain independent legal advice regarding compliance with applicable law before using any circumvention tool. Singapore Mobile Proxy does not operate in Iran, does not provide legal advice, and is not responsible for any legal consequences arising from a user’s decisions. For guidance on responsible use of mobile proxy services, see ethical mobile proxy use.