dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
538
share rss forum feed

ame101

join:2002-05-02
Southington, CT

[CT] Lots of sites not loading or just partly...

....seem to have started early yesterday(storm issue?), not my computer/router. Sites that will not load will work fine on Sprint mobile connection. Some vague info on COX site, but more of less no info. Also lost 98% of all HD channels yesterday for a time. Anyone having same issues?



X8oD

@cox.net

Same issue here, in Wallingford. Cannot reach a few regular sites i browse. Changed DNS, still not working.



snowissue

@cox.net
reply to ame101

Same issue some sites load others do not. It is a Cox issue because it works when I use ATT and connect my computer to my phone


ame101

join:2002-05-02
Southington, CT

Spent 35-40 minutes on phone with level 1 and 2 support. Can or can not see issues, say they will look into it more and call me back.


ame101

join:2002-05-02
Southington, CT

used/removed router,computers, changed DNS(COX/google), even ran new drop from Tap. Level 2 was great. Hoping for fast fix.



nil
Java Geek
join:2000-11-27
kudos:2
reply to ame101

I'm having the same issue, started yesterday.



nil
Java Geek
join:2000-11-27
kudos:2

1 edit
reply to ame101

Here's a failing traceroute:

traceroute to e4838.b.akamaiedge.net (23.33.119.153), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  1.144 ms  0.864 ms  0.782 ms
 2  * * *
 3  ip98-190-163-102.ri.ri.cox.net (98.190.163.102)  9.625 ms  10.564 ms  9.889 ms
 4  ip98-190-163-128.ri.ri.cox.net (98.190.163.128)  10.862 ms  13.311 ms  12.493 ms
 5  ip98-190-33-44.ri.ri.cox.net (98.190.33.44)  12.344 ms  11.703 ms  9.793 ms
 6  ip98-190-33-34.ri.ri.cox.net (98.190.33.34)  13.561 ms  15.412 ms  12.463 ms
 7  provdsrj02-ae3.0.rd.ri.cox.net (98.190.33.26)  14.171 ms  14.998 ms  15.269 ms
 8  68.1.5.157 (68.1.5.157)  25.620 ms  24.193 ms  18.361 ms
 9  16-7.r1.ny.hwng.net (69.16.190.81)  19.541 ms
    209.197.17.205 (209.197.17.205)  20.424 ms  20.703 ms
10  209.197.17.202 (209.197.17.202)  19.618 ms
    unknown.hwng.net (209.197.0.186)  18.502 ms  20.859 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  *
 

A different site times out at this router:
 3  ip98-190-162-102.ri.ri.cox.net (98.190.162.102)  15.798 ms  8.992 ms  9.720 ms
 4  ip68-9-7-118.ri.ri.cox.net (68.9.7.118)  11.728 ms  10.429 ms  10.716 ms
 5  ip98-190-33-42.ri.ri.cox.net (98.190.33.42)  14.390 ms  10.306 ms  17.634 ms
 6  ip98-190-33-24.ri.ri.cox.net (98.190.33.24)  20.515 ms  12.429 ms  11.909 ms
 7  provdsrj01-ae3.0.rd.ri.cox.net (98.190.33.20)  12.374 ms  14.999 ms  12.022 ms
 8  68.1.4.133 (68.1.4.133)  23.048 ms  23.544 ms  23.738 ms
 9  72.21.221.9 (72.21.221.9)  67.908 ms  26.455 ms  29.114 ms
10  72.21.220.55 (72.21.220.55)  26.155 ms  27.039 ms  23.664 ms
11  205.251.245.55 (205.251.245.55)  24.375 ms  26.270 ms  28.127 ms
 

twimg.com times out, check out the pings before it does:
traceroute to twimg.com (210.163.219.24), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  3.322 ms  0.759 ms  0.737 ms
 2  * * *
 3  ip98-190-163-102.ri.ri.cox.net (98.190.163.102)  12.863 ms  12.172 ms  10.171 ms
 4  ip98-190-163-128.ri.ri.cox.net (98.190.163.128)  12.366 ms  11.975 ms  9.599 ms
 5  ip98-190-33-44.ri.ri.cox.net (98.190.33.44)  13.120 ms  10.418 ms  10.209 ms
 6  ip98-190-33-34.ri.ri.cox.net (98.190.33.34)  13.488 ms  13.372 ms  14.007 ms
 7  provdsrj02-ae3.0.rd.ri.cox.net (98.190.33.26)  71.449 ms  13.032 ms  13.773 ms
 8  68.1.5.161 (68.1.5.161)  19.083 ms  19.185 ms  20.185 ms
 9  ae-15.r06.nycmny01.us.bb.gin.ntt.net (129.250.194.153)  19.892 ms  20.033 ms  19.341 ms
10  ae-2.r22.nycmny01.us.bb.gin.ntt.net (129.250.4.174)  19.892 ms  31.394 ms  17.600 ms
11  ae-4.r21.sttlwa01.us.bb.gin.ntt.net (129.250.2.51)  96.632 ms  89.183 ms  92.139 ms
12  ae-0.r20.sttlwa01.us.bb.gin.ntt.net (129.250.2.53)  89.182 ms  88.283 ms  98.831 ms
13  as-3.r20.tokyjp01.jp.bb.gin.ntt.net (129.250.4.190)  194.153 ms  173.973 ms  175.132 ms
14  ae-2.ocn.tokyjp01.jp.bb.gin.ntt.net (129.250.12.198)  183.922 ms  290.438 ms  182.395 ms
15  118.23.168.22 (118.23.168.22)  178.607 ms
    118.23.168.23 (118.23.168.23)  189.651 ms
    60.37.27.86 (60.37.27.86)  199.148 ms
16  122.28.169.118 (122.28.169.118)  196.953 ms  193.416 ms
    122.28.169.114 (122.28.169.114)  185.112 ms
17  61.126.89.222 (61.126.89.222)  208.599 ms  189.001 ms  193.224 ms
18  * * *
 


X8oD

@cox.net

At 10am this morning, the sites seem to be working as usual. No issues!



nil
Java Geek
join:2000-11-27
kudos:2

Yep, fixed for me too, yay!


nickphx

join:2009-10-29
Phoenix, AZ
reply to nil

uh it's pinging that high because the site is in JAPAN.... Try taking a Trans-Atlantic voyage in under 200ms.



nil
Java Geek
join:2000-11-27
kudos:2

Good point

I don't normally sit there watching traceroutes and examining ping times, so guess never noticed that before.


ame101

join:2002-05-02
Southington, CT

Got a call back, was told "try it now", no real reason given, just happy it is fixed.