Comcast Routing issues - tracert fails repeatedly

103oakwoodcircle.com and other sites not reachable through Comcast network, bypassing Comcast w/VPN or mobile internet makes it accessible ...

I can browse the site using my Comcast Internet connection and that, taken with your VPN and mobile network results, it suggests that it is your webhost that is blocking traffic from your Comcast IP.

Your target is hosted on Amazon's AWS network. Hop #13 is an Amazon IP, and I would guess that all the hops after #10 are on Amazon's network as well. Internet hosts and routers are often configured to give low priority to trace packets and higher priority to data packets, so trace results don't always reflect what is happening with data packets. Please see https://www.dslreports.com/faq/14068. You should follow up with your webhost's admins to find out what's happening here. Expect them to say "We're not blocking you!", as these are typically triggered by security software that many staff members don't know about.

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.

I'm seeing a very similar issue for several sites, just starting today. They all stop tracing at the same hop. Works fine through a VPN.

$ traceroute sutterhealth.org
traceroute to sutterhealth.org (198.217.73.225), 30 hops max, 60 byte packets
 1  _gateway.lxd (100.115.92.193)  0.371 ms  0.042 ms  0.042 ms
 2  100.115.92.25 (100.115.92.25)  0.680 ms  0.388 ms  0.993 ms
 3  192.168.86.1 (192.168.86.1)  6.475 ms  6.188 ms  6.081 ms
 4  96.120.88.197 (96.120.88.197)  32.671 ms  32.566 ms  32.330 ms
 5  et-1-1-rur201.scotts.ca.sfba.comcast.net (96.110.103.161)  32.238 ms  32.115 ms  31.525 ms
 6  po-100-xar02.rohnertpr.ca.sfba.comcast.net (162.151.86.17)  31.327 ms  18.701 ms  26.586 ms
 7  68.87.194.113 (68.87.194.113)  24.675 ms  23.732 ms  27.043 ms
 8  be-397-ar01.hayward.ca.sfba.comcast.net (96.108.99.9)  26.926 ms  18.334 ms  22.985 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Traceroute is a tool, but it relies on ICMP protocol.  That's blocked on a lot of VPS/Cloud instances at the cloud providers gateway.  You'll get to the cloud provider across the routers in the middle, but you likely timeout  after that before you get to the VPS/Cloud instance.  It's part of DoS protection.

Ping, might tell you if the VPS/Cloud instance is active, but they'd have to allow that in their own firewall config in the machine instance.  Hit and miss there.

Nmap {nmap.org) is a better tool to tell you if a specific port on a specific server is alive and accepting traffic or not.  Only scan one port at a time, otherwise, we're all blocking portscans to multiple ports and will cut off your IP address -- perhaps for quite some time if you portscan anything that employs an adaptive firewall.  (DoS protection again).