Phone Farm Instagram Account Bans: Am I Crazy?

[OKKO]

Are you saying that his setup is wrong? Or phone farming isn't worth it anymore?

Both. His setup is aggressive enough that it’ll trip flags even if the automation “works”, and phone farms in general aren’t forgiving anymore unless you run them like a slow, high-touch operation.

 

[Alexei777]

I recently spent $7,500 on a phone farm setup from someone on here, and we’re about two weeks in, but it’s been having consistent issues the entire time.

The setup is 3 iPhone 7s, each connected to T-Mobile. The provider configured everything using Dopamine / Sileo / Crane along with Appium for automation.

Overall, the automation seems well-built, but during the first ~10 days it had problems like posting multiple times on the same account or getting stuck on random screens, which would stall the workflow. Those issues have mostly stopped now… but the bigger issue is that almost every account is getting banned.

He built two automations:

1. Account creation automation (creates an account and makes one post, then moves to the next account)
2. Posting automation

He recommended running 100 IG accounts per phone, since posting 2x/day across that many accounts takes roughly 24 hours to cycle through everything.

For content, we’re using a mix of pre-designed templates and a repurposing tool (TikFusion) to generate variations and avoid duplication flags. But even with that, we’re still losing accounts. I even tested using 100 completely random (and unique) videos from my personal camera roll, and the accounts were still getting flagged 20–30 minutes after posting.

When I say “banned,” I mean Instagram starts forcing a CAPTCHA / “verify you’re human” prompt, and the accounts quickly get disabled afterward.

At this point, my gut says it’s something with the setup itself—possibly the automation behavior, device fingerprinting, or the way it’s rotating IPs. The provider is basically implying it’s on us to troubleshoot, but I paid $7,500 and this has been happening since day one. He tried to say it was the content’s fault at first, so that’s why I ran the experiment of posting my own random personal videos, and the same thing happened.

It’s extremely frustrating to spend $7.5k and follow every single step they tell you, then have them tell you it’s essentially your fault and to figure it out.

If anyone has any ideas on what could be causing this (or how to stabilize it), I’d really appreciate the help. Thanks in advance.

Did you received something like: “account disabled, verify your identity”?

The whole configuration is bad because it’s combine wrong things.
But let’s spoke about what your automation is doing in the first place - so create an account + one post and then move on to the next one.
No warming up your accounts.
So from IG point of view you are a bot.
Why? Because you are not using a human behavior.
Think about this:
You’re creating a personal IG account. You’ll write your name, username, maybe a short Biography.
Then what? Are you posting directly a photo for your “feed”?
No! Why? Who supposed to see that one since you have 0 followers?
So the next step is to just take a look, to use the search option, to scroll, to follow a couple of accounts (not 50,100,1000), to check the reels section, so to act as someone new to their platform who will spend some time to see what is about.
You’ve to do these things daily.
Spend time on IG, post, then spend time again (like you are checking if someone engage with your post).

To keep this short, the thing is IG will know that you are using Crane for eg. because it’ll analyze the behavior.
But this will not be a huge problem.
But it you are using Crane + Appium + no warming up your accounts of course that you’ll get a ban because for them you are 100% a bot.

 

[SpawneR]

I ALWAYS said and maintained that phone farms are extremely complicated to maintain at scale and almost impossible to deploy for good automations. The cost/benefit vs anti detect browsers which can be made relatively bulletproof, but not off the shelves is just not there.

Here is what you are dealing with:

Device fingerprints are permanent.Even real phones have a single, highly trackable fingerprint (IMEI, device ID, OS/hardware combination). Factory resets or account rotations do not magically hide it. Instagram and other apps can detect repeated device IDs across accounts.

A mobile proxy might hide your IP, but it does not mask your device fingerprint or the network characteristics. Things like cell tower triangulation(are you folks fucking reading this?), carrier metadata, and timing patterns are often visible to the platform. That’s why accounts are flagged even if each phone has its own T-Mobile connection.

True location obfuscation requires spoofing GPS, Wi-Fi SSIDs, and cellular triangulation simultaneously, plus careful timing of activity. There is no easy way to trick IG into thinking your phone farm is multiple independent humans on unique networks.

Not having a captcha solver or a real warmup process is basically inviting bans. Even legitimate anti detect setups include warm-up and interaction simulation over days or weeks, not immediate mass posting.

Spending $7.5k on a small iPhone farm with a few mobile proxies is almost guaranteed to fail against IG detection systems. The platforms have far more visibility into devices, networks, and behavior than most setups account for. Even vectored antidetect browsers or hosted antidetect solutions are orders of magnitude easier to manage than real phone farms if you care about survival.

And this is just the surface layer facts, this goes deeper technically, but I think the point is clear.

If you do not know how to deal with all the above, you have not even got your toe in the door, there is much more to this.
Look at all the "SMM" BS panels, all are useless, if not to say corrosive/radioactive to use.

Saying that Anti Detect browser is better for automation than using phone farm for INSTAGRAM is really dumb. It shows that you have no idea of the topic and you just yap to look smart but in the end you are not, because you probabbly never did botting on Instagram yourself.

OP:

Did Invictus sold you that 7.5K automation?

 

[theusualkeysersoze]

Saying that Anti Detect browser is better for automation than using phone farm for INSTAGRAM is really dumb. It shows that you have no idea of the topic and you just yap to look smart but in the end you are not, because you probabbly never did botting on Instagram yourself.

OP:

Did Invictus sold you that 7.5K automation?

Calm down Nancy and perhaps show me your IS SMM panel which does not exist. Show me what you got instead of running your mouth. Ill tell you what I have, headful browser bot passing as human running posting, scrapin and various other interactions across 500+ LI accounts.

Or, read again, I said it is vastly more complicated and expensive to run ana utomated phone farm that does automated tasks without blowing up or shadow banning the accounts by proxy. It far easier and cheaper via AD browsers emulating a Windows environment and that is all.

Maybe you wanna tell to the people, are your little phone farms real devices or cloud devices, how much does one device cost you to acquire and to run, when you root them, how do you make sure that is not obvious, lets just stop there, you go and "develop" your wanna be phone automations that do not exist.No wait, how do you match the gelolocation and triangluation data to the proxy? Be precise, I can follow the technical aspect, tell me how it is done. I think this is sufficient for the first batch of questions, I will not be holding my breath. Addendum, how do you reproduce human jitter, you gonna tell me that is easy, right? And what do your automations do.

I know the answers, it is all metaphorical questions.

For an anti detect environemnt, you run this from a windows server with gpu and audio drivers, GO scheduler and nodejs browsing orchestration and hook in static isp proxies and you are good to go. Costs a handful of usd per profile.

Now you tell me about your "automations" , how many accounts per phone, maintenance cost, acquisition cost etc.

For the people who are naive enough to believe to buy into these SMM panels and people once naive like the OP, if you do not wanna have a rude awakening, do not buy into these promises, not before having real world video proof and tried for sure.

I do not even care really, I have my very own made bots and videos available and folks from VectorT13 interested in them, you do not have jack shit, if you had any worthwhile mobile automations theyd be the first to knock on your door, amongst many others.

Show me the money, talk less.

 

[SpawneR]

I am not quite sure which F20-29 or F30-39 suits you.

But since you think I am stupid, and you are smart, tell me, what is the percentage of Instagram users using it via Windows Desktop? Oh, okay, so the number is below 1% right? Oh, now tell me, when you put 100 accounts, to mass DM, Mass Follow or whatever user wants using WINDOWS, from the same ISP Pool of proxies, what do you think will happen?

Don't get me wrong, Anti Detect browsers are waaaaaaaay cheaper, and they work great for automation and I personally use thousands of profiles daily for my own work, but STATING that Anti Detect browsers are better than Phone Farm is just outrageous.

 

[deusdeorum]

First off, I'm sorry that you got scammed. I hope you find a resolution, or maybe this is one of those 'hard lessons' that make you stronger and smarter.

To begin - You kinda got scammed. Phone automation is a complication job. But what is more complicated is ... Instagram.

A coder maybe 'great' at coding phone automations whilst at the same time truly 'suck' at understanding the megalodon that is Instagram. I think this is the mistake you've landed in.

Just to clear the floor, I have some points. This is coming from someone who's running a phone farm on custom software (in-house dev, so don't ask for contacts or stuff). I won't disclose the amount of phones or profiles for privacy but it's a decent sized operation.

#1 - Phone farm is indeed a great way for automation. It can be a breeze if done right. And give you lots of superpowers in ways most people just cannot imagine.
#2 - I get close to 0% ban rate on my profiles, closing in on 2 year anniversary of my farm. Using a phone farm the correct way really does mean you get 0 bans. This is first hand experience.

Now, lets talk about mistakes that I would assume you're making (assume being the keyword here)

#1 - Warm-up is crucial. No matter what. If you create an account and starting posting right away, that is risky AF. I've done months of R&D with my team before I started my farm, and we realized once you setup the account, it's best not to post or maybe post a few hours later (after warm-up), and make it just one post.
#2 - Creating accounts itself is hard. If you're leaking your OS/5G/Hardware data, you're fucked. And your coder is a noob. If you're using cloned apps that are spoofed hiding every possible hardware data, device integrity data, then you have a 'chance'. On top of that, using mobile numbers instead of emails gives a far better trust score, so go that route. Later, add a Gmail email, again, better trust score.
#3 - Warm-up, warm-up and warm-up. BUT - and this is a big one ... with 'HUMAN EMULATION'. Make the profiles run Instagram like a human would. Do this ... (its what we did) ... record yourself using Instagram for an hour. Just chilling. And watch that recording. What do you do? Take notes. And then coder builds emulation around that. There's 1000+ touch points that go into 'human emulation'. Without this, you're just asking to be banned.

Everything can be 'cracked', it's just that your coder has no experience from the way you're describing things. If he said 'posting' is 'warm-up'. Fuck.

That video thing is smart. Do you use your farm to grow/promote your own stuff?

 

[DICloak Browser]

It sounds like the main issue here is likely related to device fingerprinting and IP rotation rather than the content itself. Instagram is flagging automation behavior — even with unique content, the automated posting and session patterns are detectable.
To stabilize the accounts, consider using antidetect browsers that mask device fingerprints, isolate sessions per account, and provide better IP rotation control. Automation behavior needs to mimic real user patterns to avoid bans. If the setup doesn’t address these technical issues, the accounts will continue getting flagged.

 

[banjozinko]

Your setup appears to be heavily flagged, and honestly, it seems overpriced. You should reach out to the seller to address these issues. Not warming up accounts is a serious mistake—we always warm ours up through our farm before posting.

Hey Fillip. Would you sell me your phone farm tech and knowledge?

 

[Nendande]

He recommended running 100 IG accounts per phone, since posting 2x/day across that many accounts takes roughly 24 hours to cycle through everything.

Running 100 Instagram accounts on a device is red flag.

 

[Mc125997]

@theusualkeysersoze @SpawneR @Invictus @xWGx

Do any of you have an idea on how i can achieve my goal of operating hundreds of social media accounts that I can post reels/videos on? Preferably on instagram or TikTok?

The guy ended up blocking me and running off with my $7500. It's BS and it sucks, but I still need something that works. One of you geniuses on this site knows how to make it happen and can service me with a working solution. I know it

I know for a fact people are running working operations. I just need the person who knows how to get it done and can deliver.

 

[swissrdp]

why you dont use captcha solving services for that

 

[Mc125997]

why you dont use captcha solving services for that

1) The guy I bought the service from didn't have that in the automation
2) Even with a captcha solver, if every account is generating a ban... there has to be a deeper issue

 

[VAT]

I believe Crane is dead to build new accounts. I've personally built IG accounts to 100k+ followers and million of views. But now seems like accounts hit a brickwall. They pop off for a while and then collapse overnight.

Building new accs on crane seems pretty much impossible. The best use case for crane is to run already established accounts.

 

[swissrdp]

1) The guy I bought the service from didn't have that in the automation
2) Even with a captcha solver, if every account is generating a ban... there has to be a deeper issue

i have same system and no problem for me. this guy maybe amateur about automation. you need 2captcha api for solving captcha, captcha coming every account even my personal on my phone

 

[Moonslice]

Why phone farm ? I'm still having success with android emulators. Residential proxies are the real investment here.

 

[Mc125997]

i have same system and no problem for me. this guy maybe amateur about automation. you need 2captcha api for solving captcha, captcha coming every account even my personal on my phone

After you solve the captcha, is it typically smooth sailing from there?

 

[theusualkeysersoze]

why you dont use captcha solving services for that

You can't just resolve every captcha, mate, some captchas are Easter eggs laid so to expose you as a bot.

I am working on a reddit account creation bot and they're everywhere.

 

[DQ Agency]

Based on what you described, this doesn’t sound like a content issue at all. When accounts get hit with CAPTCHA and disabled that quickly (20–30 minutes), it’s usually a behavioral or environment signal, not duplication.


High account density (100 accounts per phone), heavy automation, and very predictable posting patterns can easily trip platform risk systems — even if the content itself is clean and unique. Once a device or environment is flagged, new accounts created or operated there tend to fail fast regardless of what you post.


In cases like this, swapping content rarely helps. The root cause is more often automation behavior, account velocity, device-level trust, or how actions are sequenced, rather than creatives. Unfortunately, this is also why phone farm setups often look good on paper but struggle in real-world stability.


I’d be frustrated too after following the provider’s instructions. At minimum, they should help diagnose whether the issue is structural instead of pushing it back on content.

 

[theusualkeysersoze]

Running 100 Instagram accounts on a device is red flag.

Omg I have just only now seen this, it's not just a red flag, this is more red flags than exist in China accumulated lol.

@Mc125997

I agree with the sentiment, why do people think mobile farm orchestration automation is better than an anti detect orchestration, it's 100 times worse.

There's not a single freaking operator out there that is not doing it managed by humans and the smm panels don't work, think about that for a minute. I phone handled by a human is under some circumstances better than an anti detect setup but people really have not much of an idea how hard this is to program. I really mean 100 times worse.

Arguably, LinkedIn is hard, right. So I have had something like 700 LinkedIn accounts running concurrently over 3 servers, they lived for quite long, some will die, some will re auth, it's fine, can't lose sleep about a bit fallout if you did everything you knew you could. So I do have A literal and precise proof of concept, not just an idea. But I wouldn't dare to do it via mobile, I believe I can say I am a decent dev(full stack senior), but a real mobile device multi accounting orchestration which mimics real users? With the access that apps are given on phones? Nope. Windows emulation? Yeah, I know exactly and precisely. It's also never a one off handover, api changes, front end frameworks change, reddit uses shadow root nowadays, great "fun" to work with that. This also goes beyond just dev work, you must know exactly how anti detects and proxies work, I don't wanna sound rocky, but most people do not know how they work , it's not plug and play with default settings and forget about it. So this kinda requires IT knowledge, too.

I know you're in a tight spot and judging if someone is competent to do something or if it's just bs is hard for a non dev, you need a dev that can go beyond creating a little crud app, you need someone to deploy and maintain the whole thing. I could, but I am pretty well booked out for the time being, I took some projects I really like working on, but if truly interested, create a HAF thread or WTB and send me the link, as that's the forum rules.

You see, this is a post that took me 20 minutes to compose so I will not sugar coat a turd, if it's windows emulation, I can do, if it's mobile orchestration, that's radioactive and I wouldn't even touch that for 7 grand, because that'd thin out to 1 usd per hour only to never have it work, nobody has it working, nobody.

My 700 LinkedIn account do 247 actions, literally non stop, it works, it's windows emulation and it'd never have worked from mobile, and mind you, was pretty dear to make, too.

Be sceptical if someone says fully automated real mobile device orchestration for xxx accounts, it's very very complicated.

 

[Alpabism]

At this point, the question isn’t how to fix this setup but whether it’s worth fixing. Phone farms stopped being forgiving years ago, and most people burning money now are fighting signals they can’t see or suppress.

Are you saying that fixing is not an option because it's not worth it anymore now?