RamsteinUSA
join:2007-02-15
Vista, CA
 ·RoadRunner Cable
|  reply to RamsteinUSA
Re: TraceRoute
The Roadrunner Network is a huge freaking Mess! all this testing and taking different measurements did nothing to help! RoadRunner is in total MeltDown!
It is Horrible !
Maybe my Review will help these incompetent managers at RR see that they can't blame the customers connectors, routers, and computers for RoadRunner's total incompetence.!
Of Course everytime I talk to RR they say they never ever look at what customers say online at websites, and al these measurements are never taken seriously or looked at by RoadRunner. They only look at a power meter and they ping it.. If the ping clears up while the techh is at the site of the work order, and the Internet works, they leave and close the work order!
the network never gets fixed!
 |
|
RamsteinUSA
join:2007-02-15
Vista, CA
·RoadRunner Cable
|
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
|
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
| 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 | 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
| 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
| 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 | 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
| 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
| 
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
| 
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...
|
|
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
| 27 hours up, 1.82 GB uploaded.
Show Level 3 (Los Angeles, CA) Ping to 76.176.20.108
icmp_seq=0 time=24 ms
icmp_seq=1 time=20 ms
icmp_seq=2 time=24 ms
icmp_seq=3 time=20 ms
icmp_seq=4 time=20 ms
icmp_seq=5 time=20 ms
icmp_seq=6 time=20 ms
icmp_seq=7 time=24 ms
icmp_seq=8 time=20 ms
icmp_seq=9 time=32 ms
---- 76.176.20.108 statistics ----
10 packets transmitted, 10 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 20/22.4/20/32/1.697/3.666 ms
P.S. all of that traffic is through the ethernet port. The USB port shows no traffic since it's last restart.
--
Don't mind me, I'm just trying to help...
|
|
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
| 
Pings have been mostly steady since the uploading stopped... |
About 12 hours of low latency...
--
Don't mind me, I'm just trying to help...
|
|
MacLeech
The one and only
Premium,MVM
join:2001-07-14
SoCal
edit:
May 20th, @09:19AM
| RamsteinUSA,
38 hours, 1.92 GB uploaded
19 hours of low latency:
Show Level 3 (Los Angeles, CA) Ping to 76.176.20.108
icmp_seq=0 time=20 ms
icmp_seq=1 time=24 ms
icmp_seq=2 time=20 ms
icmp_seq=3 time=20 ms
icmp_seq=4 time=20 ms
icmp_seq=5 time=24 ms
icmp_seq=6 time=20 ms
icmp_seq=7 time=20 ms
icmp_seq=8 time=20 ms
icmp_seq=9 time=20 ms
---- 76.176.20.108 statistics ----
10 packets transmitted, 10 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 20/20.8/20/24/1.131/1.6 ms
Show Level 3 (San Diego, CA) Traceroute to 76.176.20.108
1 so-6-0-0.mp1.SanDiego1.Level3.net (4.68.112.129) 36 msec 40 msec 0 msec
2 as-2-0.bbr1.LosAngeles1.Level3.net (64.159.1.30) 4 msec 4 msec 4 msec
3 ae-22-56.car2.LosAngeles1.Level3.net (4.68.102.173) 4 msec
ae-12-51.car2.LosAngeles1.Level3.net (4.68.102.13) 4 msec
ae-22-52.car2.LosAngeles1.Level3.net (4.68.102.45) 4 msec
4 ROADRUNNER.car2.LosAngeles1.Level3.net (4.71.36.74) 4 msec
ROADRUNNER.car2.LosAngeles1.Level3.net (4.78.195.190) 4 msec 12 msec
5 tge10-2.ontrca1-swt1.socal.rr.com (76.167.2.77) [AS20001 {ROADRUNNER-WEST}] 8 msec 8 msec 12 msec
6 76.167.9.193 [AS20001 {ROADRUNNER-WEST}] 12 msec 8 msec 12 msec
7 gig3-21.ontrca1-rtr1.socal.rr.com (76.167.2.51) [AS20001 {ROADRUNNER-WEST}] 16 msec 12 msec 44 msec
8 cpe-76-176-0-9.san.rr.com (76.176.0.9) [AS20001 {ROADRUNNER-WEST}] 40 msec 16 msec 12 msec
9 10.125.64.1 16 msec 16 msec 16 msec
10 cpe-76-176-20-108.san.res.rr.com (76.176.20.108) [AS20001 {ROADRUNNER-WEST}] 24 msec 24 msec 20 msec
11 * * *
See the pattern?
No massive uploads, no massive latency.
Roadrunner's network wasn't the problem. It wasn't in massive meltdown and Roadrunner did nothing to fix the problem. The problem was on your end.
--
Don't mind me, I'm just trying to help...
|
|
