dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1399
share rss forum feed

peteboston

join:1999-11-10
Wakefield, MA

4 edits

[Speed] Massachusetts - Persistent slow perf. to locations

Dear RCN,

I have been a Massachusetts RCN customer for 7 years and I have suffered from a 100% reproducible performance problem since day one that I hope someone will finally take the time to troubleshoot and resolve since I am confident that I am not the only one impacted by this and it's making RCN's throughput suffer massively. I have opened up various cases over the years (none recently) and nobody has ever taken enough interest to solve this.

The quick summary is that I receive my rated speed 25/2 to NYC and WDC, but to many other internet locations, performance drops off significantly. It doesn't matter what time of day I do the test or what computer I use. I have tested with Mac and Windows devices plugged directly in with a Cat 6 cable to the modem, so I have taken my internal network out of the picture of being a possible cause for the performance dropoff. I am confident that the problem(s) are either on RCN's network or with RCNs peer(s).

Since I communicate with many sites on the west coast, the performance dropoff is very frustrating. Can someone at RCN please figure out if this is not on your network, what is wrong with one of your peers that is resulting in this poor performance?

Seems clear from the results below that there is definitely at least one problem on RCN's network, but it's likely not the only problem as only some of the sites I am trying to access appear to route through your IL connection (see download performance results below)

I have done a head-to-head comparison with a local FIOS connection and the same computers and receive full speed to these same speakeasy.net/speedtest locations. FIOS obviously takes a completely different route to get to these locations, but the point is that they get their rated speeds without dropoff.

I have considered increasing my speed w/ RCN, but there's no point if I can't even get the speeds I am supposed to get now.

Thanks in advance for your time investigating this persistent problem.

Encoded Mac: 3ff67fe2db94d5c34592349b0c9c3c3d84b292f8

Speedtest Download Throughput Results:(speakeasy.net/speedtest)
(Note, these performance results are reproducible without speedtest, so it is not just a speedtest or speakeasy/megapath problem)

NYC 25.46Mb/s (New York, NY) 216.254.95.15 speedtest1.nyc1.speakeasy.net

WDC 23.39Mb/s (Washington, DC) 66.92.159.15 speedtest1.wdc1.speakeasy.net

ATL 15.17Mb/s (Atlanta, GA) 216.27.175.15 speedtest1.atl1.speakeasy.net

CHI 14.92Mb/s (Chicago, IL) 64.81.159.15 speedtest1.chi1.speakeasy.net

DAL 8.99Mb/s (Dallas, TX) 64.81.127.15 speedtest1.dfw1.speakeasy.net

LAX 7.31Mb/s (Los Angeles, CA) 64.81.45.15 speedtest1.lax.speakeasy.net

SFO 7.73Mb/s (San Francisco, CA) 64.81.79.15 speedtest1.sfo1.speakeasy.net

SEA 6.22Mb/s (Seattle, WA) 66.93.87.15 speedtest1.sea.speakeasy.net

Baseline to RCN Speedtest Servers

RCN MA Speedtest 26.39Mb/s 209.6.160.31 ma.speedtest.rcn.net

RCN IL Speedtest 12.62Mb/s & 16.45Mb/s 216.80.19.62 il.speedtest.rcn.net

RCN PA Speedtest 26.42Mb/s 208.59.202.70 pa.speedtest.rcn.net


peteboston

join:1999-11-10
Wakefield, MA

Dear RCN,

I know your team is extremely busy and you monitor DSLreports out of the kindness of your hearts in your spare time. I would greatly appreciate an acknowledgement of this problem so that you can start to come up with a plan to correct it.


negativeduck
Premium,VIP
join:2002-02-14
Centreville, VA
kudos:1

1 recommendation

I'm waiting on the head of the backbone guys to get back. Ofcourse as you know and was explained when you were working with Scott RCN doesn't own the internet as hole. While other providers who'm you mention may have private transit and other agreements they may have different connectivity to the other side of the country and take different paths from both TO and FROM that remote site. RCN does not maintain dedicated connectivity to the opposite side of the country.

I recall the only place we were able to get symmetrical tests was from your remote office and we saw a difference in paths through an un-related third parties. Your office couldn't change your outbound. And while there was something strange it was //in the middle// a black hole where we had no direct relationship.

As you know it's increasingly complicated to work around problems 3 companies removed from our direct arrangements. Likewise it is possible with some providers you may get better connectivity and throughput into Japan than you will through us.

While I understand your concerns and as a RCN customer you want us to resolve this. But do you have any information from the admins of each of these test locations providing their route and path info between the providers in your house? Again I must stress the path you take to get TO the remote site may or very likely is NOT the same path they take to get back to us.

But I won't be really able to offer any more information till I get a chance to talk to the head of the backbone routing.
--
Bryan Laird
RCN Engineering


peteboston

join:1999-11-10
Wakefield, MA

Thanks Bryan. Glad to see that you're looking in to this. I am quite aware that RCN isn't responsible for every problem on the internet, unfortunately this one has a very big impact on us wonderful and loyal RCN customers and really seems very specific to either RCN's network or something going on at RCN's peering location(s).

I will do everything possible to get you guys data on a few return paths, unfortunately I don't have access to every remote destination on the internet to get you a return path traceroute. There are still some old traceroute mirror servers out there, so let me see if I can use any of them to get some return path information to help you guys isolate this.

You guys should be able to see these performance problems as well, as they are not isolated to me.

In the end, my goal is to make sure that when we're done, RCN customers receive the best performance possible for their connectivity.

Best Regards,
-pete


peteboston

join:1999-11-10
Wakefield, MA

Let's start at home before worrying about the rest of the internet (next). Can you ask the backbone engineering team to look at what is wrong on the RCN backbone between MA & IL first? While this is only impacting a portion of the sites on the internet, some are definitely going through your IL site and will obviously be impacted by this.

As I pasted above and can be easily reproduced to RCN's own speed test server, there is no way to get max speed to RCN IL from RCN MA, so this should be a good place to start troubleshooting since I believe there are numerous problems to resolve and this is one of many.

Outbound path:
tge0-0-0-0.core2.sbo.ma.rcn.net (207.172.15.130) 13.726 ms 13.748 ms
4 tge0-0-0-1.core1.chgo.il.rcn.net (207.172.19.231) 44.668 ms tge0-0-0-1.core2.chgo.il.rcn.net (207.172.19.233) 44.829 ms tge0-0-0-1.core1.chgo.il.rcn.net (207.172.19.231) 44.720 ms
5 tge2-3.aggr1.chgo.il.rcn.net (207.172.15.213) 43.603 ms 44.680 ms 44.586 ms
6 il.speedtest.rcn.net (216.80.19.62) 44.663 ms 37.978 ms 35.791 ms

Last speedtest: 18.64Mb/s, 17.83Mb/s, 18.74Mb/s (this is actually better than the other day, but still far below what I get to MA)

RCN MA: 27.6Mb/s
RCN PA: 24.07Mb/s


negativeduck
Premium,VIP
join:2002-02-14
Centreville, VA
kudos:1
reply to peteboston

So, one thing did you notice that your throughput is directly tied to your Latency. This is usually indicative of a window (tcp) problem on either the sender or the receiver side. Actually fairly common for throughput to start to take a stellar dive as latency increases more and more. IE 56ms to Dallas yea your likely butting up against that and depending on the range / your stacks ability to change can cause an impact. Yes ICMP being bottom of the barrel may not be 100% accurate of the RTT your seeing in tcp transmissions but then again it might be and without direct knowledge of all links it's hard to say. Likewise if you ran the same test UDP you would probably get full speed.

(NOTE: The Windows on the speedtests (outs) are tweaked for serving their local markets at the best, they are NOT tweaked for serving all locations)

So Backbone guys came back list of questions:
1. What are his target sites - i.e. the ones on the west coast that he actually cares about, not the speed test sites?
2. Traceroutes from his VZ connection to the speedtest servers.
3. What time of day are the problems, or are the problems particularly acute? Or is it equally good/bad all day?
4. What does he get on the 'Speed Test Plus' test found on most speedtest.net sites for packet loss, latency, and jitter?
5. Ditto as above but on Verizon

This was followed with:
I could make a routing change to avoid Megapath (which runs speedtest.net) and go level3-megapath, but this seems crazy to favor an indirect over a direct connection and the speedtest sites are proxies for the sites he actually cares about so improving them artificially won't make him happy.
--
Bryan Laird
RCN Engineering


peteboston

join:1999-11-10
Wakefield, MA

4 edits
reply to peteboston

Performance is good all day on VZ and bad all day and night on RCN outside of the few sites that have decent performance.

Here are the VZ Stats from the same exact computer to the same exact servers, I will send traceroutes in an hour or so.

[Updated on 8/16 to include RCN comparison on right]

FIOS 25/25---------------------- -- RCN 25/2
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ -- \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
SEA 27.26Mb/s 111ms 19 hops -- RCN 6.22Mb/s 107ms 11 hops
SFO 27.77Mb/s 104ms 23 hops -- RCN 7.73Mb/s 88ms 10 hops
LAX 30.09Mb/s 100ms 16 hops -- RCN 7.31Mb/s 91ms 9 hops
DAL 30.98Mb/s 63ms 16 hops -- RCN 8.99Mb/s 60ms 11 hops
CHI 30.58Mb/s 64ms 11 hops -- RCN 14.92Mb/s 37ms 6 hops
ATL 30.13Mb/s 79ms 17 hops -- RCN 15.17Mb/s 34ms 9 hops
NYC 30.23Mb/s 63ms 13 hops -- RCN 25.46Mb/s 16ms 6 hops
WDC 30.87Mb/s 62ms 12 hops -- RCN 23.39Mb/s 21ms 9 hops


peteboston

join:1999-11-10
Wakefield, MA

1 edit

Here are the VZ FIOS Traceroutes to the same sites

NY:
3 g0-14-1-4.bstnma-lcr-22.verizon-gni.net (130.81.59.166) 8.147 ms 15.290 ms 7.599 ms
4 so-5-0-0-0.bos-bb-rtr2.verizon-gni.net (14 ae3-0.lsancagb-mxc1.bb.megapath.net (155.229.57.97) 98.462 ms 99.563 ms 105.436 ms
15 ge-2-0-0-0.c00.law.bb.megapath.net (155.229.70.201) 160.088 ms 101.542 ms 101.196 ms
16 *) 6.852 ms 8.528 ms 6.864 ms
5 so-7-2-0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.19.66) 27.173 ms 24.447 ms 20.054 ms
6 0.xe-3-1-0.br3.nyc4.alter.net (152.63.2.81) 17.759 ms 21.094 ms 18.621 ms
7 te-7-3-0.edge2.newyork2.level3.net (4.68.111.137) 60.084 ms 59.607 ms 60.040 ms
8 vlan52.ebr2.newyork2.level3.net (4.69.138.254) 62.092 ms 61.822 ms 62.533 ms
9 ae-4-4.ebr1.newyork1.level3.net (4.69.141.17) 60.319 ms 59.726 ms 62.047 ms
10 ae-92-92.csw4.newyork1.level3.net (4.69.148.46) 62.837 ms 71.723 ms
ae-62-62.csw1.newyork1.level3.net (4.69.148.34) 69.257 ms
11 ae-33-80.car3.newyork1.level3.net (4.69.155.133) 64.450 ms
ae-23-70.car3.newyork1.level3.net (4.69.155.69) 79.741 ms
ae-43-90.car3.newyork1.level3.net (4.69.155.197) 58.907 ms
12 unknown.level3.net (63.209.170.234) 56.613 ms 59.667 ms 56.715 ms
13 * * *

WDC:
3 g0-14-1-3.bstnma-lcr-22.verizon-gni.net (130.81.190.230) 7.244 ms 6.939 ms 7.617 ms
4 so-5-0-0-0.bos-bb-rtr2.verizon-gni.net (130.81.151.220) 6.925 ms 11.350 ms 12.729 ms
5 so-7-2-0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.19.66) 58.466 ms 47.044 ms 32.408 ms
6 0.xe-3-1-0.br3.nyc4.alter.net (152.63.2.81) 17.060 ms 17.533 ms 18.098 ms
7 te-7-3-0.edge2.newyork2.level3.net (4.68.111.137) 59.377 ms 59.516 ms 102.252 ms
8 vlan51.ebr1.newyork2.level3.net (4.69.138.222) 59.417 ms 64.446 ms 59.991 ms
9 ae-3-3.ebr2.washington1.level3.net (4.69.132.89) 60.051 ms 59.448 ms 59.649 ms
10 ae-82-82.csw3.washington1.level3.net (4.69.134.154) 62.113 ms
ae-72-72.csw2.washington1.level3.net (4.69.134.150) 67.100 ms 59.315 ms
11 ae-21-70.car1.washington1.level3.net (4.69.149.67) 67.785 ms
ae-31-80.car1.washington1.level3.net (4.69.149.131) 116.340 ms
ae-21-70.car1.washington1.level3.net (4.69.149.67) 99.125 ms
12 63.210.41.194 (63.210.41.194) 59.822 ms 61.562 ms 59.862 ms

ATL:
3 g0-14-1-4.bstnma-lcr-22.verizon-gni.net (130.81.59.166) 10.866 ms 8.124 ms 7.132 ms
4 so-5-0-0-0.bos-bb-rtr2.verizon-gni.net (130.81.151.220) 7.277 ms 7.424 ms 7.311 ms
5 so-7-2-0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.19.66) 14.712 ms 17.176 ms 17.346 ms
6 0.xe-3-1-0.br3.nyc4.alter.net (152.63.2.81) 16.834 ms 16.772 ms 17.037 ms
7 te-7-3-0.edge2.newyork2.level3.net (4.68.111.137) 59.979 ms 77.578 ms 135.964 ms
8 vlan51.ebr1.newyork2.level3.net (4.69.138.222) 73.341 ms 62.389 ms 60.256 ms
9 ae-3-3.ebr2.washington1.level3.net (4.69.132.89) 62.748 ms 59.699 ms 64.702 ms
10 ae-72-72.csw2.washington1.level3.net (4.69.134.150) 60.052 ms 69.112 ms
ae-82-82.csw3.washington1.level3.net (4.69.134.154) 65.671 ms
11 ae-22-70.car2.washington1.level3.net (4.69.149.68) 59.658 ms
ae-12-60.car2.washington1.level3.net (4.69.149.4) 61.599 ms
ae-42-90.car2.washington1.level3.net (4.69.149.196) 62.068 ms
12 ge1-1.bbsr1.iad.megapath.net (166.90.148.2) 59.436 ms 59.389 ms 59.591 ms
13 66.80.131.46 (66.80.131.46) 77.530 ms 79.088 ms 77.021 ms
14 ge-3-0-0-0.c01.ash.bb.megapath.net (155.229.123.245) 129.224 ms 111.861 ms 97.557 ms
15 ae8-0.asbnvacz-mxc2.bb.megapath.net (155.229.101.149) 66.643 ms 64.473 ms 92.414 ms
16 ae1-0.atlngamq-mxc2.bb.megapath.net (155.229.57.154) 79.563 ms 79.483 ms 79.900 ms
17 ge-2-1-0-0.c00.atp.bb.megapath.net (155.229.101.194) 78.708 ms 77.185 ms 80.062 ms

CHI:
3 g0-14-1-3.bstnma-lcr-22.verizon-gni.net (130.81.190.230) 8.089 ms 6.875 ms 7.417 ms
4 so-5-0-0-0.bos-bb-rtr2.verizon-gni.net (130.81.151.220) 7.571 ms 7.270 ms 7.579 ms
5 so-7-2-0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.19.66) 36.701 ms 16.613 ms 15.450 ms
6 0.xe-3-1-0.br3.nyc4.alter.net (152.63.2.81) 17.079 ms 17.588 ms 17.725 ms
7 te-7-3-0.edge2.newyork2.level3.net (4.68.111.137) 60.022 ms 59.606 ms 62.001 ms
8 vlan52.ebr2.newyork2.level3.net (4.69.138.254) 62.446 ms 69.479 ms 62.265 ms
9 ae-2-2.ebr1.chicago1.level3.net (4.69.132.65) 59.937 ms 61.534 ms 62.990 ms
10 ae-11-51.car1.chicago1.level3.net (4.69.138.3) 89.311 ms 219.613 ms 79.806 ms
11 covad.car1.chicago1.level3.net (166.90.73.82) 62.900 ms 64.340 ms 62.643 ms

DAL:
3 g0-14-1-3.bstnma-lcr-22.verizon-gni.net (130.81.190.230) 8.403 ms 8.323 ms 6.684 ms
4 so-5-0-0-0.bos-bb-rtr2.verizon-gni.net (130.81.151.220) 7.134 ms 8.166 ms 8.789 ms
5 so-7-2-0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.19.66) 50.203 ms 29.257 ms 14.676 ms
6 0.xe-3-1-0.br3.nyc4.alter.net (152.63.2.81) 17.227 ms 18.170 ms 17.273 ms
7 te-7-3-0.edge2.newyork2.level3.net (4.68.111.137) 59.891 ms 59.179 ms 62.488 ms
8 vlan51.ebr1.newyork2.level3.net (4.69.138.222) 60.896 ms 62.085 ms 67.227 ms
9 ae-3-3.ebr2.washington1.level3.net (4.69.132.89) 59.797 ms 59.719 ms 60.012 ms
10 ae-72-72.csw2.washington1.level3.net (4.69.134.150) 60.033 ms
ae-82-82.csw3.washington1.level3.net (4.69.134.154) 62.494 ms 62.250 ms
11 ae-91-91.ebr1.washington1.level3.net (4.69.134.141) 67.001 ms
ae-61-61.ebr1.washington1.level3.net (4.69.134.129) 72.605 ms
ae-91-91.ebr1.washington1.level3.net (4.69.134.141) 63.020 ms
12 ae-2-2.ebr3.atlanta2.level3.net (4.69.132.85) 60.074 ms 62.370 ms 60.011 ms
13 ae-7-7.ebr3.dallas1.level3.net (4.69.134.21) 61.857 ms 66.614 ms 62.550 ms
14 ae-83-83.csw3.dallas1.level3.net (4.69.151.157) 61.397 ms
ae-73-73.csw2.dallas1.level3.net (4.69.151.145) 63.449 ms 60.414 ms
15 ae-21-70.car1.dallas1.level3.net (4.69.145.67) 222.112 ms 186.806 ms 129.639 ms
16 covad.car1.dallas1.level3.net (4.78.221.134) 60.142 ms 59.057 ms 62.819 ms

LAX:
4 so-5-0-0-0.bos-bb-rtr2.verizon-gni.net (130.81.151.220) 8.142 ms 8.038 ms 5.967 ms
5 so-7-2-0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.19.66) 15.609 ms 14.473 ms 17.752 ms
6 0.xe-3-1-0.br3.nyc4.alter.net (152.63.2.81) 18.246 ms 18.126 ms 16.874 ms
7 te-7-3-0.edge2.newyork2.level3.net (4.68.111.137) 59.751 ms 61.977 ms 61.029 ms
8 vlan51.ebr1.newyork2.level3.net (4.69.138.222) 65.954 ms 70.344 ms 67.861 ms
9 ae-6-6.ebr2.newyork1.level3.net (4.69.141.21) 83.970 ms 103.075 ms
ae-4-4.ebr1.newyork1.level3.net (4.69.141.17) 56.311 ms
10 ae-61-61.csw1.newyork1.level3.net (4.69.134.66) 59.036 ms
ae-81-81.csw3.newyork1.level3.net (4.69.134.74) 64.753 ms 60.682 ms
11 ae-41-90.car1.newyork1.level3.net (4.69.155.195) 115.429 ms
ae-21-70.car1.newyork1.level3.net (4.69.155.67) 57.297 ms
ae-31-80.car1.newyork1.level3.net (4.69.155.131) 62.174 ms
12 ge2-2.bbsr1.nyc.megapath.net (209.246.126.2) 129.055 ms 96.970 ms 62.162 ms
13 ge-0-1-2-0.nycmny83-mxc1.bb.megapath.net (155.229.70.234) 60.306 ms 62.804 ms 63.981 ms
14 ae3-0.lsancagb-mxc1.bb.megapath.net (155.229.57.97) 98.462 ms 99.563 ms 105.436 ms
15 ge-2-0-0-0.c00.law.bb.megapath.net (155.229.70.201) 160.088 ms 101.542 ms 101.196 ms
16 *

SFO:
3 g0-14-1-3.bstnma-lcr-22.verizon-gni.net (130.81.190.230) 12.433 ms 15.111 ms 12.098 ms
4 so-5-0-0-0.bos-bb-rtr2.verizon-gni.net (130.81.151.220) 11.230 ms 7.001 ms 11.297 ms
5 ge-7-1-0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.19.33) 54.155 ms 21.938 ms 19.321 ms
6 0.xe-3-1-0.br3.nyc4.alter.net (152.63.2.81) 22.724 ms 19.882 ms 17.909 ms
7 te-7-3-0.edge2.newyork2.level3.net (4.68.111.137) 65.134 ms 61.784 ms 67.265 ms
8 vlan51.ebr1.newyork2.level3.net (4.69.138.222) 68.072 ms 72.625 ms 63.011 ms
9 ae-3-3.ebr2.washington1.level3.net (4.69.132.89) 64.053 ms 65.741 ms 64.838 ms
10 ae-62-62.csw1.washington1.level3.net (4.69.134.146) 69.302 ms 65.179 ms 79.851 ms
11 ae-41-90.car1.washington1.level3.net (4.69.149.195) 73.547 ms
ae-11-60.car1.washington1.level3.net (4.69.149.3) 64.871 ms 96.108 ms
12 63.210.41.194 (63.210.41.194) 69.553 ms 77.271 ms 76.626 ms
13 67.100.36.202-ge3.6-atln-osr2-atlanta.covad.com (67.100.36.202) 99.080 ms 104.061 ms 104.325 ms
14 67.100.37.2-ge5.1-atln-osr1-atlanta.covad.com (67.100.37.2) 128.404 ms 113.223 ms 103.724 ms
15 67.100.37.103-ge3.7-chcg-osr2-chicago.covad.com (67.100.37.103) 100.058 ms 101.846 ms 103.041 ms
16 67.100.36.16-ge3.4-dlla-osr1-dallas.covad.com (67.100.36.16) 101.426 ms 101.611 ms 102.259 ms
17 67.100.37.117-ge3.6-phnd-osr2-phoenix.covad.com (67.100.37.117) 99.614 ms 97.097 ms 97.456 ms
18 h-67-100-36-30.noclli.covad.net (67.100.36.30) 97.001 ms 96.816 ms 96.706 ms
19 67.100.36.220-ge3.6-lsan-osr2-los-angeles.covad.com (67.100.36.220) 104.071 ms 102.694 ms 102.073 ms
20 67.100.36.20-ge3.4-lsan-osr1-los-angeles.covad.com (67.100.36.20) 102.458 ms 102.234 ms 102.469 ms
21 67.100.36.121-ge3.6-snva-osr2-sunnyvale.covad.com (67.100.36.121) 104.623 ms 103.531 ms 102.037 ms
22 h-67-100-37-243.noclli.covad.net (67.100.37.243) 102.074 ms 98.916 ms 99.589 ms
23 0.ge-0-0-3.cr1.sfo1.speakeasy.net (74.211.163.1) 102.246 ms 123.863 ms 102.520 ms

SEA:
3 g0-14-1-3.bstnma-lcr-22.verizon-gni.net (130.81.190.230) 7.866 ms 6.815 ms 7.674 ms
4 so-5-0-0-0.bos-bb-rtr2.verizon-gni.net (130.81.151.220) 27.469 ms 9.354 ms 8.194 ms
5 so-7-2-0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.19.66) 19.730 ms 14.349 ms 12.389 ms
6 0.xe-3-1-0.br3.nyc4.alter.net (152.63.2.81) 17.069 ms 17.586 ms 69.725 ms
7 te-7-3-0.edge2.newyork2.level3.net (4.68.111.137) 60.007 ms 59.692 ms 62.787 ms
8 vlan51.ebr1.newyork2.level3.net (4.69.138.222) 59.971 ms 67.082 ms 60.006 ms
9 ae-3-3.ebr2.washington1.level3.net (4.69.132.89) 64.903 ms 64.582 ms 62.761 ms
10 ae-62-62.csw1.washington1.level3.net (4.69.134.146) 59.923 ms
ae-92-92.csw4.washington1.level3.net (4.69.134.158) 59.712 ms 62.313 ms
11 ae-12-60.car2.washington1.level3.net (4.69.149.4) 237.196 ms
ae-22-70.car2.washington1.level3.net (4.69.149.68) 219.690 ms 227.017 ms
12 ge1-1.bbsr1.iad.megapath.net (166.90.148.2) 60.201 ms 59.565 ms 62.756 ms
13 ae1-0.c00.ash.bb.megapath.net (155.229.57.162) 131.789 ms 151.358 ms 115.078 ms
14 ae8-0.asbnvacz-mxc1.bb.megapath.net (155.229.70.149) 62.757 ms 61.584 ms 62.749 ms
15 ae3-0.snvacaid-mxc1.bb.megapath.net (155.229.57.117) 87.649 ms 88.232 ms 88.867 ms
16 ae0-0.snvacaid-mxc2.bb.megapath.net (155.229.57.14) 89.034 ms 86.116 ms 87.024 ms
17 ge-2-1-0-0.c01.pao.bb.megapath.net (155.229.70.222) 87.691 ms 85.087 ms 85.790 ms
18 spk-mega.c01.pao.megapath.net (66.80.133.30) 87.424 ms 86.700 ms 84.874 ms
19 ge-0-0-0.605.cr1.sea1.speakeasy.net (69.17.87.33) 107.472 ms 106.733 ms 107.536 ms


peteboston

join:1999-11-10
Wakefield, MA
reply to negativeduck

o Backbone guys came back list of questions:
1. What are his target sites - i.e. the ones on the west coast that he actually cares about, not the speed test sites?

>> Feel free to write me a direct email for this information. The reality is, everything is equally slow, the speedtests are just the easiest way for me to show this in a manner where you can easily reproduce.

2. Traceroutes from his VZ connection to the speedtest servers.

>> Above.

3. What time of day are the problems, or are the problems particularly acute? Or is it equally good/bad all day?

>> Consistent performance problems w/ RCN - no time of day difference.

4. What does he get on the 'Speed Test Plus' test found on most speedtest.net sites for packet loss, latency, and jitter?

>> Will need to run this test, have not done so.

5. Ditto as above but on Verizon

>> Performance, latency and hops listed above for all of the same sites from VZ connection from same market.

>> The theory on latency doesn't make any sense given that VZ is sometimes 5-10ms greater to these West Coast sites, but there performance blows mine away.


peteboston

join:1999-11-10
Wakefield, MA
reply to peteboston

RCN 25/2 Massachusetts SpeedTest Plus Results
Start Time 8/16 9:40P ET
Stop Time 8/16 9:53P ET

City, Download, Upload, Packet Los, Latency, Jitter
NYC 24.95, 2.04, 0%, 15ms, 2ms
WDC 23.21, 2.06, 0%, 24ms, 2ms
CHI 14.55, 2.08, 0%, 40ms, 1ms
ATL 16.06, 2.08, 0%, 36ms, 1ms
DAL 10.49, 2.06, 0%, 79ms, 32ms
SEA 4.94, 2.03, 0%, 129ms, 36ms
SFO 6.78, 2.05, 0%, 92ms, 1ms
LAX 6.29, 2.06, 0%, 105ms, 20ms


peteboston

join:1999-11-10
Wakefield, MA
reply to peteboston

Please let me know if there is any more information your team needs for troubleshooting.


peteboston

join:1999-11-10
Wakefield, MA
reply to negativeduck

Bumping up again. Please let me know if you need more data to root cause what is going on regarding performance.


peteboston

join:1999-11-10
Wakefield, MA

Dear RCN,

I am really hopeful someone can help get this fixed. Please let me know if you need any more data from me.