The problem is not with avastSvc.exe as that in this instance is the web shield proxy redirecting a request connect to this IP, either from your browser or another program on your system.
You can exclude avast in MBAM until you are blue in the face as it will make no difference at all as MBAM is blocking the IP and not avastSvc.exe.
####
I have seen this so many times I have even saved my usual response - MBAM malicious IP Detection reporting avastSvc.exe as process:
No avast isn't infected. MBAM isn't blocking avast as such, as the avastSvc.exe is the main avast service and it controls the various shields. The Web Shield routes all http traffic through its localhost proxy, so all MBAM sees is avastSvc.exe as the originating process, which is incorrect.
This is either you trying to connect to this IP via your browser or possibly a link in a site you're viewing redirecting of getting content from that IP address.
What site were you on when this alert occurred ?
@@@@
I find this feature in MBAM more a hindrance than a help - This is what I hate about the MBAM malicious site blocking, it doesn't do what it says on the tin as there are many more categories that it also alerts on and this under the guise of the malicious sites, so there is no way that the user knows what is 'malicious' about the IP alert. So for my money (excuse the pun) they either need to change the wording and or make it clear 'why' an IP was blocked.