We were experiencing a routing anomaly to 18.104.22.168 on multiple nodes. Something existed within their infrastructure that was replying to ICMP pings to 22.214.171.124 but was obviously not the real 126.96.36.199 endpoint.
We were persistent, had to engaged their peering partner who further provided diagnostic evidence the problem was indeed on iWeb’s network.
They were eventually presented with so much contradicting evidence to their claims that this was a Cloudflare problem that it was finally escalated to their network engineering team this morning who promptly corrected the issue.
Never give up!