AT&T Residential and Mining

[Mac128]

Hi,
Thank you for allowing me to join.

I'm not yet started with mining.  AT&T account is unlimited residential data. 
I understand that AT&T blocks port 8333. 

Will a red flag situation occur with my AT&T service if I start mining?
Or will AT&T notice and throttle me, or tell me to stop? 

Many thanks!

[NotFuzzyWarm]

AT&T and other ISP's in the US could care less about home or commercial mining and will do nothing. At least for Bitcoin, even a top-end miner uses very very little bandwidth. Something around 15MB per-day per miner.

[RickDeckard]

AT&T and other ISP's in the US could care less about home or commercial mining and will do nothing. At least for Bitcoin, even a top-end miner uses very very little bandwidth. Something around 15MB per-day per miner.

I would add that latency ends up being more important than bandwidth for the reason that the less latency (a.k.a ping) you have, the more reliable and more frequent will be the exchange of information/packets between you and the pool you're mining to (assuming you want to join a pool).
With a reliable ping you'll avoid having rejected shares[1]:

Rejected shares is a term for all shares that are rejected for any of the below reasons:

• Stale share - The share was submitted too late (probably because of the high latency or problems with connection). This is the only share that is expected to happen in small quantities thus it is considered normal.
• Share above target (invalid share) - There is a problem with your mining software that needs to be inspected or configured properly. It is also possible that the mining software is not compatible with NiceHash.
• Duplicate share - The share was submitted more than once and indicates a bug in your mining software or incompatibility with NiceHash.
• Other - Any other type of rejected shares usually means a bug in your mining software.

The most common rejected shares are 'share above target' and 'stale' shares.

[1]https://www.nicehash.com/blog/post/what-are-accepted-and-rejected-shares

[BitMaxz]

I don't think AT&T can detect if you are mining and I don't see any red flag if you mine while using this ISP but just in case you want to encrypt all of your mining activity then consider changing your DNS to a different DNS like Cloudflare to make sure you are submitting an encrypted data because if you didn't use other DNS your ISP can do deep packet inspection where they can know what site you are accessing to so changing DNS to cloudflare or google DNS will encrypt your data submitted to ISPs.

[RickDeckard]

I don't think AT&T can detect if you are mining and I don't see any red flag if you mine while using this ISP but just in case you want to encrypt all of your mining activity then consider changing your DNS to a different DNS like Cloudflare to make sure you are submitting an encrypted data because if you didn't use other DNS your ISP can do deep packet inspection where they can know what site you are accessing to so changing DNS to cloudflare or google DNS will encrypt your data submitted to ISPs.

As an alternative to Cloudfare for a DNS resolver, would it work to implement a recursive DNS like Unbound[1]? This would increase greatly the privacy as the way that recursive DNS work is that they break down requests and go ask around DNS resolvers what address is associated with a certain IP in multiple stages. This would have a drawback of being slow the first few times but with time it would fetch data directly from the local cache. This is usually applicable in Pi-holes even, I just don't know if it would work correctly with traffic associated with miners.
[1]https://github.com/NLnetLabs/unbound