If it was blocked on Let's Encrypt's side, that's not the symptoms that you'd see.
It looks like your network (or your ISP's network) might not be routing to 172.65. correctly. We've seen a few times around here networks that somehow thought that IP should be treated like private 172.16.0.0/12 space even though it isn't. (ARIN specifically notes that people sometimes have this problem.)