The account graph: how one slip links your whole fleet

Ask most people to picture their accounts and they describe a list. One row per login, each row minding its own business.

The platform on the other side keeps no such list. It keeps a graph. Every account is a node, and every attribute two accounts share draws an edge between them. An IP address, a card number, a recovery email, a device fingerprint. The graph gets built quietly, all the time, long before anything goes wrong. Then one account trips something, and the platform walks outward along the edges to see what else it can reach.

I run proxy and cloud phone farms, and I manage fleets of accounts that have to stay genuinely separate to survive. I have had one careless edge, a line I did not even remember drawing, take out a batch of accounts that were run cleanly in every other respect. The graph is the model I build the whole operation around, so this piece walks through it from the platform’s side. What the edges are, which ones carry weight, and why cleaning up afterwards achieves nothing.

What the graph is made of

Strip the jargon away and a graph is dots and lines. The dots are accounts and the pieces of information attached to them. A card number. A phone number. An email address. A device fingerprint. An IP.

The lines are shared attributes. Two accounts funded by the same card get an edge through that card. Two accounts that logged in from the same device get an edge through that device. None of this waits for you to misbehave. The structure exists so that when the platform needs to know who is connected to whom, it can answer in a single query.

A list can only describe one account at a time. The question a platform hunting coordinated accounts actually cares about goes further than whether one account is bad. It wants to know what else that account touches. That is a graph question, answered by starting at one dot and walking the lines, which is why every serious platform stores identity this way.

The network edge

The most common edge is a shared address. Two logins from the same IP get connected, and the strength of that connection depends on the address itself.

A busy home connection is a weak, noisy edge. Families sit behind those, and the platform knows it. An office IP that touches forty accounts is a different matter, and a datacenter address that no ordinary person would browse from is a clean, strong edge the platform can trust. Every account you touch from one address gets quietly wired to every other account you touched from it.

The payment edge

Of all the edges, the one drawn through a payment method is the hardest to argue with. A card number or a billing address is close to unique and verified outside the platform, so a shared one is strong evidence that two accounts belong to the same hand.

Billing records also never get cleaned up. The fact that one card funded two accounts sits in the ledger permanently, long after the card expired and you moved on. This single edge has ended more fleets than any fingerprint trick ever has.

The quiet edges through recovery details

Recovery contacts link just as hard and show up nowhere on the surface. A recovery email reused across three accounts. A phone number sitting behind several logins as the backup contact. You never see these while using the account, yet they live in the platform’s records and tie the identities together without any help from the device or the network.

People obsess over proxies and fingerprints, then link five accounts through the one number they used to catch verification codes.

The machine, and the message you wrote yourself

The device draws its own edges. The same fingerprint appearing under two account names connects them directly. Storage that survives an ordinary cookie wipe, a local storage entry or an identifier cached in a file, can stitch a supposedly fresh session back to the browser that logged into a different account last week. One browser profile serving several logins joins every one of them.

Then there is the edge almost nobody considers. You write to support from one account and mention another. Or you send the ticket from an email tied to a second login, or ask the agent to move something between two of your accounts. You have drawn an edge by hand, in writing, and handed it over. Support notes become part of the record. I have seen more clean fleets betrayed by a frustrated support message than by any clever detection method, because the operator did the linking personally.

Edges get drawn in a hurry

Almost none of these lines are drawn on purpose. They get drawn under pressure. A login from the wrong network because you were away from your setup, or a top up with the nearest card because the right one declined. A quick fix on your everyday browser because opening the isolated profile felt slow.

Each shortcut is a permanent edge created in a second. The graph does not care that you were tired. The line is the same either way.

What happens when one dot goes bad

As long as every account sits alone, a problem with one stays a problem with one. The moment a single account is confirmed bad, the platform starts at that dot and walks outward. Everything one edge away gets a closer look, and the strong edges, the shared card or the shared recovery number, often get the neighbor actioned in the same sweep.

Edges carry different weights. A shared home IP raises an eyebrow. A login an hour apart on a similar fingerprint raises another. Weak edges like these rarely convict on their own. A shared card or an identical device ID is close to proof. The trap is that you can keep every weak edge spotless and still be sunk by one strong edge, because a single hard line between two accounts fuses them.

The linking is retroactive

An edge does not have to hurt you the day it is drawn. It only has to exist in the record. The platform can log that two accounts shared a card in the spring, do nothing for months, then run a new sweep that traverses payment edges it used to ignore. The account dies in the autumn for a line drawn half a year earlier. A fleet can feel perfectly safe right up until the sweep that walks the edges everyone forgot were there.

The history cannot be revised, either. Deleting the card now does nothing about the record that it once funded two accounts. Removing a recovery email leaves the edge it already created. Changing your IP today does nothing about the logins that already share yesterday’s address. The only edge that never hurts you is the one that was never drawn, which is why prevention is the entire game.

Blast radius

Think of it as blast radius. Fifty accounts with no bridges between them means losing one costs you a fiftieth of the fleet. Run a single card or one shared browser through all fifty and that shared attribute becomes a fuse connecting every island to every other. The count of accounts was never the danger. The count of lines between them decides how far a single failure travels.

So each account has to be a genuine island. Its own IP, its own payment method, its own recovery contacts, its own device profile, with no attribute shared with anything else you run. Islands are also all or nothing. A distinct proxy and antidetect profile per account achieves little if all of them still share one recovery phone number, because that one surviving edge reconnects everything you separated. A fleet is exactly as isolated as its most careless shared attribute.

The discipline is the product

The tools are the easy half. Buying a distinct proxy and profile per account is a solved problem, doable in an afternoon. The hard half is never crossing an edge, once, tired, in a rush, that you spent months keeping clear. The graph is built entirely out of the shortcuts you took.

None of this makes a fleet invincible, and anyone promising that is selling something. Detection keeps improving, and a good enough sweep eventually reaches patterns that used to look safe. What genuine separation buys is containment. When one account gets caught, there is no line for the failure to travel down. It falls alone.

I keep my own fleet separated exactly this way, distinct mobile proxies, distinct profiles, distinct payment and recovery details, because I would rather lose one account than the fleet behind it. The full breakdown of every edge type, how to close each one, and the tools I actually run are at Multi Account Ops.

Get new guides and videos first — join the Telegram channel.