Fair use
Connections, sharing, and fair use
Personal plans are for your own devices and must not be lent, jointly purchased, shared, or resold. Team use must follow the product's stated terms. A connection threshold is not a limit on the number of signed-in devices. Excessive concurrent connections, scanning, attacks, and other abuse may trigger speed limits or account restrictions. Stop abnormal traffic and check for recovery. If the issue persists, submit a ticket with the time and node details.
Connections are not devices
A browser, downloader or app can open many connections, including background sync on the same device. Compare the account's limit with client connection records instead of counting signed-in devices alone.
What to do when limited
- Keep the restriction message, time and node. Distinguish balance, plan, concurrency and account-use restrictions.
- Identify connection-heavy applications and pause confirmed downloads, repeated speed tests or abnormal background tasks.
- Check whether you exposed a local proxy, shared a subscription or leaked a token. Handle the actual leaked credential using account security.
- After stopping the identified traffic, check the new state. If the restriction remains, submit the specific message and reproduction details.
Do not rotate accounts, share credentials or repeatedly reset parameters to bypass limits. Recovery depends on the cause and service rules; not every restriction is temporary throttling.
Read the service terms and product limits before use. For multiple people, choose a plan explicitly allowing team use.