Proxies

Proxy types, connectivity, rotation, and network policies

Every account in your workspace requires a dedicated proxy. The proxy provides both IP diversity (reducing the risk of Telegram linking accounts) and a stable transport layer.

Proxy types

Rental proxies are provisioned from the platform's pool and are exclusive to one account at a time. You cannot detach a rental proxy from one rental account and attach it to another while the first account exists.

Connectivity test

Every proxy undergoes a pre-assignment connectivity test:

1. The platform sends a TCP SYN to the proxy endpoint.
2. If the proxy requires authentication, the platform sends credentials and waits for an HTTP 200 or SOCKS5 grant.
3. The platform performs an IP-leak check by resolving api.telegram.org through the proxy and comparing the egress IP against the proxy's declared IP.
4. If any step fails, the proxy is marked unreachable and cannot be assigned until you edit the endpoint or the test passes on a retry (every 30 minutes).

Rotation

The platform rotates proxy assignments for rental proxies every 6 hours per account. Rotation is automatic and transparent. The runtime re-establishes the MTProto connection through the new proxy without dropping messages.

• 6 rotations per day per account (maximum)
• Rotation is skipped if the account is in cooldown or paused
• You cannot manually trigger a rotation for rental proxies
• For owned accounts with your own proxy, rotation is not available. You must update the proxy endpoint manually

Traffic quotas

Each rental proxy bundle includes 1 GB of outbound traffic per month. Traffic is measured at the proxy layer and includes all MTProto traffic (messages, media uploads/downloads, updates).

For owned proxies used with owned accounts, traffic is not metered by the platform.

Pre-connect IP-leak check

Before any rental proxy is used for the first time in a session, the platform performs an IP-leak check:

1. Open a connection through the proxy to a known echo service.
2. Read the egress IP from the response.
3. Compare against the proxy's declared egress IP range.
4. If the egress IP falls outside the declared range, the proxy is quarantined and a notification is sent.

Reserved network policy

The platform maintains a reserved network policy that restricts what IP ranges rental proxies may use for egress. The current policy allows egress to any public IPv4 address except the following reserved ranges:

• 10.0.0.0/8
• 172.16.0.0/12
• 192.168.0.0/16
• 127.0.0.0/8
• 169.254.0.0/16
• 0.0.0.0/8
• 100.64.0.0/10 (CGNAT)

Any proxy detected egressing to a reserved range is automatically quarantined and removed from rotation.

FAQ

Can I use the same proxy for two accounts? No. One proxy per account. This is enforced at the runtime level.

What happens when a rental proxy fails the health check? The account is moved to inactive status with a 2/hr fallback send budget. A new proxy is assigned automatically on the next rotation cycle.

Can I bring my own proxy for a rental account? No. Rental proxies pair only with rental accounts, and those proxies are supplied by the platform.

What is the proxy latency SLA? The platform maintains proxy infrastructure with a target P99 latency of under 500ms to Telegram's API endpoints. Proxies exceeding 2000ms P99 over a 5-minute window are automatically rotated.

How do I check my current proxy's IP? Go to Accounts > select an account > Proxy details. The current egress IP and assigned proxy endpoint are displayed.