cdysthe
Regular Contributor
Hi,
Update: I am now convinced it's my ISP which causes the problems below since they are still present when I hook up to the cable modem directly, so the post below doesn't really belong in this forum, sorry.
I have a problem with either my router, an RT-N66U or my ISP which is Suddenlink. Yesterday I started having issues connecting to our corporate VPN and e-mail clients and other Internet connected applications timed out a long time before they did anything. Online gaming also got impossible being cut off all the time. When I wanted to do a speedtest it took a long time to get the Speedtest.net site loaded, but when it ran the ping and speed was very good and what it normally is when everything works. I have never seen anything like this. I also tried to do a traceroute from the router to www.cnn.com and got this:
traceroute to www.cnn.com (157.166.238.17), 30 hops max, 38 byte packets
1 10.21.128.1 (10.21.128.1) 179.859 ms 7.019 ms 7.807 ms
2 173-219-245-152-link.sta.suddenlink.net (173.219.245.152) 9.008 ms 8.480 ms 7.967 ms
3 173-219-236-126-link.sta.suddenlink.net (173.219.236.126) 23.503 ms 20.011 ms 23.010 ms
4 xe-2-3-0.er2.dfw2.us.above.net (64.124.200.181) 19.360 ms 14.611 ms 14.826 ms
5 206.111.5.109.ptr.us.xo.net (206.111.5.109) 11.535 ms 13.925 ms 11.655 ms
6 207.88.13.242.ptr.us.xo.net (207.88.13.242) 36.096 ms 40.733 ms 43.526 ms
7 te-4-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.1) 37.077 ms 38.716 ms 38.363 ms
8 ae0d0.cir1.atlanta6-ga.us.xo.net (207.88.13.153) 32.859 ms 32.520 ms 31.844 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
Etc.
I tried to ping from the router and got this:
PING www.cnn.com (157.166.238.17): 56 data bytes
--- www.cnn.com ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
I am not able to determine if it is the router or my ISP. It started yesterday afternoon and is not gotten any better this morning. I am running the latest Merlin build on the router.
Any idea where I should start to look, or if calling my ISP is what needs to happen?
Update: I am now convinced it's my ISP which causes the problems below since they are still present when I hook up to the cable modem directly, so the post below doesn't really belong in this forum, sorry.
I have a problem with either my router, an RT-N66U or my ISP which is Suddenlink. Yesterday I started having issues connecting to our corporate VPN and e-mail clients and other Internet connected applications timed out a long time before they did anything. Online gaming also got impossible being cut off all the time. When I wanted to do a speedtest it took a long time to get the Speedtest.net site loaded, but when it ran the ping and speed was very good and what it normally is when everything works. I have never seen anything like this. I also tried to do a traceroute from the router to www.cnn.com and got this:
traceroute to www.cnn.com (157.166.238.17), 30 hops max, 38 byte packets
1 10.21.128.1 (10.21.128.1) 179.859 ms 7.019 ms 7.807 ms
2 173-219-245-152-link.sta.suddenlink.net (173.219.245.152) 9.008 ms 8.480 ms 7.967 ms
3 173-219-236-126-link.sta.suddenlink.net (173.219.236.126) 23.503 ms 20.011 ms 23.010 ms
4 xe-2-3-0.er2.dfw2.us.above.net (64.124.200.181) 19.360 ms 14.611 ms 14.826 ms
5 206.111.5.109.ptr.us.xo.net (206.111.5.109) 11.535 ms 13.925 ms 11.655 ms
6 207.88.13.242.ptr.us.xo.net (207.88.13.242) 36.096 ms 40.733 ms 43.526 ms
7 te-4-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.1) 37.077 ms 38.716 ms 38.363 ms
8 ae0d0.cir1.atlanta6-ga.us.xo.net (207.88.13.153) 32.859 ms 32.520 ms 31.844 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
Etc.
I tried to ping from the router and got this:
PING www.cnn.com (157.166.238.17): 56 data bytes
--- www.cnn.com ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
I am not able to determine if it is the router or my ISP. It started yesterday afternoon and is not gotten any better this morning. I am running the latest Merlin build on the router.
Any idea where I should start to look, or if calling my ISP is what needs to happen?
Last edited: