Hello Mark.
We will certainly look into it and help you.
We've sent you an email that offered free additional support to investigate and resolve this issue further.
Please check for the email and revert to us.
Thanks for your understanding in advance.
Hi,
I have used AVG for years. I am wondering if anyone else is having this issue after a recent update. It seems AVG now has at least 124 simultaneous active established outgoing secure connections to 2 IP addresses: 84.17.43.104 & 212.102.33.38 using port 443. Here is a sampling of them.
...:52887 52887 84.17.43.104:443 TCP EST OUT 5147
...:57945 57945 212.102.33.38:443 TCP EST OUT 6616
...:57742 57742 212.102.33.38:443 TCP EST OUT 6256
...:57804 57804 84.17.43.104:443 TCP EST OUT 6347
...:58169 58169 84.17.43.104:443 TCP EST OUT 6985
...:53246 53246 84.17.43.104:443 TCP EST OUT 4218
...:58699 58699 212.102.33.38:443 TCP EST OUT 7671
...:52920 52920 84.17.43.104:443 TCP EST OUT 5207
...:58020 58020 212.102.33.38:443 TCP EST OUT 6797
...:57176 57176 212.102.33.38:443 TCP EST OUT 5536
...:58799 58799 84.17.43.104:443 TCP TW OUT 58
...:58019 58019 84.17.43.104:443 TCP EST OUT 6797
...:54762 54762 84.17.43.104:443 TCP CW OUT 40
...:58784 58784 152.195.19.97:443 TCP EST OUT 7791
...:58749 58749 84.17.43.104:443 TCP EST OUT 7749
...:58439 58439 212.102.33.38:443 TCP EST OUT 7337
...:58748 58748 212.102.33.38:443 TCP EST OUT 7788
...:53211 53211 212.102.33.38:443 TCP CW OUT 235
...:52613 52613 84.17.43.104:443 TCP EST OUT 4819
...:60156 60156 212.102.33.38:443 TCP EST OUT 4317
...:53165 53165 84.17.43.104:443 TCP CW OUT 138
...:52614 52614 212.102.33.38:443 TCP EST OUT 4867
...:52452 52452 212.102.33.38:443 TCP EST OUT 4562
...:56900 56900 212.102.33.38:443 TCP EST OUT 5289
...:57645 57645 212.102.33.38:443 TCP EST OUT 6076
...:58423 58423 212.102.33.38:443 TCP EST OUT 7307
...:57133 57133 84.17.43.104:443 TCP EST OUT 5460
...:52519 52519 212.102.33.38:443 TCP EST OUT 4684
...:58477 58477 84.17.43.104:443 TCP EST OUT 7427
...:57244 57244 84.17.43.104:443 TCP EST OUT 5596
...:52788 52788 212.102.33.38:443 TCP EST OUT 5109
...:52697 52697 212.102.33.38:443 TCP EST OUT 5052
...:58522 58522 212.102.33.38:443 TCP EST OUT 7487
...:57868 57868 84.17.43.104:443 TCP EST OUT 6483
...:57646 57646 84.17.43.104:443 TCP EST OUT 6039
...:57243 57243 212.102.33.38:443 TCP EST OUT 5596
...:56901 56901 84.17.43.104:443 TCP EST OUT 5238
...:58094 58094 212.102.33.38:443 TCP EST OUT 6905
...:52355 52355 84.17.43.104:443 TCP EST OUT 4332
...:58628 58628 84.17.43.104:443 TCP EST OUT 7607
...:57273 57273 84.17.43.104:443 TCP EST OUT 5603
...:52640 52640 84.17.43.104:443 TCP EST OUT 4906
...:52539 52539 84.17.43.104:443 TCP EST OUT 4699
...:57608 57608 84.17.43.104:443 TCP EST OUT 5986
...:52483 52483 212.102.33.38:443 TCP EST OUT 4623
...:52540 52540 212.102.33.38:443 TCP EST OUT 4745
...:52585 52585 212.102.33.38:443 TCP EST OUT 4806
Is there some reason AVG now needs over 124 Active sessions?
Is this a bug? Am I the only one experiencing this? Why is my bandwidth being bogged down with so many connections? Is it send data to them? What exactly is it sending?
A quick internet search finds a London based data "processing"/mining company my computer is reaching out to constantly with 124 secure lines open at once? Is this how the 2017 Avast merger has infected this company? If so I will be looking elsewhere for my internet needs. For now I have blocked them. Updates seem to still work so what is the point of the 124 connections to a Data Mining company and do I still want to use AVG going forward…?
I am running Win7 64 bit with AVG Internet Security:
Software version 22.3.3228 (build 22.3.7108.719)
Virus Def version 220427-4
UI version 1.0.655
Thank you
Mark
Hello Mark.
We will certainly look into it and help you.
We've sent you an email that offered free additional support to investigate and resolve this issue further.
Please check for the email and revert to us.
Thanks for your understanding in advance.