Visitor

 • 

13 Messages

Sunday, April 24th, 2022

Closed

Cannot reach certain websites

About a week or so ago, I noticed I could not reach certain websites when connected to my comcast network, but I COULD reach them via a VPN through that same network, and also through my Verizon cellphone or hotspot. 

The details:

- I own the hardware: Gryphon router and a Netgear CM500 cable modem

- Confirmed that multiple devices in the house cannot reach the websites when on the Comcast cable network

- Those same devices CAN reach the same websites via a VPN or on a cell network/cell hotspot

- I am not a network engineer

- tried Comcast customer service, who shunted me over to Netgear, who wanted to charge me $130 for tech service. I don't believe either tech understood what I was saying.

I am a little handy, so while on the comcast network I did a traceroute on the sites that don't work. Here is one of them:

traceroute to xwavesoft.com (69.195.98.233), 64 hops max, 72 byte packets

1  www.gryphoncare.com (192.168.1.1)  2.990 ms  2.014 ms  1.561 ms

2  100.93.141.67 (100.93.141.67)  11.964 ms  10.218 ms  12.512 ms

3  po-309-346-rur302.roseville.mn.minn.comcast.net (24.124.173.89)  12.457 ms  11.630 ms  13.060 ms

4  po-2-rur301.roseville.mn.minn.comcast.net (68.87.174.157)  11.706 ms  12.930 ms  12.929 ms

5  68.87.174.105 (68.87.174.105)  11.929 ms  13.320 ms  14.133 ms

6  68.87.174.241 (68.87.174.241)  13.713 ms  20.313 ms  14.293 ms

7  69.139.176.209 (69.139.176.209)  17.979 ms  15.529 ms  12.406 ms

8  be-39821-cs02.1601milehigh.co.ibone.comcast.net (96.110.40.101)  33.735 ms  32.253 ms  31.362 ms

9  be-1213-cr13.1601milehigh.co.ibone.comcast.net (96.110.39.102)  34.996 ms  32.258 ms  32.874 ms

10  be-304-cr13.champa.co.ibone.comcast.net (96.110.36.205)  30.939 ms  32.295 ms  31.143 ms

11  be-1313-cs03.champa.co.ibone.comcast.net (96.110.37.233)  32.339 ms  37.985 ms  34.207 ms

12  be-36731-ar01.saltlakecity.ut.utah.comcast.net (96.110.43.234)  53.793 ms  46.793 ms  42.613 ms

13  96.216.180.114 (96.216.180.114)  42.423 ms  43.452 ms  41.458 ms

14  * * *

15  * * *

16  * * *

[goes to #64 before ending without connecting]

According to whois.arin.net, 96.216.180.114 belongs to Comcast Cable Communications, LLC (CCCS).

Here is a traceroute on a second website:

traceroute to [omitted, as the domain name is my own and I don't wish to share it] 64 hops max, 72 byte packets

1  www.gryphoncare.com (192.168.1.1)  4.081 ms  1.547 ms  1.360 ms

2  100.93.141.66 (100.93.141.66)  10.421 ms  10.736 ms  11.490 ms

3  po-309-345-rur301.roseville.mn.minn.comcast.net (24.124.173.81)  11.463 ms  11.269 ms  11.224 ms

4  po-2-rur302.roseville.mn.minn.comcast.net (68.87.174.158)  10.430 ms  10.653 ms  11.527 ms

5  68.87.174.109 (68.87.174.109)  12.358 ms  12.662 ms  11.394 ms

6  68.87.174.209 (68.87.174.209)  13.399 ms  11.640 ms  11.448 ms

7  96.108.188.169 (96.108.188.169)  14.793 ms  11.642 ms  13.857 ms

8  be-37011-cs01.350ecermak.il.ibone.comcast.net (96.110.43.1)  20.703 ms  22.214 ms  27.153 ms

9  be-2111-pe11.350ecermak.il.ibone.comcast.net (96.110.33.194)  22.005 ms  21.558 ms  20.934 ms

10  62.115.54.21 (62.115.54.21)  21.022 ms  24.841 ms  21.926 ms

11  * * *

12  kanc-bb2-link.ip.twelve99.net (62.115.138.74)  35.815 ms  35.099 ms  36.265 ms

13  * * *

14  dls-b23-link.ip.twelve99.net (62.115.138.65)  47.488 ms  44.344 ms  46.472 ms

15  dls-b1-link.ip.twelve99.net (62.115.113.85)  43.555 ms  48.574 ms  43.528 ms

16  cyrusone-svc067803-lag002972.ip.twelve99-cust.net (62.115.184.155)  51.849 ms  51.184 ms  51.399 ms

17  be-1003-r0.dfw4.cyrusone.net (209.172.218.38)  49.646 ms  51.059 ms  49.434 ms

18  be-4030-r1.hou1.cyrusone.net (209.172.217.242)  51.638 ms  50.486 ms  51.199 ms

19  * * *

20  * * *

21  * * *

[goes to #64 before ending without connecting]

On line 10, whois.ripe.net tells me 62.115.54.21 is located in Sweden(?). I am in the midwest of USA, connecting to (in this case) a server out in (I think) Utah…the hosting company is Bluehost.com. Why would the request be routed that way?

It seems like a DNS problem in the Comcast network, but again, I'm not a network engineer. I don't see how this could be caused by either my router or modem.

Thoughts?

Oldest First
Selected Oldest First
No Responses!
forum icon

New to the Community?

Start Here