I have what I believe to be the cause of this issue. We have a domain (loadbalancing.com) that we do load balancing and health checks on. One of the origins for load balancing is on a shared host ( and also shares the IP with anotherdomain.com. For some reason, the load balancing is sending health checks and traffic checks to anotherdomain.com instead of loadbalancing.com. I replied to the ticket and hope it can be fixed. The reasoning for my theory is when the user agent for health checks and load balancing was blocked on anotherdomain.com, the health checks for loadbalancing.com started responding as critical (403 error) for that same origin IP.
1 Like