This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bandwith Issues Chrome/Firefox/Edge

We have been using Sophos intercept x advanced with MTR for about 6 weeks. Since then, our bandwidth has dropped 90%. We use a gigabit internet connection and have previously achieved the following values ​​in a speed test in the browser: Down: 900MB/s Up: 800MB/s

Now, if we're lucky, we'll get Down: 60MB/s Up: 300MB/s.

We found out that it is due to the following settings:
 If these settings are deactivated, we have full bandwidth when surfing again. But we don't want to leave them disabled. This is not a condition, the support from Sophos is not getting anywhere either. We expected more...


here are the screenshots from the speedtest:

deactivated settings:


activated settings:




This thread was automatically locked due to age.
Parents
  • I've just discovered the same issue on my site too. Has anyone had a definitive answer back from Sophos as to when they plan to roll out a fix for this? I am amazed something as impactful and obvious as this made it past their devs in the testing stages?! The fact that they missed this and rolled it out to customers and then drag their heels to fix doesn't fill me with confidence. I certainly wont be going with Sophos when I renew my AV and refresh my Firewalls....

  • Sophos sent me a test fix coupled with a registry change which seemed to resolve the issue, (previously this didnt work as i rebooted after applying the change) They however advised that the registry key (which works alongside the updated executables they provided) deletes itself on reboot. So although it fixes the issue, it isnt a long term fix.

    I have been informed that the engineering team are putting this fix together in the latest core agent update (and should deploy automatically when available)

Reply
  • Sophos sent me a test fix coupled with a registry change which seemed to resolve the issue, (previously this didnt work as i rebooted after applying the change) They however advised that the registry key (which works alongside the updated executables they provided) deletes itself on reboot. So although it fixes the issue, it isnt a long term fix.

    I have been informed that the engineering team are putting this fix together in the latest core agent update (and should deploy automatically when available)

Children