Early access opens to founding users from December 2026Apply
TinyCoal
Guides · Fixing common problems

What happens when a proxy drops, and how to handle it

Giving each account its own fixed network exit is common practice for teams running accounts in several countries. Sooner or later an exit goes down: the provider runs maintenance, the line gets unstable, the plan expires. The drop itself isn't the problem. The problem is not noticing, or your software quietly switching to your own network and carrying on without telling you.

TinyCoal Editorial Team · Published · Updated

The bottom line: when a proxy drops, you'll usually see one of three things: pages won't open or only half load; the login acts up and you're asked to sign in again or verify; or, most dangerous of all, the software or browser falls back to your own network automatically, so the account's location jumps from the local city to wherever you are. The right move is to stop when it drops: pause everything on that account, fix the exit or replace it with one in the same location, confirm the exit location, language and time zone are all correct, and only then open the account again. Never "use my own connection just for now".

What you might see when the connection drops

"The proxy dropped" can look very different from one time to the next. The table below sorts it by what you can actually see, with the risk and the fix for each:

What happenedWhat you'll seeRiskWhat to do
Fully disconnectedPages won't open, keep spinning, or show a connection timeoutLowest: nothing went out, you just lose timePause the account; check the exit; once fixed, test the exit location before opening it
Dropping in and outPages half load, images don't appear, uploads stall partwayUnclear whether posts or replies went out; retrying may send the same one twiceStop; once fixed, check the profile and message history, and only fill gaps you're sure about
Fell back to your own networkPages load as normal, but an exit check shows the city where you areHighest: the account's login location suddenly jumps across countries, which often brings a new verification requestClose the account's environment at once; find out why it fell back; turn off any "connect directly on failure" setting
Still connected, but the location changedThe provider switched IPs automatically, and the city or even the country changedThe account's location is unstable and no longer matches its language and time zonePause; ask the provider to switch back to the same city, or move to a fixed exit
Some requests skipped the proxyThe page shows the right exit, but a test site shows some requests revealing your real IPWebsites can see where your own network isPause; check that DNS and WebRTC settings in the browser and software also go through the proxy
Login acts up after the dropOnce reconnected, you're logged out or shown a captcha or two-step verificationNeeds the account holder in person; handled badly, it can lock the accountThe holder handles it on the official login page; first confirm the exit is back at its original location

"Often brings a new verification request" in the table reflects general experience with sudden login location changes. TikTok hasn't published what happens when the login location changes, and we couldn't find any official guidance on it.

Why "stop when it drops, never fall back to your own network" matters so much

The point of giving an account a fixed exit is that, to the platform, it always looks like it's being used in the same place: the exit is in Jakarta, the interface is in Indonesian, the time zone is Jakarta time, and posts go out during the local day. When those things line up, the account's activity is steady and makes sense. See Matching language and time zone across countries.

The moment it falls back to your own network, several things go wrong at once:

  • The location jumps. One minute it's in Jakarta, the next it's in another country.
  • Language and time zone no longer match the exit. The interface is still Indonesian and the time zone still Jakarta time, but the exit is somewhere else. The account's activity stops adding up.
  • You don't know it happened. Pages work as normal, so you keep answering messages and posting videos until a verification request the next day tips you off.

Compared with that, the cost of stopping is a short delay. Weighed against each other, stopping always wins. Keep one platform rule in mind too: TikTok's Community Guidelines state that once an account is restricted or banned, you can't open a new account to get around it. When something goes wrong with an account, there's very little room to recover, so prevention at the source matters.

What to do first, and what comes next

  1. Stop. Pause all scheduled posts, automated tasks and anything in progress on the account, and close its browser environment. If other accounts use the same provider, take a quick look at them too.
  2. Don't log in on your own network. Not even "just to check messages". Wait until the exit is fixed. Anything urgent can be handled by the holder in the official Business Center or on their phone first, as long as that's how the account is normally used anyway. For what Business Center can do, see TikTok Business Center vs. third-party tools.
  3. Work out where the problem is. Does your own network get online? Do the provider's other exits work? If only this one is down, it's this exit. If they're all down, it's the provider or your own machine.
  4. Fix the exit or replace it. Fix the original one if you can. If you have to replace it, choose a fixed exit in the same country and city where possible, and don't share it with any other account.
  5. Test the exit before opening the environment. Once reconnected, confirm the exit's country and city match the original, no requests are revealing your real IP, and language and time zone line up. Then open the account.
  6. Check what happened during the drop. Look at the profile to see whether scheduled videos went out, and at the message history to see whether replies were delivered. If a result is unclear, check before doing anything. Don't just send it again.
  7. Deal with login and verification. If you were logged out or asked to verify, the holder handles it in person on the official page.
  8. Write it in the check sheet. Note which exit, what time it dropped, how long it was down and how it was fixed. If the same exit drops several times in a week, it's time to replace it. See the daily checklist for multiple accounts.

How to choose a stable exit

You can't avoid drops completely, but you can choose exits that drop less often and don't jump to a new location when they do. The table below lists what to look at when choosing and trialing an exit. Set your own pass marks based on your business:

What to look atHow to checkWhy it matters
Whether it's fixedAsk whether it's a long-term fixed IP or one that rotates automatically by time or requestA rotating exit keeps changing where the account appears to be used
Whether the location matches the accountUse a test site to see the exit's country and cityThe exit location is the baseline for language, time zone and posting times
How many accounts share one exitKeep your own record of which account uses which exit. It can live alongside your account naming sheet; see How a team manages multiple TikTok accountsOne exit per account means a drop only affects one account, and you know straight away which one
Drop frequency and latencyTrial it for a week, noting how many drops each day and the usual latencyMore reliable than the provider's advertised figures
What happens on a dropDisconnect it once on purpose and see whether the software and browser stop or switch to your own networkDecides whether a drop means "a short delay" or "a sudden location jump"
Provider noticesWhether they warn you ahead of maintenance, expiry or line changesYou can pause in advance instead of cleaning up afterwards
Backup planWhether there's a standby exit in the same city you can switch to at any timeIf the main exit is down for a long time, you can switch without changing location

Cheaper isn't better, and neither is more expensive. Let a week of real records decide: how many drops, how long each one lasted, and whether the location changed afterwards. Only keep exits that are steady on all three.

How to set up checks and alerts

If you rely on people to notice drops, you'll always notice late. Whatever tools you use, you can set things up along these lines:

  • Turn off "connect directly on failure". Look through your browser's proxy settings, proxy extensions and system proxy software for options like "connect directly if the proxy fails" or "addresses that skip the proxy", and turn them off or limit them to local addresses. This is the most direct way to prevent falling back to your own network.
  • Send DNS and WebRTC through the proxy too. Routing web pages through the proxy isn't enough on its own. Open a test site that shows DNS and WebRTC addresses and confirm your own network's address doesn't appear.
  • Check four things on a schedule. Is it connected, has the exit city changed, is latency normal, has it fallen back? Match the frequency to how active the account is: accounts with automated posting or replies running should be checked more often.
  • Pause automatically when it drops. When a check finds a problem, stop the account's tasks first, then alert you. The order matters.
  • Send alerts somewhere you'll definitely see them. A red dot in a corner of the app that nobody sees overnight is no alert at all.
  • Review once every morning. Exits that dropped overnight and came back on their own still get a line in the check sheet.

The most common mistakes

  • "I'll just answer one message on my own connection." The few minutes saved can cost you a cross-country location jump and a verification request.
  • Grabbing any working exit the moment one drops. Switching to another country creates exactly the location jump you were trying to avoid. If you switch, stay in the same city.
  • Reposting everything unconfirmed as soon as you're back. Some of it already went out, and posting again means the same post appears twice. Check first, then fill the gaps.
  • Sharing one exit between several accounts. One drop hits a whole group of accounts, and when you troubleshoot, you can't tell which account's activity went wrong.
  • Only checking the exit shown on the web page. The IP on the page can be right while DNS or WebRTC still use your own network.
  • Treating drops as too minor to record. Without records, you can't see which exit or provider keeps causing trouble.

How to tell you handled it properly

What to checkHow to check itWhat good looks like
Nothing fell back to your own network during the dropLook at activity logs and check recordsNo activity on the account while the exit was down
The location didn't change after recoveryTest the exit's country and cityThe same as before the drop
No duplicate postsGo through the profile post by postEach post appears exactly once
The drop was caught quicklySee how long passed between the drop and the pausePaused automatically, not discovered by someone the next day
Problem exits were replacedLook back over a week of check recordsExits that kept dropping have been swapped out

How "pause when it drops" works in TinyCoal

You can set up everything above by hand, but with many accounts it's easy to miss something. TinyCoal gives each account a separate environment with its own fixed network exit. If the proxy drops, that environment pauses immediately and does not switch to your real network; DNS and WebRTC also go through the proxy. Daily checks and reports test the exit's city, latency and whether your real IP is leaking, and flag it when the same IP is used by two environments. Posts that didn't go out during a drop are marked in the publishing schedule with the reason "proxy disconnected", and anything with an unclear result is checked first rather than posted again. Messages and comments in the unified inbox are only sent after a person confirms them, so no reply slips out on its own during a drop. Check records and activity logs stay on your own computer; see Local data and privacy and our Privacy policy. These measures reduce the mess a drop can cause, but they can't guarantee an account won't face platform enforcement. Details are in our Terms of service.

The teams with the most exits are usually cross-border sellers and agencies, with one group of accounts per country, so managing drops is part of daily life. Other team types are in Who it's for, and everything TinyCoal does is in All features. If you haven't decided whether you need a tool, start by working out how much time checks take each day; see Running 20 accounts on your own: how long it takes. If views dropped after an outage, work through the no-views checklist.

FAQ

The proxy dropped for a few minutes and came back on its own. Do I still need to do anything?

Check three things: whether the exit location changed after it came back, whether any activity went through your own network during those minutes, and whether any post or reply is in an unclear state. If all three are fine, just make a note of it.

How many accounts can share one exit?

We suggest one exit per account. The platform hasn't published a rule on this, and we couldn't find any official guidance. The benefit of one per account is that a drop only affects one account, and troubleshooting stays simple.

I need to move an exit to a different city. What's the safest way?

First be clear about why you need to move it. If you can avoid it, don't. If you really have to, adjust the language, time zone and posting times to the new location at the same time, then watch the account for a few days before going back to your normal pace. More questions are in the FAQ, and other methods are in Guides.

Sources

The parts about TikTok's rules are based on the official pages below, read on November 20, 2026:

What we could not verify (and therefore did not write): how TikTok handles changes in login location; what triggers verification; how the platform decides which country an account is in; any official guidance on how many accounts can use one network exit; how long an exit can be down before it affects an account. The drop scenarios and suggestions in this guide come from general experience with network connections, not from platform rules. TikTok is a trademark of its owner. TinyCoal is not affiliated or partnered with TikTok.

Small spark. Great fire.

A desktop app for Windows and Mac. Early access opens to founding users in batches from December 2026. General release in Q1 2027.

Join early access