It isn't alerting on avast, this is their so called malicious site blocking at work and it doesn't like that IP address.
The avastSvc.exe is the main controller for avast, this includes the web shield localhost proxy. When you are using your browser all http traffic/connections are redirected through the web shield proxy so that the content can be scanned. So something is trying to connect to that IP.
The problem is MBAM isn't reporting what is initiating the connection but the avast process controlling the redirection through the proxy.
Personally I feel this mbam feature is more hassle than it is worth, it isn't just malicious sites that are pinged, but also other categories; not to mention that you have both the web shield and network shield looking after this type of thing. I have disabled this on both of my mbam Pro installations, that decision is however up to you.
I don't know why you have obfuscated that last part of the IP as we can't check it out.