Sudden drop in "Reach" after changing to AWS

Has anyone notice something similar. I recently went from using a automatization software that was running locally on my machine at home to running it on AWS server that's running on a sister city. All I do is like post nothing else with it.

While doing this I notice a huge drop on the IG "reach" numbers on a picture I posted today. I have 17k plus followers and usually IG gives me a reach of about 2.2k on the first day of the picture reaching 2.8k by day two. Today's post has been stuck 1.4k the lowest reach I have had by this time of day I can not even see it hitting 2k by end of day.

Anyone experiencing drop in reach today and could it be related to switching over to AWS?

Have been using AWS for 2 years and today one of my clients complaining theyre not getting enough followers anymore - my FL is showing more people following her than she actual has on ig.. wtf?

EDIT: Hopefully not shadow ban - feel like it could be.

unclefonzi said:

Have been using AWS for 2 years and today one of my clients complaining theyre not getting enough followers anymore - my FL is showing more people following her than she actual has on ig.. wtf?

EDIT: Hopefully not shadow ban - feel like it could be.

Click to expand...

That's interesting I had my best day ever yesterday with 150 follows while running it locally. Today follower growth seems slow yet can't make a judgment since I had the software off for most of today's.

Would be interesting to keep hearing your development with AWS

Yeah, seems FL is having problems today. I just posted about it at https://www.blackhatworld.com/seo/followliker-error-edition-mismatched.960331/

For you guys on AWS, I hope it's not Instagram now banning AWS IPs. Which are easy to get and block on Instagram's side.

colorme said:

Yeah, seems FL is having problems today. I just posted about it at https://www.blackhatworld.com/seo/followliker-error-edition-mismatched.960331/

For you guys on AWS, I hope it's not Instagram now banning AWS IPs. Which are easy to get and block on Instagram's side.

Click to expand...

Feel like it is a bug on FL rather than a ban - I see im following like 2k accounts on FL when im really following like 200 on ig..

Just to be safe from now on going to run on local machine and make it a dedicated bot, with proxies too ofc

febernovo said:

Has anyone notice something similar. I recently went from using a automatization software that was running locally on my machine at home to running it on AWS server that's running on a sister city. All I do is like post nothing else with it.

While doing this I notice a huge drop on the IG "reach" numbers on a picture I posted today. I have 17k plus followers and usually IG gives me a reach of about 2.2k on the first day of the picture reaching 2.8k by day two. Today's post has been stuck 1.4k the lowest reach I have had by this time of day I can not even see it hitting 2k by end of day.

Anyone experiencing drop in reach today and could it be related to switching over to AWS?

Click to expand...

Howdy,

Can you do some more experimenting switching back and forth between aws and your local machine? It's possible that instagram is subtly throttling you. Even try posting the exact same picture with the same tags to get scientific with it. I wouldn't know exactly, as I was educated in a one room schoolhouse.

On the topic of AWS IPs, I have to caution you about not using a proxy. Here's the thing- Amazon publishes all the IP addresses currently in use, so if I was in charge of instagram, you beat your sweet little *** that I'm going to make your experience as bad as possible if you're accessing my app--clearly for illicit purposes--from an AWS server. I can't post the link or else I'll get sent to the clink.

Partner, you need to be using a proxy on AWS. It is so easy to positively identify AWS traffic that a donkey who spent one day on Codecademy could implement the feature.


YEEEE HAW

You need good proxies to run bots on AWS.

Yeehaw22 said:

Howdy,

Can you do some more experimenting switching back and forth between aws and your local machine? It's possible that instagram is subtly throttling you. Even try posting the exact same picture with the same tags to get scientific with it. I wouldn't know exactly, as I was educated in a one room schoolhouse.

On the topic of AWS IPs, I have to caution you about not using a proxy. Here's the thing- Amazon publishes all the IP addresses currently in use, so if I was in charge of instagram, you beat your sweet little *** that I'm going to make your experience as bad as possible if you're accessing my app--clearly for illicit purposes--from an AWS server. I can't post the link or else I'll get sent to the clink.

Partner, you need to be using a proxy on AWS. It is so easy to positively identify AWS traffic that a donkey who spent one day on Codecademy could implement the feature.


YEEEE HAW

Click to expand...

Spot on. Anyone on AWS using bots, needs to use great proxies.

Thanks everyone for your responses. Seems like using AWS + Proxies is the general recommendations. I wish I could still run it locally my copy of Windows expired and that's why I decided to give AWS a try if the results continue to be this bad I'll have to switch back.

Things I have noticed and things I've been doing this past day:

- The picture never reached 2k in reach, for example a picture I shared two days before sits at a 3k reach currently and by the end of its first day it had maybe 2.7k in reach.
- So does feel IG is throttling this post.
- I've heard the term "confidence value" when some talk about IG and currently trying to use the AWS account to access Facebook normally and check IG normally in the hopes that it makes my activity seem more normal and maybe raises the confidence value a bit.
- I'm posting today too so will be monitoring if IG cuts my reach again.
- If I see another huge drop today I'll look into Proxies. Have not had any experience with them before