Follow Block On EB & API - Help

Joined
Apr 18, 2019
Messages
39
Reaction score
6
Does anyone know how to get past these follow blocks? I am on 4G, still seem to get super random blocks and all accounts are on EB. Accounts were running fine on API last week and now all of a sudden, starting Sunday, got hit with a lot of API blocks. I turned down settings, but still getting blocks for a lot of my client accounts. Any help would be much appreciated.
 
Randomize as much as you can and don't run more than 5 accounts at a time per 4g. You can make it run in shifts with ultra timings
 
Randomize as much as you can and don't run more than 5 accounts at a time per 4g. You can make it run in shifts with ultra timings
I currently have 1:1 proxies from HC. settings are super randomized with very large gaps and large seconds in between follows.
 
is 5/shift your personal experience?

Please excuse me for not following, what do you mean?

Yes @Naroha, it is! I know people that are doing 30 accs/proxy. The timings need to be lasered sync. Tip: Use nightmode

@RokitFocusrite - Let's say you have 10 accounts that use 1 proxy. You split them in 2 batches:
Batch 1 run from 12 AM to 12PM then rest 12PM to 12AM
Batch 2 rest from 12 AM to 12PM then run 12PM to 12AM
 
Would someone please be able to recommend me 4G proxies located in Los Angeles?
 
Would someone please be able to recommend me 4G proxies located in Los Angeles?

I am just trying to keep my clients safe, do not mind spending a little extra money. I would rather spend a little extra money and go to sleep with ease.
 
My accounts run only on API, EB gave persistent blocks to accounts. Jarvee provides API UserAgents, but very old/incorrect API agents for phones that shouldn't have that API that Jarvee has given. Rather edit those with updated API's found on the net. Instagram generally blocks bad API UserAgents. Like, I saw on mine that the device is from 2012, discontinued, last Android version on the phone was 4.0, screen is 720x440 with 246 DPI but UserAgent Jarvee gave was Android 8.0 with 1990x1440 and 540 DPI? Not gonna work. Updated API's have proven to work for my accounts.
 
My accounts run only on API, EB gave persistent blocks to accounts. Jarvee provides API UserAgents, but very old/incorrect API agents for phones that shouldn't have that API that Jarvee has given. Rather edit those with updated API's found on the net. Instagram generally blocks bad API UserAgents. Like, I saw on mine that the device is from 2012, discontinued, last Android version on the phone was 4.0, screen is 720x440 with 246 DPI but UserAgent Jarvee gave was Android 8.0 with 1990x1440 and 540 DPI? Not gonna work. Updated API's have proven to work for my accounts.

Perfect. With that being said, how do I know if my API is old? Don't understand why Jarvee cant put them on newer APIs?
 
My accounts run only on API, EB gave persistent blocks to accounts. Jarvee provides API UserAgents, but very old/incorrect API agents for phones that shouldn't have that API that Jarvee has given. Rather edit those with updated API's found on the net. Instagram generally blocks bad API UserAgents. Like, I saw on mine that the device is from 2012, discontinued, last Android version on the phone was 4.0, screen is 720x440 with 246 DPI but UserAgent Jarvee gave was Android 8.0 with 1990x1440 and 540 DPI? Not gonna work. Updated API's have proven to work for my accounts.

What you're also saying is all your accounts are running fine with API right now?
 
Easy enough to check, simply google the phone that Jarvee is trying to emulate. Yeah my accounts run fine through API, 5%+- have persistant blocks and have to work via EB buts it's not too hard to manage.
 
Easy enough to check, simply google the phone that Jarvee is trying to emulate. Yeah my accounts run fine through API, 5%+- have persistant blocks and have to work via EB buts it's not too hard to manage.

Oh this is interesting...

I've had a google, but can't decipher this: 27/8.1.0; 480dpi; 1080x1920; Samsung;a5xelteskt;SM-A510S; qcom; en_US

480dpi is screen res, 1080x1920 is size, SM-A510S is the model... what's the other stuff? is the OS 27/8.1.0?
 
So from my experience the things that tend to help an account last the most is the way in which it was made, the uniqueness of the content, and the settings of the bot.

Usually once an account is made, it has a trust score initially given to it that determines how closely Instagram's bot detection API watches the future actions of the account. Instagram lists what they track in their privacy policy.
https://help.instagram.com/402411646841720

Analytics information: This one seems to be influenced the most by your bot settings.

Cookies and similar technologies: This one is affected by how clean the browser or mobile device is that you make the account on (there are ways to completely wipe browsers and devices)

Log file information: The biggy here is the IP address that they log. It seems the IP the account was made on affects the account's lifespan the most. Another thing is that you have to look at the network layer of the device. When sending packets, TCP/IP adds a lot of information on multiple layers. Proxies can only influence the topmost or HTTP layer of a packet. If you go to the IP layer however there's a header called the TTL. I'll let you research that, but different operating systems and devices assign different numbers to this value. So even if you're spoofing a User Agent of a browser, that's only affecting the HTTP header. You'll have to figure out for yourself what number your operating system assigns and how you can change it to mimic other devices. Hint: Look up Passive OS Fingerprinting

Device identifiers: Again this is another reason why a spoofed user agent isn't enough. Instagram is a lot more evasive on people's devices than they think.

Metadata: The information IG gives here is one where you have to read between the lines. If you're using the same content on multiple pages, YOU MUST at least be aware of how they can be traced and linked to one another. After you do that you have to learn how to change all of it. Hint: Look up file hash, pic metadata, image comparison algorithm

Once you know how to make extremely clean accounts, then you can get somewhere in terms of testing settings. I say this because I've gotten away with some pretty aggressive settings recently on new accounts as well as new accounts that kept getting PV'd every other day on some extremely lax settings. It seems that the more Instagram trusts an account initially, the more you can get away with. There are a few other secrets that I've figured out as well but I kinda don't even wanna give the hints out for those. I said that part to say keep testing, there are always small little exploits in code no matter how strict it seems. One day you might stumble across a few that make no sense why they work but they just do. Keep going.
 
I am using Jarvee for all my client accounts. How do they screw you? Everyone is on EB.

No one is on API as of this last fucking block that happened this past Saturday :/

Is Jarvee working?

I have been using GMT2 for the last 8 months. I used FL before that. GMT2 has not been working since the update in June. I have a lot of clients and I am starting to lose them one by one.

Is Jarvee having similar problems with action blocks? If Jarvee is working, what are safe action limits at the moment? I am seriously considering moving over to Jarvee or any software that is currently working with the new algorithm.
 
Is Jarvee working?

I have been using GMT2 for the last 8 months. I used FL before that. GMT2 has not been working since the update in June. I have a lot of clients and I am starting to lose them one by one.

Is Jarvee having similar problems with action blocks? If Jarvee is working, what are safe action limits at the moment? I am seriously considering moving over to Jarvee or any software that is currently working with the new algorithm.

You are having issues with client accounts? What proxies are you using? I know people still have some trouble with spammy crappy accounts (expected) but real accounts should be working fine through automated API requests (unless you are still trying to bot like 2018 and pushing 800+ follows a day
 
You are having issues with client accounts? What proxies are you using? I know people still have some trouble with spammy crappy accounts (expected) but real accounts should be working fine through automated API requests (unless you are still trying to bot like 2018 and pushing 800+ follows a day

I am getting action blocks since the June update (as are a lot of people as far as I know). I am using dedicated proxies from a provider in my country that I have been using since 2016-2017 with no issues.

I reduced my settings in June to 20-80 follows a day with 4-8 min rests in between operations and less then 6 hours a day. 10-60 likes a day with 4-8 min rests in between operations and less than 6 hours a day. 80-160 unfollows a day with 4-8 minutes rest between operations and less than 6 hours a day. So all my accounts are running for less than 12 hours a day and only 6 days a week shuffled.


IG automation for clients has been almost passive income for me for years. I moved on to paid social for clients, but I don't want to lose this service as it's an extra 1-3k depending on the month. I moved on to include paid social (FB and IG) after the updates in 2018 as I had a feeling that IG was going to go after automation and it was going to get more difficult. So I am not an expert in paid social yet.
 
Back
Top