Instagram Follow Block - Mega Thread - Level 1 [SERIOUS]

sorry I didn’t really understand what you are saying. please use less slang. thank you for your answer. do you recommend not using EB while api blocked?

To add up to this, what I basically did was export the statistics from the last 30 days of a sample of 50 accounts.

I took the ones that were currently blocked and tried to find patterns in terms of actions done.

Everyone should be doing this instead of just taking the 6000/30 as facts.
From my sample the problems start at 5k follows and/or unfollows.


That message about “Sharing your account with a service that helps you get more likes or followers…” seems like the final nail in the coffin for people running actions on clients accounts.

They’re going full savage trying to scare and fuck with your clients.
I don’t see clients ignoring this when they can’t even post for a full week.

4 Likes

Got a bit of an unusual situation here that could be causing potential EB blocks with Jarvee users.

Backstory : Account’s never been managed before, never been follow blocked. Account 3-4 years old, posted on every 2 weeks or so, what you’d call a very safe account. Assigned to a mobile proxy and automation started, did about 20 follows in the first day over a 16 hour period (very conservative settings), did 2 follows the next day and got API blocked.

2-3 days later after getting fed up with the API block I swapped to only the Embedded browser and began following. At this point I’d given it the most conservative settings Jarvee would allow
FollowLimits

I presumed Jarvee would continue to use these settings even though it’s going through the Embedded browser over API calls. But when I stopped to check the summary I noticed as soon as I started it, it followed 7 people in almost exactly 70-second intervals.

I’m not an expert, but surely shouldn’t Jarvee be following the settings I’ve laid out for the account, even when its using the EB? Seems like an easy way to get follow blocked, doing actions every 70 seconds.

4 Likes

this is something you should be sending to support to look at. awesome to share with us but if you want it corrected they need to be notified!

2 Likes

Same here for me. That issue only occurs when using EB.

I don’t use Jarvee so can’t help you with their programming bug but with my home brew program, I do 45-75 seconds wait between follows (then 2 min +/- break every random 8-12 follows). Besides the 6000/30day block, I never had any problem. Since I went under 6000 earlier this week, everything (15 accounts) has been running fine even at the same rate(I only lowered total follow per day so I don’t go over 6000).

Just came here to say that my follow block was lifted. It’s been a wild ride so far and I look forward to the future. Let’s get it!

I have been able to follow a bunch of friends back on my phone today (20+) and the while my account has been having the likes and story viewer feature running at a very slow passive rate. I have began running very slow actions with jv on my home internet with very low action rate, things are running smooth so far.

Remember to play the long game here guys…

3 Likes

@ja_son - I reached out to my client I will let you know :+1:

1 Like

Here is something I found out about the recent ‘API’ block, it is not an API block. I think it is related to thrust score. So to start off, only my newer accounts are follow blocked, and one older account (which always had problems, low thrust score).

Some of them were following by API and others were following via EB. Now comes the fun part. If I changed the API ones to EB, they were able to follow again. But today I turned one which was blocked on EB and always has run on EB (still blocked) to API. And this made it possible to follow again. So, this should rule out any API problem.

Think it has something to do with the thrustfactor and/or the adding of accounts to 4G proxies (think this is also part of the thrustfactor). If there are 8 accounts added to one 4G proxy at around the same time and they all use automation, it is not that hard for IG to find out that you are using automation. (This is what I did on the blocked accounts.)

So try to do everything as humanlike as possible, do not forget small details, because everything can hurt your ‘thrust score’. Maybe it has even something to do with the way they are made, because the accounts that are blocked are all from the same account seller.

2 Likes

I manage about 400 clients all in Jarvee had the same block issues starting June 4th. 90% of accounts are back however the rest are still not working with some accounts having as few as 2000 follows in last 30 days. All exclusive data center proxies. Just had a client get the 7 day ban which means they likely won’t be a client anymore. Wasn’t using EB either. Just DM, f/u, comment and Story Views.

3 Likes

That’s very interesting.

What is the 7 day ban?

1 Like

There are multiple filters from IG that can block an account, not just 6000/30.
Im unfollowing at all the accounts until we have some more information about this

1 Like

Extra Update:

So the ones who were API blocked and which I transferred to EB are now also able again to follow in API. I think it is a combination of thrustfactor and your settings.

2 Likes

did you transfer to EB with same settings?
how long did it take?
how many accounts?

I do have some api blocks that last 5 days.
I found a solution for it that I am still testing, so I can’t share now. maybe I will share in lvl 2 if managers here will upgrade me.

Wich web software are you testing ? Kind of instazood?

Thanks

@lochorui I use Instazood and things are no better over here either sadly.

did you transfer to EB with same settings?
how long did it take?
how many accounts?

I do have some api blocks that last 5 days.
I found a solution for it that I am still testing, so I can’t share now. maybe I will share in lvl 2 if managers here will upgrade me.

Yeah same settings and directly. It only happens on accounts from the same account seller, so I just think it is thrustfactor. This can also be the case for clients who made their account the wrong way or have many accounts. It is no API block, cause I also had some test accounts on EB and they also received the blocks and the blocks disappeared after turning to API.

They disappeared directly after switching, but I only switched back after 7 days, so I dont know how fast you can switch back.

You just need to earn your level 2, if you have a solution, you can just post it here.

2 Likes

I don’t want to worry you, but probably after 20-50 follows the follow block will be back - I have been there.

I think it’s a problem with Jarvee. I have API blocks on 10 client accounts (for over 250) - both on mobile and DC proxies. Reseting device ID is helpful just for couple of minutes. All of them are blocked only in Jarvee (they can perform actions on phones and browsers).

What is interesting - when I moved these blocked accounts to another software made for IG automation purposes (not private/mobile API like Jarvee, but web API) - everything works perfectly.

It is not an entire API block, because my EB accounts were also banned. So they ban you via the API or EB, so no problem with the API. The only thing I found within my test accounts is that the ones which are not made by myself (aka bought from the same supplier) are the ones receiving blocks. So maybe just thrustfactor issues.

1 Like

How do i run accounts on eb?