I just posted this on another thread, but I wanted to post it here too since this thread was talking about ISP issues.........and maybe others are seeing this due to the same IP blocking reasons...... ------- I have been troubleshooting this same update issue from our network for a couple of weeks now.... From what I could find......v1.36 used 208.111.160.6 to get updates.....and now v1.37 has tried to use 208.111.160.6 and 208.111.161.254 What I found out before today is that our cybersecurity department at HQ is blocking 208.111.160.6 because it was in the US-CERT recommended blocks for January 2009..... because it was detected as being an IP address hosting malicious code...... I'm not sure if they are blocking 208.111.161.254 as well....but MBAM won't update when it tries to go THAT ip address either....... Here is what I got back from cybersecurity........ US-CERT reported that 208.111.160.6 on their CAT3 Watchlist, meaning the site has been identified as hosting malicious code. US-CERT additionally provided the following hostnames in which the malicious code was detected. They are cdn-208-111-160-6[dot]iad[dot]llnw[dot]net and cds723[dot]iad[dot]llnw[dot]net. Not really sure where to go from here...... unless 208.111.160.6 can get its reputation cleared with US-CERT