In our Mobile Proxy services, specific usage limits are applied to maintain balanced system performance and provide uninterrupted service to all our users. These limits ensure the stable operation of the proxy infrastructure while forming the foundation of our fair use policy.
The basic limits applied in our Mobile Proxy services are as follows:
These limits apply to a single Mobile Proxy service. If you have multiple Mobile Proxy services, each has its own independent limits.
A connection request is each new TCP connection request made to the proxy server. When you visit a web page or make an API call, you establish a new connection with the proxy server. For example:
The system monitors the total number of connections made within a 60-second time window. When 1000 connections are reached during this period, new connection requests may be temporarily throttled or rejected.
Example Scenario: Usage averaging 500-700 connections per minute is considered normal and works smoothly. However, at intensive usage exceeding 1000 connections, the system's protection mechanisms are activated.
If you have two or more Mobile Proxy services, each service has its own dedicated connection limits. For example:
You can optimize performance by distributing the connection load across multiple proxies for high-volume operations.
By using connection pooling in your software, you can reuse existing connections instead of opening a new connection for each request. This method both prevents exceeding the connection limit and improves performance.
The HTTP Keep-Alive feature allows you to send multiple HTTP requests over a single TCP connection. This way, you can significantly reduce the number of connections.
By controlling the number of requests sent per second in automation software, you can maintain balanced usage without approaching the limits. For example, targeting 600-800 connections per minute is a safe usage range.
If you have many requests, sending them asynchronously (async) instead of sequentially can work more efficiently.
When usage exceeds the per-minute connection limit, the proxy server may respond as follows:
Limit exceeding is typically temporary, and normal operation resumes when the one-minute time window is renewed.
The 1000 connections per minute limit is sufficient capacity for most usage scenarios:
| Usage Type | Estimated Connections | Suitability |
|---|---|---|
| Social Media Management | 100-300/min | ✓ Suitable |
| Web Scraping (Medium Scale) | 300-600/min | ✓ Suitable |
| E-commerce Automation | 200-400/min | ✓ Suitable |
| SEO Tools | 150-350/min | ✓ Suitable |
| Intensive Data Collection | 800-1000/min | ⚠ Near Limit |
| Industrial Scraping | 1000+/min | ✗ Multiple Proxies Required |
If your operations regularly exceed 1000 connections per minute:
Yes, the limit is per proxy. No matter how many devices you use it from, the total per-minute connection count is limited to 1000. The limit is shared among devices.
Currently, there is no live connection counter in our customer panel. However, you can see connection counts from the logs of the software you use or from network monitoring tools (such as Wireshark, tcpdump).
No, temporary limit exceeding does not have any negative impact on your account. However, continuous and excessive usage within limits may be evaluated under the fair use policy.
No, they are different concepts. A thread is a concurrent execution unit in your software. Each thread can open multiple connections. For example, software running with 10 threads can open 500 connections per minute.
For questions about connection limits or high-capacity usage needs, you can contact our 24/7 support team. You can reach us through the support request section on our website or via our WhatsApp support line.