Ricky11465
join:2006-07-22
Monroe, MI
| So my first day with a cap?
So after returning from my family's house over the weekend. I find my service i would assume capped? Of course there might be an outage, or Comcast having an issue. But i must admit if they placed their throttling today in Michigan. Why me, i stream netflix and youtube as well as vonage.
I decided to do a little tracert if anyone can bear it. I like the 4294967264 ms ping portion. Also keep in mind i use opendns, however i have troubleshooted the issue to my best. Switching DNS servers, resetting modem, as well as router, and network connection. So i can safely say its not me, but somewhere on comcasts line. My upstream is 1 meg, from its ussual 2. And my Downstream 192kb or less. From the lovely powerboost performance of 12-16 megs. So i must ask, i am not in thier test area, but why is it i wake up to slow then read news that they started throttling while i slept?
Tracing route to google.com [64.233.187.99]
over a maximum of 30 hops:
1 52 ms 52 ms 52 ms 192.168.1.1
2 64 ms * 8 ms c-3-0-ubr01.monroe.mi.michigan.comcast.net [73.3
7.108.1]
3 74 ms 8 ms 8 ms ge-2-1-ur02.monroe.mi.michigan.comcast.net [68.8
6.120.157]
4 63 ms 63 ms 4294967264 ms te-0-4-0-5-ar01.taylor.mi.michigan.comcast
.net [68.87.190.169]
5 * * 72 ms pos-0-7-0-0-cr01.cleveland.oh.ibone.comcast.net
[68.86.85.49]
6 84 ms * 84 ms pos-0-6-0-0-cr01.chicago.il.ibone.comcast.net [6
8.86.85.50]
7 73 ms * 74 ms xe-10-1-0.edge1.Chicago2.Level3.net [4.71.248.17
]
8 22 ms 73 ms 74 ms vlan52.ebr2.Chicago2.Level3.net [4.69.138.190]
9 113 ms 106 ms 87 ms ae-2.ebr2.Washington1.Level3.net [4.69.132.70]
10 104 ms 103 ms 88 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.1
46]
11 36 ms 35 ms 4294967279 ms ae-1-69.edge1.Washington1.Level3.net [4.68
.17.16]
12 88 ms 95 ms 94 ms GOOGLE-INC.edge1.Washington1.Level3.net [4.79.23
1.6]
13 107 ms * 101 ms 66.249.95.149
14 50 ms 109 ms 115 ms 72.14.236.175
15 118 ms 105 ms 105 ms 216.239.49.226
16 * 48 ms * jc-in-f99.google.com [64.233.187.99]
17 59 ms 103 ms 51 ms jc-in-f99.google.com [64.233.187.99]
Trace complete.
Interesting aint it. |
