| reply to annoyed
Re: Metro Detroit slow internet? Yeah I am definitely feeling a major slow down every night at around the same time (10-ish). I'm going to call tomorrow and hopefully, after the mandatory cable run around where they try to blame my router (despite the fact that direct connecting doesn't help), will get some news. |
|
| I'm having slow speeds running through a router tonight.
Weird thing is I'm getting different routes depending upon if I;m connected to my router or the modem.
Support says they don't allow trace routes!
Check these out:
With Router
Tracing route to news.us.easynews.com [69.16.186.8]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 7 ms 9 ms 9 ms 172.31.12.238
4 9 ms 8 ms 8 ms gi1-2.core01.dtw03.atlas.cogentco.com [38.104.40
.77]
5 8 ms 9 ms 10 ms po4-0.core01.dtw04.atlas.cogentco.com [154.54.25
.62]
6 11 ms 12 ms 12 ms po4-0.core01.tol01.atlas.cogentco.com [154.54.25
.109]
7 118 ms 117 ms 118 ms po10-1.core01.ord01.atlas.cogentco.com [154.54.5
.153]
8 116 ms 117 ms 118 ms te7-7.mpd01.ord01.atlas.cogentco.com [154.54.1.9
8]
9 118 ms 118 ms 118 ms vl3489.mpd01.ord03.atlas.cogentco.com [154.54.5.
18]
10 118 ms 130 ms 121 ms te7-3.ccr02.ord03.atlas.cogentco.com [66.28.4.66
]
11 117 ms 118 ms 118 ms Tenge4-4-10000M.ar3.CHI2.gblx.net [64.212.107.73
]
12 119 ms 117 ms 123 ms 204.246.200.154
13 119 ms 117 ms 117 ms 1-3.r1.ch.hwng.net [209.197.1.137]
14 148 ms 150 ms * 2-1.r1.at.hwng.net [69.16.191.46]
15 157 ms 156 ms 156 ms 2-1.r2.dc.hwng.net [69.16.191.125]
16 157 ms 159 ms 160 ms ve1006.ar2.dc.hwng.net [69.16.190.126]
17 158 ms 158 ms 157 ms news.dc1.easynews.com [69.16.186.8]
Trace complete.
Without router:
Tracing route to news.us.easynews.com [69.16.186.8]
over a maximum of 30 hops:
1 * * * Request timed out.
2 8 ms 8 ms 9 ms 172.31.12.238
3 8 ms 9 ms 9 ms gi1-2.core01.dtw03.atlas.cogentco.com [38.104.40
.77]
4 9 ms 9 ms 9 ms po4-0.core01.dtw04.atlas.cogentco.com [154.54.25
.62]
5 11 ms 9 ms 9 ms po4-0.core01.tol01.atlas.cogentco.com [154.54.25
.109]
6 117 ms 119 ms 117 ms po10-1.core01.ord01.atlas.cogentco.com [154.54.5
.153]
7 117 ms 118 ms 118 ms po15-0.core02.ord01.atlas.cogentco.com [66.28.4.
62]
8 116 ms 118 ms * te7-7.ccr02.ord01.atlas.cogentco.com [154.54.3.2
54]
9 120 ms 116 ms 117 ms vl3491.ccr02.ord03.atlas.cogentco.com [154.54.6.
210]
10 15 ms 14 ms 16 ms Tenge4-4-10000M.ar3.CHI2.gblx.net [64.212.107.73
]
11 17 ms 23 ms 24 ms Highwinds-Network-Group-Chicago.TengigabitEthern
et2-4.ar5.CHI1.gblx.net [64.214.70.74]
12 19 ms 19 ms 18 ms 1-3.r1.ch.hwng.net [209.197.1.137]
13 45 ms 43 ms 44 ms 2-1.r1.at.hwng.net [69.16.191.46]
14 42 ms 44 ms 44 ms 2-1.r2.dc.hwng.net [69.16.191.125]
15 44 ms 44 ms 45 ms unknown.hwng.net [209.197.1.46]
16 41 ms 44 ms 43 ms ve8.ar2.dc.hwng.net [69.16.186.121]
17 43 ms 45 ms 41 ms news.dc1.easynews.com [69.16.186.8]
Trace complete.
I'm totaly baffled how this could occur. |
|
