Boereport.com is resolving to 172.64.80.1 - we can't access to this web site

Hi there, we have multiple offices. In Toronto, this domain is resolved to 104.21.23.109 and In Montreal, it is resolved to 172.67.211.72, boereport.com works on web browsers. However, in Calgary, it is resolved to 172.64.80.1, it keeps showing “the site is unreachable” on web browser. On firewall logs, this IP is allowed for sure. Any idea why doesn’t work with this IP? Please advise. thx.

Could you please elaborate on the error message you are seeing?

Hmmm…can’t reach this page
It looks like the webpage at https://boereport.com/ might be having issues or it may have moved permanently to a new web address.

This is found on web browser. Please advise. thx.

From my end I can retrieve the content via connecting to that IP without issues:

% curl -svo /dev/null https://boereport.com --connect-to ::172.64.80.1
* Connecting to hostname: 172.64.80.1
*   Trying 172.64.80.1:443...
* Connected to 172.64.80.1 (172.64.80.1) port 443
...
< HTTP/2 200 
< date: Mon, 15 Apr 2024 12:36:48 GMT
< content-type: text/html; charset=UTF-8
< vary: Accept-Encoding
< vary: Accept-Encoding
< vary: Accept-Encoding
< vary: Accept-Encoding,Cookie
< x-powered-by: WP Engine
< link: <https://boereport.com/wp-json/>; rel="https://api.w.org/"
< x-cacheable: SHORT
< cache-control: max-age=600, must-revalidate
< x-cache: HIT: 24
< x-cache-group: normal
< cf-cache-status: DYNAMIC
< report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=WSfWJFRAzXXdsSA0WyxT0H4rsbGHyz4FDe7bsgvpZvH9rYy3PY%2FHq6%2FsoRqFXi1pXUxWc3hW1neTXRktS0o%2BMkR4kljHpfLxh%2FPyobGMegCQNN7rAs8R0uxhDKUO3Dff"}],"group":"cf-nel","max_age":604800}
< nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
< server: cloudflare
< cf-ray: 874bfbb81f1694e5-LHR
< alt-svc: h3=":443"; ma=86400
< cf-team: 1f835ba704000094e550c28400000001
< 
{ [8192 bytes data]
* Connection #0 to host 172.64.80.1 left intact

If you’re seeing a timeout when running the same command from the affected location, it would be a good idea to run a TCP MTR towards this IP to see whether the packets are dropped and on which hop this is happening: Gathering information for troubleshooting sites · Cloudflare Support docs.

Here is an example:

mtr -P 443 -T 172.64.80.1 -r -n
1 Like

Just found the root cause…It works on Google Chrome and Firefox, but no good on Edge. I will ping our Application team. Thank you for your quick response! Much appreciated!!!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.