• TalkBass has been independent since 1998. Add your voice.
    Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
    Join freeLog in
    Want zero display ads or expanded classifieds tools? Compare plans.

Routing issue to talkbass.com from Comcast Business IP block?

Hey mods, the last couple of days I've been having intermittent connectivity issues JUST to talkbass.com. I'm on a Comcast Business netblock, but the site loads great for me if I fire up a VPN and try to connect from different locales both local (US/Seattle-based) and international (Sweden, France, etc). Are you aware of any routing issues to/from Comcast at this time? Happy to share my netblock via DM if appropriate.

Many thanks in advance!
 
  • Like
Reactions: GitmoMango
Is anyone else experiencing issues trying to connect to TB? Since yesterday, I've not been able to connect most times I've tried.

I've never had this connection problem with TB before, and TB is the only site that I'm experiencing this problem with, as well.
 
No issues here. A couple of things to try to fix it:
1. Delete the cookies and browsing history from your browser
2. Run command prompt as an administrator and type "ipconfig /flushdns" and hit ENTER
3. See if a different browser gives the same results
 
Hey mods, the last couple of days I've been having intermittent connectivity issues JUST to talkbass.com. I'm on a Comcast Business netblock, but the site loads great for me if I fire up a VPN and try to connect from different locales both local (US/Seattle-based) and international (Sweden, France, etc). Are you aware of any routing issues to/from Comcast at this time? Happy to share my netblock via DM if appropriate.

Many thanks in advance!

Confirmed issue with Comcast users not being able to access TB or slow loading. Will get on the phone with our network host and report back.
 
here you go:

traceroute to 108.171.216.2 (108.171.216.2), 30 hops max, 28 byte packets
1 hosted-by.2is.nl (62.221.192.2) 0.363 ms 0.341 ms 0.324 ms
2 xe-0-3-1-3245-cr01.ams04.astralus.net (185.187.12.170) 0.669 ms xe-0-3-0-3244-cr01.ams04.astralus.net (185.187.12.168) 0.670 ms xe-0-3-1-3245-cr01.ams04.astralus.net (185.187.12.170) 0.666 ms
3 adm-b5-link.telia.net (195.12.255.233) 0.760 ms hurricane-electric.telecity2.nl-ix.net (193.239.116.14) 1.441 ms adm-b5-link.telia.net (195.12.255.233) 0.760 ms
4 adm-bb3-link.telia.net (62.115.136.194) 147.583 ms 100ge2-1.core1.ams1.he.net (184.104.192.129) 1.419 ms adm-bb4-link.telia.net (62.115.137.64) 146.788 ms
5 100ge16-1.core1.lon2.he.net (72.52.92.213) 8.221 ms prs-bb3-link.telia.net (213.155.136.21) 148.698 ms 100ge16-1.core1.lon2.he.net (72.52.92.213) 8.218 ms
6 100ge13-2.core1.nyc4.he.net (72.52.92.166) 75.092 ms 75.040 ms 86.443 ms
7 las-b24-link.telia.net (62.115.121.220) 151.328 ms las-b24-link.telia.net (62.115.114.86) 145.884 ms 100ge2-1.core2.chi1.he.net (184.104.193.173) 93.257 ms
8 webnx-ic-319980-las-b3.c.telia.net (213.248.77.75) 146.452 ms 100ge14-2.core1.mci3.he.net (72.52.92.54) 104.612 ms 100ge2-2.core1.mci3.he.net (184.105.81.209) 105.410 ms
9 100ge12-1.core1.den1.he.net (184.105.64.49) 115.888 ms 116.105 ms 100-42-215-249.static.webnx.com (100.42.215.249) 150.123 ms
10 * * 100ge11-2.core1.slc1.he.net (72.52.92.42) 126.045 ms
11 * * webnx-inc.10gigabitethernet1-1-9.switch1.slc1.he.net (64.62.243.74) 128.446 ms
12 104-237-48-158.static.webnx.com (104.237.48.158) 154.615 ms * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
 
here you go:

traceroute to 108.171.216.2 (108.171.216.2), 30 hops max, 28 byte packets
1 hosted-by.2is.nl (62.221.192.2) 0.363 ms 0.341 ms 0.324 ms
2 xe-0-3-1-3245-cr01.ams04.astralus.net (185.187.12.170) 0.669 ms xe-0-3-0-3244-cr01.ams04.astralus.net (185.187.12.168) 0.670 ms xe-0-3-1-3245-cr01.ams04.astralus.net (185.187.12.170) 0.666 ms
3 adm-b5-link.telia.net (195.12.255.233) 0.760 ms hurricane-electric.telecity2.nl-ix.net (193.239.116.14) 1.441 ms adm-b5-link.telia.net (195.12.255.233) 0.760 ms
4 adm-bb3-link.telia.net (62.115.136.194) 147.583 ms 100ge2-1.core1.ams1.he.net (184.104.192.129) 1.419 ms adm-bb4-link.telia.net (62.115.137.64) 146.788 ms
5 100ge16-1.core1.lon2.he.net (72.52.92.213) 8.221 ms prs-bb3-link.telia.net (213.155.136.21) 148.698 ms 100ge16-1.core1.lon2.he.net (72.52.92.213) 8.218 ms
6 100ge13-2.core1.nyc4.he.net (72.52.92.166) 75.092 ms 75.040 ms 86.443 ms
7 las-b24-link.telia.net (62.115.121.220) 151.328 ms las-b24-link.telia.net (62.115.114.86) 145.884 ms 100ge2-1.core2.chi1.he.net (184.104.193.173) 93.257 ms
8 webnx-ic-319980-las-b3.c.telia.net (213.248.77.75) 146.452 ms 100ge14-2.core1.mci3.he.net (72.52.92.54) 104.612 ms 100ge2-2.core1.mci3.he.net (184.105.81.209) 105.410 ms
9 100ge12-1.core1.den1.he.net (184.105.64.49) 115.888 ms 116.105 ms 100-42-215-249.static.webnx.com (100.42.215.249) 150.123 ms
10 * * 100ge11-2.core1.slc1.he.net (72.52.92.42) 126.045 ms
11 * * webnx-inc.10gigabitethernet1-1-9.switch1.slc1.he.net (64.62.243.74) 128.446 ms
12 104-237-48-158.static.webnx.com (104.237.48.158) 154.615 ms * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

I'm not a network guy, but if you're in Eastern PA, why are your first trace route hops from the Netherlands? Hmm... Did you do this from your own desktop system? Thanks for your help here, let me know if you need help with the trace route (what OS are you running?)