Bookmine.co Not Loading – Routing Issue Returned

also the website owner whitelisted my ip, so this proves the issue is on your guys side.

... traceroute results show the connection stalls at an Xfinity hop before reaching the destination. ...

That doesn't prove anything really. Routers along a route are often programmed to ignore trace packets.

I can browse the site, yet my trace has a huge "hole" between hops 7 and 14, like so:

C>tracert -4 bookmine.co

Tracing route to bookmine.co [69.57.162.10] over a maximum of 30 hops:

  1     4 ms     3 ms     3 ms  router1 [192.168.1.1]
  2    12 ms     9 ms     8 ms  96.120.9.181
  3     8 ms     8 ms     9 ms  po-301-1203-rur01.york.pa.pitt.comcast.net [24.124.216.181]
  4    10 ms    10 ms    10 ms  be-87-rar01.lowerpaxton.pa.pitt.comcast.net [96.110.25.9]
  5    18 ms    18 ms    18 ms  be-33-ar01.pittsburgh.pa.pitt.comcast.net [69.139.168.185]
  6    26 ms    26 ms    26 ms  be-31631-cs03.newark.nj.ibone.comcast.net [96.110.42.25]
  7    26 ms    25 ms    26 ms  be-2312-pe12.newark.nj.ibone.comcast.net [96.110.34.10]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14    81 ms    80 ms    81 ms  premium264-2.web-hosting.com [69.57.162.10]

Trace complete.

Although something along the route is dropping trace packets, the routers are still doing their job: forwarding data packets.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

Hello,

I’m unable to access the website bookmine.co on my Xfinity connection. This is the same problem I had before — last time it turned out to be an Xfinity routing issue, which was fixed after escalation. The site worked normally again for a while, but now the issue has returned.

The site itself is up (I can access it via mobile data and others on different ISPs can load it). I also submitted the URL through the “Report a Website Not Working” tool, but the issue persists.

Here are my traceroute results, which show the problem is occurring on Xfinity’s network:

Tracing route to bookmine.co

  1     2 ms     1 ms     1 ms  10.0.0.1
  2    10 ms    12 ms    12 ms  100.92.100.227
  3    23 ms    12 ms    37 ms  po-56-rur302.salem.or.bverton.comcast.net [96.217.96.201]
  4    14 ms    11 ms    12 ms  po-300-xar02.salem.or.bverton.comcast.net [96.216.159.121]
  5    15 ms    14 ms    12 ms  ae-75-ar01.troutdale.or.bverton.comcast.net [96.216.60.221]
  6     *       40 ms    20 ms  be-36211-cs01.seattle.wa.ibone.comcast.net [68.86.93.49]
  7    19 ms    36 ms    18 ms  be-2101-pe01.seattle.wa.ibone.comcast.net [96.110.39.202]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 ...
 30     *        *        *     Request timed out.

As you can see, traffic is routing correctly up to Xfinity’s backbone in Seattle, but after that it fails and never reaches the destination.

This is the exact same symptom as last time, and once it was escalated internally it was corrected. I’d like to request this be escalated again to the proper team so the routing to bookmine.co can be fixed.