Review by RamsteinUSA 
UPDATED: 236 days ago
member for 1.8 years, 548 visits, last login: a few hours ago
 Vista,San Diego,CA
 $115 per month
 "Steady uninterrupted connection."
 "still has a few intermittent connection and/or slow downs"
 "Time Warner / RoadRunner has made great strides in service. But, still has a few small issues."
| Pre Sales information:
Install Co-ordination:
Connection Reliability:
Tech Support:
Services:
Value for money:
(ratings above consensus)
|
Update 04/12/2008:
I added a snapshop of packed loss problems...
original continued,
Most the time it runs fine, but there are many times when the connection slows down or takes a few moments to respond. Other times it screams at top speed 10000/100. If and when I call support, I wait until a problem festers for at least a few days or a couple weeks just to give them time to fix their own problems. I live in an area where most the people are older (retired) and are probably not even using High Speed Internet, and am pretty sure they are not downloading much music or files. If there is some network or node issues, they are not near me.
When I do talk to customer support and tell the connection is intermittent, they tell me there are no outstanding issues on their end. I know that I always ask the field techs about the latest/best connectors and they make sure I have the latest and greatest connectors on the cables from the service box on the street to the ends going to my TV and Computer.
Bottom line is, they are getting closer, but still have lots of problems on their network. The Cable to TV works 99.9% of the time. We did have an outage the other day on that Super Tuesday political voting day. They Cable for the TV died for a couple hours around 6 to 7:30 pm. My Internet connection stayed up. Go-Figure.
One more niggle nagging problem, The TV Programming on the on display guide on the TV still has advanced programming issues where the programming sometimes, often does not go beyond 12 hours. It is as if the people who input the data went on vacation in the middles of putting the data in for each TV show.
I hope TW/RR fixes the nodes, adds more capacity or does whatever they need soon to make the service more reliable. I still can't say it fully reliable.
I do want to give a Shout-Out for Time Warner, as they really made me a very happy customer. I won a contest and am now watching a Large flat screen HDTV LCD TV. I do probably watch more TV than many people, but I am mostly stuck at home, with some health problems, so I might as well enjoy my TV viewing as much as possible. Also, my family relies a lot on the Internet up and running, so I keep the family computer running at it's best too. The Internet is just as important to me, if not more because I enjoy all the information and communication, so I feel trends in the service whether it is working better or worse often.
The people at TW/RR are very courteous and friendly. The technicians are always good and thorough. They just need to add more capacity. All the infrastructure in my area or San Diego North County is new and is the latest and greatest. That just about sums it all up. I have lived in the same area for many years, and have seen the cable companies change hands probably five or six times. TW/RR 95% there as far as having a constantly high performing network where I live.
Attachments:
Followup comments:  
Just Concerned
@rr.com
| Everything looks good up to your PC from the outside... Running traces back to your IP address shows good latency all the way up to your IP address. With latency like you're showing it seems like your either uploading something while the tests are running or your connection is being leeched off of through the router...
Although right now, your IP is responding with latency in the low 20s when I ping it, just like your the neighboring IPs when I pinged them.
Your speed tests show that your getting close to 4000/384 which is the standard HSO speed for RR in your area, so I'm not sure where you get the slow speed claims... the majority of the speed tests you've done are getting what your provisioned for. The ones that aren't are showing low upload, which is more than likely related to what is causing the high latency.
If you want a second opinion and maybe some help, you should visit the RR forum here. | |
| |  | 
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 18th, @01:27PM
| Re: RoadRunner Router Nightmare the Norm for RR Subscribers No it's not.
Which router on that list is your connection going through?
It's also possible some of the routers on that list are configured to filter ICMP packets (pings). I wouldn't exactly trust that "routerwatch" list without a trace or two through the listed routers to customers they are inline with.
Even a LQ test to you looked good earlier today:
»/linequality/nil/2228901
--
Don't mind me, I'm just trying to help...
| |
|
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 18th, @01:31PM
| Bigger picture Looking at the long term monitor things look a bit different:
»ny-monitor.dslreports.com/r3/cri···%3Am%3Ay
It looks like something affecting your latency is being turned on and off, it's not the normal "oversubscription" graph.
Compare that graph, to the graph to your gateway IP:
»ny-monitor.dslreports.com/r3/cri···%3Am%3Ay
You should also check an inbound trace (or a few) to see where things go bad:
»www.traceroute.org/#USA
Tracing back to your IP shows the problem is VERY local to you, with the latency only being bad at your IP.
and posting the actual link to the local speed test results for your area isn't bad either:
»/archive?zip=9···m=rr.com
--
Don't mind me, I'm just trying to help...
| |
| | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
| Re: Bigger picture said by RamsteinUSA :said by MacLeech :Looking at the long term monitor things look a bit different: » ny-monitor.dslreports.com/r3/cri···%3Am%3AyIt looks like something affecting your latency is being turned on and off, it's not the normal "oversubscription" graph. Keeping an eye on this... record.. Just make sure that is still your Public IP address. It may have changed when you pulled out the router.
--
Don't mind me, I'm just trying to help...
| |
| | | | RamsteinUSA
join:2007-02-15
Vista, CA
 ·RoadRunner Cable
| Re: Bigger picture said by MacLeech :said by RamsteinUSA :said by MacLeech :Looking at the long term monitor things look a bit different: » ny-monitor.dslreports.com/r3/cri···%3Am%3AyIt looks like something affecting your latency is being turned on and off, it's not the normal "oversubscription" graph. Keeping an eye on this... record.. Just make sure that is still your Public IP address. It may have changed when you pulled out the router. IP stayed the same | |
| RamsteinUSA
join:2007-02-15
Vista, CA
·RoadRunner Cable
|  TraceRoute
If you did not intend to come to this page...
If you did not intend to come to this page, but instead wanted to go to Google, Yahoo, etc. and wound up here, then your Internet Service Provider's (ISP) Domain Name Systems (DNS) servers have been attacked by parties unknown.
You should contact your ISP and tell them they need to fix their DNS servers. MIT and the operator of this server have nothing to do with the attack, like you, we are victims.
Trace Route from MIT
IMPORTANT: This tool works by sending a series of UDP packets with different port numbers and TTL (Time To Live). If you are running firewall software, your software may interpret the incoming packets as a hostile "port scan" originating from this server (jis.mit.edu). Rest assured, your system is not being attacked.
1 W92-RTR-1-W92SRV21.MIT.EDU (18.7.21.1) 0.553 ms 0.306 ms 0.275 ms
2 EXTERNAL-RTR-1-BACKBONE.MIT.EDU (18.168.0.18) 0.768 ms 1.583 ms 0.467 ms
3 ge-6-23.car2.Boston1.Level3.net (4.79.2.1) 0.406 ms 0.423 ms 0.431 ms
4 ae-5-5.ebr1.NewYork1.Level3.net (4.69.132.250) 8.851 ms 5.493 ms 16.130 ms
5 ae-3.ebr1.Washington1.Level3.net (4.69.132.89) 15.907 ms 22.228 ms 18.894 ms
6 ae-2.ebr1.Atlanta2.Level3.net (4.69.132.85) 30.116 ms 24.634 ms 33.993 ms
7 ae-7.ebr2.Dallas1.Level3.net (4.69.134.21) 43.985 ms 55.600 ms 54.126 ms
8 ae-3.ebr2.LosAngeles1.Level3.net (4.69.132.77) 88.939 ms 82.189 ms 76.852 ms
9 ae-22-52.car2.LosAngeles1.Level3.net (4.68.102.45) 77.773 ms ae-22-54.car2.LosAngeles1.Level3.net (4.68.102.109) 77.802 ms ae-22-56.car2.LosAngeles1.Level3.net (4.68.102.173) 76.582 ms
10 ROADRUNNER.car2.LosAngeles1.Level3.net (4.78.195.190) 77.804 ms ROADRUNNER.car2.LosAngeles1.Level3.net (4.71.36.106) 77.144 ms ROADRUNNER.car2.LosAngeles1.Level3.net (4.71.36.74) 82.989 ms
11 tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) 83.386 ms 83.611 ms 83.977 ms
12 76.167.9.193 (76.167.9.193) 84.853 ms 83.982 ms 84.964 ms
13 gig3-21.ontrca1-rtr1.socal.rr.com (76.167.2.51) 87.094 ms 87.105 ms 90.876 ms
14 cpe-76-176-0-9.san.rr.com (76.176.0.9) 88.810 ms 89.005 ms 88.794 ms
15 * * *
16 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) 538.463 ms 660.109 ms 653.484 ms
17 * * *
18 * * *
19 * * * | |
| |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 18th, @04:53PM
| Re: TraceRoute Hop 14 is good and before is good.
Hop 15 is the CMTS, but its addressed with a private 10.xxx.xxx.xxx IP which is why it doesn't respond to outside pings.
Your router is at hop 16 and as you can see is the only hop with high latency. The hops after 16 are caused by your router's packet filtering.
The problem is somewhere between your PC and the CMTS. If you ping other people on the same public subnet as you, their latency is good...
The pattern of your latency is more consistent with upload traffic saturating the configured bandwidth on your modem.
P.S. Your modem shows that you've uploaded over 1 GB of data in the last 12 hours... that averages out to a constant 194 kbit/sec upload bandwidth usage...
| |
| | | RamsteinUSA
join:2007-02-15
Vista, CA
·RoadRunner Cable
| Re: TraceRoute
IP: 64.86.142.81
Date/Time: 5/18/2007 1:43:17 PM
1 1 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.0.1]
2 345 ms 505 ms 10 ms 529 ms 483 ms 8 ms cpe-76-176-16-1.san.res.rr.com [76.176.16.1]
3 389 ms 479 ms 11 ms 499 ms 434 ms 13 ms [76.176.0.33]
4 351 ms 450 ms 139 ms * * 15 ms 24-48-219-173.losaca.adelphia.net [24.48.219.173]
5 915 ms * 95 ms * * 14 ms prt24.vnnyca2-rtr1.socal.rr.com [76.167.2.15]
6 * * * * * N/A [-]
7 N/A 347 ms * N/A N/A 312 ms te-3-1.car1.Tustin1.Level3.net [4.71.104.149]
8 * 312 ms 78 ms * * N/A ae-3-3.ebr1.LosAngeles1.Level3.net [4.69.132.218]
9 * 292 ms 32 ms * * N/A ae-11-53.car1.LosAngeles1.Level3.net [4.68.102.76]
10 713 ms * 21 ms * * N/A if-2-0.mcore3.LAA-LosAngeles.teleglobe.net [216.6.84.33]
11 713 ms * 22 ms * * N/A if-3-0.mcore4.LAA-LosAngeles.teleglobe.net [216.6.85.5]
12 666 ms * 22 ms * 140 ms 123 ms [64.86.142.81]
Ping statistics for www.foxnews.com
Packets: Sent = 6, Received = 4, Lost = 2 (33.3%)
Round Trip Times: Minimum = 22ms, Maximum = 666ms, Average = 237ms | |
| | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 18th, @05:44PM
| Re: TraceRoute Again the trace is consistent with upstream bandwidth saturation before the CMTS... although your pings to the your own router are good so the problem isn't between the PC you are using now and your own router, but that doesn't include the links between the router and modem; modem and CMTS.
The IP for the CMTS on the return trace is 10.125.64.1 you can trace to it or any other IP from here.
You'll get something like this:
GOOD TRACE
FROM www.adelphiacom.net TO 76.176.20.108.
traceroute to 76.176.20.108 (76.176.20.108), 64 hops max, 44 byte packets
1 i0.chi75.adelphiacom.net (66.109.10.17) 0.584 ms 0.431 ms 0.494 ms
2 ge-1-2-0.a0.chi75.twc-core.net (66.109.3.17) 0.491 ms 0.383 ms 0.405 ms
3 ae-0-0.c1.chi75.twc-core.net (66.109.3.5) 0.449 ms 0.355 ms 0.365 ms
4 as-1-0.c1.dfw91.twc-core.net (66.109.0.66) 25.660 ms 25.629 ms 25.601 ms
5 ge-7-1-0.c0.dfw91.twc-core.net (66.109.0.225) 25.641 ms 25.654 ms 25.633 ms
6 66.109.3.85 (66.109.3.85) 61.481 ms 66.083 ms 61.507 ms
7 ge-7-1-0.c0.lax91.twc-core.net (66.109.3.161) 61.704 ms 70.737 ms 61.608 ms
8 66.109.3.134 (66.109.3.134) 61.859 ms 61.835 ms 61.858 ms
9 tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) 67.953 ms 68.264 ms 67.999 ms
10 76.167.9.193 (76.167.9.193) 69.425 ms 69.404 ms 69.474 ms
11 76.167.2.51 (76.167.2.51) 75.818 ms 71.986 ms 75.862 ms
12 cpe-76-176-0-9.san.rr.com (76.176.0.9) 73.638 ms 76.614 ms 73.092 ms
13 10.125.64.1 (10.125.64.1) 74.071 ms 74.486 ms 74.103 ms
14 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) 81.380 ms 85.867 ms 82.106 ms
15 * * *
BAD TRACE
traceroute to 76.176.20.108 (76.176.20.108), 64 hops max, 44 byte packets
1 i0.chi75.adelphiacom.net (66.109.10.17) 0.628 ms 0.392 ms 0.400 ms
2 ge-1-2-0.a0.chi75.twc-core.net (66.109.3.17) 0.453 ms 0.351 ms 0.317 ms
3 ae-0-0.c1.chi75.twc-core.net (66.109.3.5) 0.344 ms 0.348 ms 0.311 ms
4 as-1-0.c1.dfw91.twc-core.net (66.109.0.66) 25.642 ms 25.618 ms 25.614 ms
5 ge-7-1-0.c0.dfw91.twc-core.net (66.109.0.225) 25.644 ms 25.639 ms 25.628 ms
6 66.109.3.85 (66.109.3.85) 61.521 ms 61.497 ms 61.511 ms
7 ge-7-1-0.c0.lax91.twc-core.net (66.109.3.161) 61.610 ms 61.592 ms 61.597 ms
8 66.109.3.134 (66.109.3.134) 61.814 ms 61.829 ms 61.854 ms
9 tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) 67.947 ms 67.955 ms 67.979 ms
10 76.167.9.193 (76.167.9.193) 69.429 ms 69.512 ms 69.395 ms
11 gig3-21.ontrca1-rtr1.socal.rr.com (76.167.2.51) 75.828 ms 72.137 ms 75.551 ms
12 cpe-76-176-0-9.san.rr.com (76.176.0.9) 77.280 ms 73.133 ms 77.140 ms
13 10.125.64.1 (10.125.64.1) 74.799 ms 74.601 ms 74.000 ms
14 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) 368.492 ms 720.175 ms 629.204 ms
15 *
Can you see the big latency jump happens at your IP address?? It's so sudden and pronounced between good and bad, it's as if someone connected through your modem was turning p2p filesharing on and off or another computer connected to your router was using alot of upstream bandwidth.
Then again it could be someone with an uncapped modem connected to the same CMTS upstream port... but that is extremely rare and easy to catch if its even possible any more...
--
Don't mind me, I'm just trying to help...
| |
| | | | | RamsteinUSA
join:2007-02-15
Vista, CA
·RoadRunner Cable
| Re: TraceRoute
FROM www.adelphiacom.net TO 76.176.20.108.
traceroute to 76.176.20.108 (76.176.20.108), 64 hops max, 44 byte packets
1 i0.chi75.adelphiacom.net (66.109.10.17) 0.555 ms 0.417 ms 0.356 ms
2 ge-1-2-0.a0.chi75.twc-core.net (66.109.3.17) 0.448 ms 0.359 ms 0.312 ms
3 ae-0-0.c1.chi75.twc-core.net (66.109.3.5) 0.330 ms 0.331 ms 0.301 ms
4 as-1-0.c1.dfw91.twc-core.net (66.109.0.66) 25.639 ms 25.660 ms 25.627 ms
5 ge-7-1-0.c0.dfw91.twc-core.net (66.109.0.225) 25.642 ms 25.634 ms 25.626 ms
6 66.109.3.85 (66.109.3.85) 61.573 ms 61.474 ms 61.452 ms
7 ge-7-1-0.c0.lax91.twc-core.net (66.109.3.161) 61.623 ms 61.701 ms 61.610 ms
8 66.109.3.134 (66.109.3.134) 61.823 ms 61.850 ms 61.846 ms
9 tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) 68.268 ms 67.995 ms 67.934 ms
10 76.167.9.193 (76.167.9.193) 74.885 ms 69.403 ms 69.179 ms
11 76.167.2.51 (76.167.2.51) 75.521 ms 71.842 ms 75.835 ms
12 cpe-76-176-0-9.san.rr.com (76.176.0.9) 76.905 ms 76.917 ms 73.084 ms
13 10.125.64.1 (10.125.64.1) 74.963 ms 74.185 ms 74.324 ms
14 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) 86.726 ms 122.218 ms 80.336 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * * | |
| | | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 18th, @05:39PM
| Re: TraceRoute All the hops after your IP at 76.176.20.108 which is hop 14 in the trace are within your home network. The non-responses are caused by YOUR router filtering traffic.
P.S. Now you modem shows it was reset about 8 minutes ago and has had less than 1/2 MB uploaded through it. Your public IP also stopped responding to pings... so it's either changed, firewalled, or off. All the graphs and monitors based on that IP will show 100% packet loss for now...
--
Don't mind me, I'm just trying to help...
| |
| | | | | | | RamsteinUSA
join:2007-02-15
Vista, CA
·RoadRunner Cable
| Re: TraceRoute
traceroute from www.net.berkeley.edu to 76.176.20.108
1 inr-211-inr-203--128-32-206-1.HSRP.Berkeley.EDU (128.32.206.1) 0.957 ms 0.511 ms 0.495 ms
2 g3-1.inr-201-eva.Berkeley.EDU (128.32.255.1) 0.455 ms 0.511 ms 0.753 ms
3 ge-1-2-0.inr-002-reccev.Berkeley.EDU (128.32.0.36) 0.684 ms 0.559 ms 0.527 ms
4 oak-dc2--ucb-ge.cenic.net (137.164.23.29) 0.767 ms * 1.409 ms
5 dc-sfo-dc1--oak-dc2-pos.cenic.net (137.164.22.32) 2.175 ms 1.853 ms 1.840 ms
6 dc-svl-dc1--sfo-dc1-pos.cenic.net (137.164.22.34) 2.133 ms 3.433 ms 2.132 ms
7 te1-1--480.tr01-sttlwa01.transitrail.net (137.164.131.253) 2.082 ms 2.297 ms 2.221 ms
8 paix-pal.adelphiacom.net (198.32.176.41) 2.560 ms 2.560 ms 2.682 ms
9 66.109.3.198 (66.109.3.198) 3.118 ms 2.980 ms 3.578 ms
10 66.109.0.22 (66.109.0.22) 10.831 ms 10.972 ms 10.768 ms
11 66.109.3.134 (66.109.3.134) 12.363 ms 13.137 ms 12.579 ms
12 tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) 18.671 ms 18.934 ms 18.564 ms
13 76.167.9.193 (76.167.9.193) 20.657 ms 20.778 ms 19.828 ms
14 gig3-21.ontrca1-rtr1.socal.rr.com (76.167.2.51) 23.207 ms 23.303 ms 22.643 ms
15 cpe-76-176-0-9.san.rr.com (76.176.0.9) 27.945 ms 24.178 ms 28.228 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * | |
| | | | | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 18th, @05:49PM
| Re: TraceRoute Thank you for removing the router, it helps the troubleshooting process.
Don't worry about the packet loss at 76.167.2.66, it appears to be a router configured to filter ping packets directed at it but it passes them through just fine.
You may want to use the Adelphia traceroute page so the CMTS will be able to respond to pings. You may also want to allow the firewall on your computer to respond to pings because right now you last trace TO you computer is cutoff 2 hops upstream. One being the CMTS with the private IP, the other being your computer with the firewall.
If you don't have a firewall, then it's possible you're tracing to the wrong IP. It tends to change when you remove the router unless you spoofed the MAC of the NIC in your PC when you installed it.
--
Don't mind me, I'm just trying to help...
| |
| | | | | | | | RamsteinUSA
join:2007-02-15
Vista, CA
·RoadRunner Cable
| If you did not intend to come to this page...
If you did not intend to come to this page, but instead wanted to go to Google, Yahoo, etc. and wound up here, then your Internet Service Provider's (ISP) Domain Name Systems (DNS) servers have been attacked by parties unknown.
You should contact your ISP and tell them they need to fix their DNS servers. MIT and the operator of this server have nothing to do with the attack, like you, we are victims.
Trace Route from MIT
IMPORTANT: This tool works by sending a series of UDP packets with different port numbers and TTL (Time To Live). If you are running firewall software, your software may interpret the incoming packets as a hostile "port scan" originating from this server (jis.mit.edu). Rest assured, your system is not being attacked.
1 W92-RTR-1-W92SRV21.MIT.EDU (18.7.21.1) 35.031 ms 4.233 ms 0.355 ms
2 * EXTERNAL-RTR-1-BACKBONE.MIT.EDU (18.168.0.18) 14.964 ms 12.465 ms
3 ge-6-23.car2.Boston1.Level3.net (4.79.2.1) 0.355 ms 0.413 ms 0.381 ms
4 ae-5-5.ebr1.NewYork1.Level3.net (4.69.132.250) 16.479 ms 16.219 ms 18.026 ms
5 ae-3.ebr1.Washington1.Level3.net (4.69.132.89) 10.818 ms 14.157 ms 18.340 ms
6 ae-2.ebr1.Atlanta2.Level3.net (4.69.132.85) 38.014 ms 24.649 ms 34.929 ms
7 ae-7.ebr2.Dallas1.Level3.net (4.69.134.21) 44.432 ms 57.499 ms 53.688 ms
8 ae-3.ebr2.LosAngeles1.Level3.net (4.69.132.77) 77.749 ms 76.804 ms 89.396 ms
9 ae-22-52.car2.LosAngeles1.Level3.net (4.68.102.45) 76.605 ms ae-22-54.car2.LosAngeles1.Level3.net (4.68.102.109) 77.338 ms ae-22-56.car2.LosAngeles1.Level3.net (4.68.102.173) 76.110 ms
10 ROADRUNNER.car2.LosAngeles1.Level3.net (4.78.195.190) 77.006 ms ROADRUNNER.car2.LosAngeles1.Level3.net (4.71.36.106) 77.033 ms ROADRUNNER.car2.LosAngeles1.Level3.net (4.78.195.190) 77.488 ms
11 tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) 84.972 ms 84.175 ms 85.150 ms
12 76.167.9.193 (76.167.9.193) 85.409 ms 86.491 ms 84.751 ms
13 gig3-21.ontrca1-rtr1.socal.rr.com (76.167.2.51) 91.171 ms 91.115 ms 86.147 ms
14 cpe-76-176-0-9.san.rr.com (76.176.0.9) 89.313 ms 88.262 ms 88.525 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * * | |
| | | | | | | | | | | | | | | | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
| Re: TraceRoute RR turned off most of the ICMP filtering done by Adelphia a few weeks ago. That's one of the reasons why the LQ tests "look" better than they did with Adelphia.
--
Don't mind me, I'm just trying to help...
| |
| | | | | | | | | | RamsteinUSA
join:2007-02-15
Vista, CA
·RoadRunner Cable
| Target Name: hyperfighter.sk
IP: 213.215.67.3
Date/Time: 5/18/2007 2:49:52 PM to 5/18/2007 2:51:37 PM
1 9 ms 10 ms 11 ms 10 ms 10 ms 8 ms 9 ms 10 ms cpe-76-176-16-1.san.res.rr.com [76.176.16.1]
2 9 ms 9 ms 8 ms 9 ms 9 ms 9 ms 9 ms 9 ms [76.176.0.33]
3 15 ms 17 ms 12 ms 13 ms 12 ms 12 ms 138 ms 12 ms gig1-23.lamdca1-rtr1.socal.rr.com [76.167.2.50]
4 22 ms 20 ms 22 ms 47 ms * 22 ms * 19 ms tge3-0-0.lsanca1-rtr1.socal.rr.com [76.167.2.76]
5 28 ms 23 ms N/A 21 ms N/A N/A 18 ms 18 ms pop1-las-P5-0.atdn.net [66.185.143.5]
6 25 ms 21 ms 21 ms 164 ms 22 ms 21 ms 22 ms 21 ms Sprint.atdn.net [66.185.150.254]
7 21 ms 19 ms 24 ms 20 ms 22 ms 31 ms 20 ms 22 ms sl-bb23-ana-1-0-0.sprintlink.net [144.232.20.207]
8 20 ms 20 ms 21 ms 23 ms 24 ms 20 ms 94 ms 20 ms sl-bb21-ana-10-0.sprintlink.net [144.232.1.185]
9 56 ms 53 ms 53 ms 53 ms 53 ms 53 ms 54 ms 53 ms sl-bb25-fw-1-0-0.sprintlink.net [144.232.20.65]
10 62 ms 65 ms 63 ms 64 ms 63 ms 128 ms 63 ms 64 ms sl-bb20-kc-3-0.sprintlink.net [144.232.20.5]
11 79 ms 80 ms 79 ms 80 ms 79 ms 78 ms 81 ms 79 ms sl-bb25-chi-9-0.sprintlink.net [144.232.20.109]
12 80 ms 84 ms 79 ms 111 ms 78 ms 80 ms 77 ms 79 ms sl-bb21-chi-13-0.sprintlink.net [144.232.26.89]
13 98 ms 96 ms 96 ms 93 ms 92 ms 92 ms 99 ms 93 ms sl-bb22-nyc-15-0.sprintlink.net [144.232.9.148]
14 91 ms 93 ms 110 ms 92 ms 91 ms 91 ms 91 ms 92 ms sl-bb21-nyc-14-0.sprintlink.net [144.232.7.101]
15 97 ms 283 ms 92 ms 92 ms 92 ms 93 ms 94 ms 93 ms sl-bb23-nyc-3-0.sprintlink.net [144.232.7.109]
16 167 ms 167 ms 169 ms 167 ms 168 ms 167 ms 166 ms 166 ms sl-bb20-par-11-0.sprintlink.net [144.232.20.44]
17 178 ms 177 ms 175 ms 176 ms 228 ms 177 ms 180 ms 178 ms sl-bb21-fra-13-0.sprintlink.net [213.206.129.66]
18 190 ms 185 ms 187 ms 188 ms 189 ms 188 ms 190 ms 190 ms sl-bb21-vie-3-0.sprintlink.net [213.206.129.122]
19 191 ms 190 ms 190 ms 189 ms 189 ms 187 ms 190 ms 189 ms sl-bb20-vie-15-0-0.sprintlink.net [80.66.136.42]
20 191 ms 191 ms 189 ms 190 ms 190 ms 189 ms 192 ms 188 ms sl-gw10-vie-14-0-0.sprintlink.net [80.66.136.35]
21 189 ms 197 ms 190 ms 189 ms 188 ms 186 ms 187 ms 187 ms sle-gtshu-24-0.sprintlink.net [80.66.137.90]
22 188 ms 187 ms 189 ms 191 ms 190 ms 189 ms 189 ms 190 ms p1-0.sk2.gtsce.net [195.39.208.146]
23 193 ms 189 ms 187 ms 188 ms 188 ms 186 ms 187 ms 188 ms [62.168.110.105]
24 189 ms 187 ms 187 ms 189 ms 190 ms 189 ms 190 ms 189 ms swg2.sh.ba.gts.sk [62.168.96.139]
25 192 ms 189 ms 186 ms 187 ms 190 ms 188 ms 188 ms 189 ms mail.senicanet.net [213.215.67.3]
Ping statistics for hyperfighter.sk
Packets: Sent = 8, Received = 8, Lost = 0 (0.0%)
Round Trip Times: Minimum = 186ms, Maximum = 192ms, Average = 188ms | |
| | | | | | | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 18th, @06:07PM
| Re: TraceRoute You're tracing to a server in Slovakia?
The big jump in pings between hop 15 and 16 is the link between New York and Paris. It then looks like it goes through Frankfurt, Viena, Hungary, and a few more hops before that server in Slovakia.
Must be a nice flight sim server to play on one that far away.
--
Don't mind me, I'm just trying to help...
| |
| | | | | | | | | | RamsteinUSA
join:2007-02-15
Vista, CA
·RoadRunner Cable
| Re: TraceRoute
VisualRoute Connection Test to 76.176.20.108
Performed on 18 May 2007 21:58:07 GMT
---------------------------------------------------------------------------------- ----------
---------------------------------------------------------------------------------- ---------------------------------------------------------------------------------- ------------
| Hop | %loss | IP Address | Node Name | Location | ms | Graph | Network |
---------------------------------------------------------------------------------- ---------------------------------------------------------------------------------- ------------
| 0 | 0 | 205.234.111.204 | DTG316.visualware.com | Ashburn, VA, USA? | - | | Defender Technologies Group LLC DEFENDER-1 |
| 1 | 0 | 205.234.111.129 | r03-8.iad.defenderhosting.com | Washington, DC, USA | 0 | + | Defender Technologies Group LLC DEFENDER-1 |
| 2 | 0 | 69.65.112.25 | r01.iad.defenderhosting.com | Washington, DC, USA | 22 | +---- | Defender Technologies Group LLC DEFENDER-1 |
| 3 | 0 | 198.186.192.253 | - | - | 28 | +------ | Prescient Software Inc. NETBLK-PRESCIENT01 |
| 4 | 0 | 69.31.31.113 | 134.po2.ar1.iad1.us.nlayer.net | Dulles, VA, USA | 0 | + | nLayer Communications Internal/Backbone NLYR-69-31-31-0-1 |
| 5 | 0 | 69.31.30.26 | 37.ae-02-00-00.p1.dca91.adelphiacom.net | Washington, DC, USA | 0 | + | nLayer Communications Inc. NLYR-ARIN-BLK2 |
| 6 | 0 | 66.109.1.133 | - | Herndon, VA, USA? | 0 | + | Road Runner HoldCo LLC COUDERSPORTBB-2 |
| 7 | 0 | 66.109.3.90 | - | Herndon, VA, USA? | 67 | + | Road Runner HoldCo LLC COUDERSPORTBB-2 |
| 8 | 0 | 66.109.3.161 | - | Herndon, VA, USA? | 67 | + | Road Runner HoldCo LLC COUDERSPORTBB-2 |
| 9 | 0 | 66.109.3.174 | - | Herndon, VA, USA? | 67 | + | Road Runner HoldCo LLC COUDERSPORTBB-2 |
| 10 | 10 | 76.167.2.77 | tge10-2.ontrca1-swt1.socal.rr.com | Herndon, VA, USA? | 92 | +------ | Road Runner HoldCo LLC RRACI |
| 11 | 0 | 76.167.9.193 | - | Herndon, VA, USA? | 102 | -+------ | Road Runner HoldCo LLC RRACI |
| 12 | 0 | 76.167.2.51 | gig3-21.ontrca1-rtr1.socal.rr.com | Herndon, VA, USA? | 80 | + | Road Runner HoldCo LLC RRACI |
| 13 | 0 | 76.176.0.9 | cpe-76-176-0-9.san.rr.com | San Diego, CA, USA | 78 | + | Road Runner HoldCo LLC RRACI |
| 14 | 0 | 10.125.64.1 | - | - | 90 | +--- | (private use) |
| 15 | 0 | 76.176.20.108 | cpe-76-176-20-108.san.res.rr.com | San Diego, CA, USA | 86 | + | Road Runner HoldCo LLC RRACI |
---------------------------------------------------------------------------------- ---------------------------------------------------------------------------------- ------------ | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | RamsteinUSA
join:2007-02-15
Vista, CA
·RoadRunner Cable
| Re: TraceRoute
Traceroute
tracing path from www.net.princeton.edu to 76.176.20.108 ...
traceroute to 76.176.20.108 (76.176.20.108), 30 hops max, 40 byte packets
1 gigagate1 (128.112.128.114) 0.716 ms 0.305 ms 0.334 ms
2 vgate1 (128.112.12.22) 0.341 ms 0.323 ms 0.347 ms
3 209.92.72.201 (209.92.72.201) 1.571 ms 1.475 ms 1.324 ms
4 ge-1-1-0-311.core1.phlapafg.uslec.net (169.130.105.18) 84.057 ms 197.720 ms 157.605 ms
5 4.78.164.9 (4.78.164.9) 2.012 ms 2.202 ms 1.907 ms
6 ge-7-0-0.mp1.Philadelphia1.Level3.net (209.247.9.229) 45.203 ms 2.028 ms 2.089 ms
7 as-0-0.bbr1.LosAngeles1.Level3.net (64.159.1.157) 67.918 ms ae-0-0.bbr2.LosAngeles1.Level3.net (64.159.1.126) 67.807 ms as-0-0.bbr1.LosAngeles1.Level3.net (64.159.1.157) 67.793 ms
8 ae-22-54.car2.LosAngeles1.Level3.net (4.68.102.109) 67.661 ms ae-12-55.car2.LosAngeles1.Level3.net (4.68.102.141) 68.465 ms ae-22-54.car2.LosAngeles1.Level3.net (4.68.102.109) 67.833 ms
9 ROADRUNNER.car2.LosAngeles1.Level3.net (4.71.36.74) 68.082 ms ROADRUNNER.car2.LosAngeles1.Level3.net (4.78.195.190) 68.121 ms 76.766 ms
10 tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) 73.903 ms 73.618 ms 73.359 ms
11 76.167.9.193 (76.167.9.193) 75.349 ms 76.073 ms 75.557 ms
12 gig3-21.ontrca1-rtr1.socal.rr.com (76.167.2.51) 82.151 ms 80.997 ms 81.265 ms
13 cpe-76-176-0-9.san.rr.com (76.176.0.9) 78.810 ms 78.416 ms 79.076 ms
14 * * *
15 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) 1634.799 ms 1567.647 ms 1745.024 ms
16 * * *
17 * * *
| |
| | | | | | | | | | RamsteinUSA
join:2007-02-15
Vista, CA
·RoadRunner Cable
| Re: TraceRoute
traceroute: Warning: Multiple interfaces found; using 128.105.7.40 @ eth0
traceroute to 76.176.20.108 (76.176.20.108), 30 hops max, 40 byte packets
1 svi-7.cisco1.cs.wisc.edu (128.105.7.248) 0.492 ms 0.418 ms 0.357 ms
2 ge-5-1.cisco-border1.cs.wisc.edu (128.105.1.1) 0.603 ms 0.475 ms 0.483 ms
3 r-cssc-b280c-1-core-vlan-493.net.wisc.edu (144.92.128.194) 1.481 ms 0.601 ms 0.356 ms
4 r-peer-vlan-1500.net.wisc.edu (146.151.164.49) 0.605 ms 0.475 ms 0.859 ms
5 r-uwmadison-isp-ge-2-1-3-947.wiscnet.net (216.56.1.25) 0.606 ms 0.726 ms 0.609 ms
6 65.77.115.177 (65.77.115.177) 0.607 ms 0.712 ms 0.731 ms
7 brvwil1wcx3-pos1-2.wcg.net (64.200.236.33) 3.854 ms 3.851 ms 4.105 ms
8 64.200.249.190 (64.200.249.190) 3.615 ms 3.752 ms 3.732 ms
9 te-4-3-70.car2.Chicago1.Level3.net (4.68.110.33) 4.484 ms 4.592 ms 4.605 ms
10 ae-31-55.ebr1.Chicago1.Level3.net (4.68.101.158) 14.979 ms ae-32-56.ebr2.Chicago1.Level3.net (4.68.101.190) 11.832 ms ae-31-55.ebr1.Chicago1.Level3.net (4.68.101.158) 11.206 ms
11 ae-1-100.ebr1.Chicago1.Level3.net (4.69.132.41) 17.463 ms ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 35.069 ms 30.584 ms
12 ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 35.947 ms ae-1-100.ebr1.Denver1.Level3.net (4.69.132.37) 30.088 ms 30.202 ms
13 ae-3.ebr2.SanJose1.Level3.net (4.69.132.57) 63.066 ms ae-1-100.ebr1.Denver1.Level3.net (4.69.132.37) 39.443 ms ae-3.ebr2.SanJose1.Level3.net (4.69.132.57) 62.318 ms
14 ae-1-100.ebr1.SanJose1.Level3.net (4.69.132.1) 63.557 ms 67.065 ms 72.049 ms
15 ae-1-100.ebr1.SanJose1.Level3.net (4.69.132.1) 72.321 ms ae-2.ebr1.LosAngeles1.Level3.net (4.69.132.10) 82.420 ms 71.008 ms
16 ae-12-51.car2.LosAngeles1.Level3.net (4.68.102.13) 72.897 ms ae-12-53.car2.LosAngeles1.Level3.net (4.68.102.77) 71.306 ms ae-12-55.car2.LosAngeles1.Level3.net (4.68.102.141) 71.907 ms
17 ae-12-51.car2.LosAngeles1.Level3.net (4.68.102.13) 70.868 ms ROADRUNNER.car2.LosAngeles1.Level3.net (4.71.36.106) 70.769 ms ROADRUNNER.car2.LosAngeles1.Level3.net (4.71.36.74) 72.816 ms
18 ROADRUNNER.car2.LosAngeles1.Level3.net (4.71.36.74) 71.644 ms tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) 78.672 ms 77.405 ms
19 76.167.9.193 (76.167.9.193) 79.193 ms tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) 78.269 ms 76.167.9.193 (76.167.9.193) 78.785 ms
20 gig3-21.ontrca1-rtr1.socal.rr.com (76.167.2.51) 81.173 ms 81.662 ms 81.555 ms
21 gig3-21.ontrca1-rtr1.socal.rr.com (76.167.2.51) 81.546 ms cpe-76-176-0-9.san.rr.com (76.176.0.9) 82.935 ms gig3-21.ontrca1-rtr1.socal.rr.com (76.167.2.51) 81.522 ms
22 * * cpe-76-176-0-9.san.rr.com (76.176.0.9) 87.167 ms
23 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) 1020.466 ms 840.457 ms 679.680 ms
24 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) 478.160 ms * *
25 * * *
Look at:
23 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) 1020.466 ms 840.457 ms 679.680 ms
24 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) 478.160 ms
| |
| | | | | | | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 19th, @12:50PM
| Re: TraceRoute Calm down. Getting mad won't fix the problem.
The network (from the CMTS to the internet) isn't the problem. Check the monitor from the server in NY to your CMTS gateway:
»ny-monitor.dslreports.com/r3/cri···%3Am%3Ay
It's something local between the CMTS and you. Every trace you've posted shows that.
What were you doing with the modem overnight?
Was it sitting connected to one computer
Was the router reconnected?
Is someone else using it?
The modem is reporting that through the ethernet interface over 2.4 GB were downloaded and over 1.3 GB was uploaded in the last 16 hours. Since most of that was overnight, I'm wondering what was left running and connected to the modem.
Why is there so much traffic through the modem?
Why is it reporting an average upload rate of about 43 kiloBYTES per second (about 344 kbps) right now? and an average download rate of 83 kiloBYTES per second (644 kbps)? That's more then enough to effect your latency...
P.S. It seems like the router is installed again, because you're getting unanswered hops AFTER your IP address is traced to and the modem reported losing it's ethernet connection for a few seconds earlier today.
--
Don't mind me, I'm just trying to help...
| |
| | | | | | | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal | Re: TraceRoute Now the modem has uploaded 1.7 GB in a little over 18 hours.
--
Don't mind me, I'm just trying to help...
| |
| | | | | | | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 19th, @12:57PM
| Re: TraceRoute Ok... what happened?
At about 9:54am the data flow dropped dramatically and your latency is better.
The modem wasn't reset, nor is the modem indicating the ethernet connection was dropped.
Currently the modem shows 18 hours 41 minutes uptime and 1.75 GB uploaded.
With 16 KB/s average upload rate, 3 KB/s average download rate over the last couple minutes...
--
Don't mind me, I'm just trying to help...
| |
| | | | | | | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 19th, @01:14PM
| Re: TraceRoute traceroute to 76.176.20.108 (76.176.20.108), 64 hops max, 44 byte packets
1 i0.chi75.adelphiacom.net (66.109.10.17) 0.575 ms 0.426 ms 0.361 ms
2 ge-1-2-0.a0.chi75.twc-core.net (66.109.3.17) 0.435 ms 0.362 ms 0.321 ms
3 ae-0-0.c1.chi75.twc-core.net (66.109.3.5) 0.347 ms 0.358 ms 0.315 ms
4 as-1-0.c1.dfw91.twc-core.net (66.109.0.66) 25.665 ms 25.668 ms 25.614 ms
5 ge-7-1-0.c0.dfw91.twc-core.net (66.109.0.225) 25.652 ms 25.659 ms 25.642 ms
6 66.109.3.85 (66.109.3.85) 61.492 ms 61.485 ms 61.481 ms
7 ge-7-1-0.c0.lax91.twc-core.net (66.109.3.161) 61.627 ms 61.606 ms 61.585 ms
8 66.109.3.134 (66.109.3.134) 69.901 ms 61.915 ms 61.835 ms
9 tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) 67.937 ms 67.945 ms 67.914 ms
10 76.167.9.193 (76.167.9.193) 69.312 ms 69.327 ms 69.372 ms
11 gig3-21.ontrca1-rtr1.socal.rr.com (76.167.2.51) 72.171 ms 75.803 ms 72.122 ms
12 cpe-76-176-0-9.san.rr.com (76.176.0.9) 76.963 ms 73.286 ms 76.781 ms
13 10.125.64.1 (10.125.64.1) 74.619 ms 73.907 ms 74.515 ms
14 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) 84.151 ms 82.435 ms 85.432 ms
15 * *
WHAT EVER IS PRODUCING THE UPLOAD TRAFFIC THROUGH YOUR MODEM IS CAUSING YOUR LATENCY PROBLEMS.
The traffic increases and latency increases are directly related.
My GUESS would be a P2P application considering the traffic patterns...
--
Don't mind me, I'm just trying to help...
| |
| | | | | | | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal | Re: TraceRoute The modem just lost the ethernet connection for a few seconds...
--
Don't mind me, I'm just trying to help...
| |
| | | | | | | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 19th, @01:27PM
| Re: TraceRoute I'm done for now. I'll check back in a couple of hours.
P.S. the upload usage on the modem is spiking again as is your latency...
traceroute to 76.176.20.108 (76.176.20.108), 64 hops max, 44 byte packets
1 i0.chi75.adelphiacom.net (66.109.10.17) 0.652 ms 0.451 ms 0.369 ms
2 ge-1-2-0.a0.chi75.twc-core.net (66.109.3.17) 0.442 ms 0.366 ms 0.340 ms
3 ae-0-0.c1.chi75.twc-core.net (66.109.3.5) 0.373 ms 0.352 ms 0.324 ms
4 as-1-0.c1.dfw91.twc-core.net (66.109.0.66) 25.654 ms 25.648 ms 26.800 ms
5 ge-7-1-0.c0.dfw91.twc-core.net (66.109.0.225) 25.662 ms 25.660 ms 25.642 ms
6 66.109.3.85 (66.109.3.85) 61.683 ms 61.499 ms 61.498 ms
7 ge-7-1-0.c0.lax91.twc-core.net (66.109.3.161) 61.660 ms 61.622 ms 61.605 ms
8 66.109.3.134 (66.109.3.134) 61.884 ms 61.844 ms 61.844 ms
9 tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) 67.976 ms 67.983 ms 67.951 ms
10 76.167.9.193 (76.167.9.193) 69.306 ms 68.893 ms 69.422 ms
11 gig3-21.ontrca1-rtr1.socal.rr.com (76.167.2.51) 71.719 ms 75.569 ms 71.826 ms
12 cpe-76-176-0-9.san.rr.com (76.176.0.9) 76.666 ms 72.975 ms 76.756 ms
13 10.125.64.1 (10.125.64.1) 73.840 ms 74.294 ms 74.119 ms
14 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) 86.273 ms 85.619 ms 450.617 ms
15 * * *
--
Don't mind me, I'm just trying to help...
| |
| | | | | | | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 19th, @03:35PM
| Re: TraceRoute
Amazing... latency dropped in the last 3 hours. Read on to find out why... |
In other words, the upload rate has dramatically slowed in the last 3 hours. I bet your overall latency has improved, although some spikes will still be occuring, but nothing like the sustained high latency that occured overnight and this morning.
Uploading dropped to almost 0 within the last 5 minutes or so. Latency should be good.
PING 76.176.20.108 (76.176.20.108): 56 data bytes
64 bytes from 76.176.20.108: icmp_seq=0 ttl=117 time=34.235 ms
64 bytes from 76.176.20.108: icmp_seq=1 ttl=117 time=29.409 ms
64 bytes from 76.176.20.108: icmp_seq=2 ttl=117 time=31.159 ms
64 bytes from 76.176.20.108: icmp_seq=3 ttl=117 time=31.397 ms
64 bytes from 76.176.20.108: icmp_seq=4 ttl=117 time=31.436 ms
64 bytes from 76.176.20.108: icmp_seq=5 ttl=117 time=30.702 ms
^X64 bytes from 76.176.20.108: icmp_seq=6 ttl=117 time=32.852 ms
^C
--- 76.176.20.108 ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max/stddev = 29.409/31.599/34.235/1.433 ms
traceroute to 76.176.20.108 (76.176.20.108), 64 hops max, 44 byte packets
1 i0.chi75.adelphiacom.net (66.109.10.17) 0.536 ms 0.395 ms 0.351 ms
2 ge-1-2-0.a0.chi75.twc-core.net (66.109.3.17) 0.382 ms 0.370 ms 0.317 ms
3 ae-0-0.c1.chi75.twc-core.net (66.109.3.5) 0.337 ms 0.337 ms 0.309 ms
4 as-1-0.c1.dfw91.twc-core.net (66.109.0.66) 25.711 ms 25.615 ms 25.623 ms
5 ge-7-1-0.c0.dfw91.twc-core.net (66.109.0.225) 25.652 ms 25.659 ms 25.651 ms
6 66.109.3.85 (66.109.3.85) 61.512 ms 61.511 ms 61.491 ms
7 ge-7-1-0.c0.lax91.twc-core.net (66.109.3.161) 61.628 ms 61.628 ms 61.624 ms
8 66.109.3.134 (66.109.3.134) 61.921 ms 66.349 ms 61.916 ms
9 tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) 67.994 ms 68.033 ms 68.670 ms
10 76.167.9.193 (76.167.9.193) 69.224 ms 69.453 ms 69.612 ms
11 gig3-21.ontrca1-rtr1.socal.rr.com (76.167.2.51) 75.727 ms 72.179 ms 75.916 ms
12 cpe-76-176-0-9.san.rr.com (76.176.0.9) 76.793 ms 77.316 ms 73.463 ms
13 10.125.64.1 (10.125.64.1) 74.315 ms 74.669 ms 74.910 ms
14 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) 84.042 ms 86.064 ms 82.520 ms
15 *
Looks good. | |
| | | | | | | | | |
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
| Re: TraceRoute
Each grey vertical line is 1 hour of time. |
6 hours with low upload rates = 6 hours with low latency.
--
Don't mind me, I'm just trying to help...
| |
|
|
(139)
(108)
(44)
Re: Bigger picture
