Jump to content
Sign in to follow this  
westchaseman

Major connection issues RoadRunner ATDN.NET

Recommended Posts

Hello,

We share data with a vendor who uses RoadRunner.  We do not use RR and have been experiencing extremely poor connections and/or disconnects for more than a week due to that fact.  Yet, when we made the same connection using an alternate computer, through RR, we did not have any of these issues.

We did some extensive testing and involved our ISP in those tests.  In short, the real issue proved to be the lack of stable connectivity between ATDN.NET and the rest of the internet.

We ran multiple tests originating from various providers; the results of which are posted below.  The only time we saw a better connection was when we used a local Road Runner connection to our customer who is on Road Runner.  Obviously, we shouldn't have to be on RR to connect with them.

Test from Road Runner Tampa FL

Connection Speed:  5Mb / 384Kb

Tracing route to rrcs-24-172-209-131.central.biz.rr.com [24.172.209.131]

over a maximum of 30 hops:

  1    1 ms    1 ms    1 ms  192.168.10.1

  2    6 ms    7 ms    7 ms  10.125.112.1

  3    8 ms    9 ms    10 ms  653215hfc01.tampabay.res.rr.com [65.32.15.1]

  4    10 ms    8 ms    19 ms  pos6-0-OC-192.tampflerl-rtr4.tampabay.rr.com [65

.32.8.137]

  5    10 ms    11 ms    10 ms  pop2-tby-P3-0.atdn.net [66.185.132.1]

  6    9 ms    9 ms    9 ms  bb2-tby-P0-3.atdn.net [66.185.138.210]

  7    29 ms    24 ms    24 ms  bb1-atm-P2-0.atdn.net [66.185.152.186]

  8    30 ms    28 ms    34 ms  bb1-cha-P6-0.atdn.net [66.185.152.183]

  9    40 ms    39 ms    39 ms  bb1-vie-P12-0.atdn.net [66.185.152.29]

10    40 ms    38 ms    40 ms  bb2-vie-P3-0.atdn.net [66.185.152.207]

11    40 ms    44 ms    52 ms  bb2-ash-P9-0.atdn.net [66.185.152.100]

12    60 ms    58 ms    58 ms  bb2-cin-P3-0.atdn.net [66.185.153.61]

13    61 ms    61 ms    65 ms  pop1-cin-P1-0.atdn.net [66.185.133.3]

14    63 ms    63 ms    61 ms  RR-Cincinnati.atdn.net [66.185.133.10]

15    74 ms    70 ms    69 ms  pos9-0.ncntoh1-rtr2.neo.rr.com [65.25.128.250]

16    70 ms    75 ms    71 ms  srp1-0.polkoh1-rtr2.neo.rr.com [24.164.96.104]

17    64 ms    70 ms    65 ms  srp1-0.mnfdoh3-ubr1.neo.rr.com [24.164.96.71]

18  125 ms  144 ms  112 ms  rrcs-24-172-209-130.central.biz.rr.com [24.172.2

09.130]

19    *        *    ^C

Max throughput we were able to pull:  1.7 Mb/s

-------------------------------------------------------------

Test from Level 3   

Connection Speed:  100 Mb/100 Mb

  1  <10 ms  <10 ms  <10 ms  core-router.tbdsl.com [198.31.248.1]

  2    1 ms    1 ms  <10 ms  63.135.224.33

  3    1 ms    1 ms    1 ms  64.156.25.77

  4    1 ms  <10 ms    1 ms  64.156.25.73

  5    1 ms    1 ms    3 ms  ge-6-2.car4.Tampa1.Level3.net [63.208.24.1]

  6    1 ms    1 ms    1 ms  ae-1-55.mp1.Tampa1.Level3.net [4.68.104.129]

  7    32 ms    32 ms    32 ms  as-1-0.bbr1.Washington1.Level3.net [4.68.128.201

]

  8    32 ms    50 ms    32 ms  so-6-0-0.edge2.Washington1.Level3.net [64.159.3.

62]

  9    33 ms    32 ms    32 ms  pop2-ash-P9-0.atdn.net [66.185.140.253]

10    32 ms    32 ms    32 ms  bb2-ash-P1-0.atdn.net [66.185.139.210]

11    51 ms    51 ms    50 ms  bb2-cin-P3-0.atdn.net [66.185.153.61]

12    50 ms    50 ms    50 ms  pop1-cin-P1-0.atdn.net [66.185.133.3]

13    54 ms    54 ms    54 ms  RR-Cincinnati.atdn.net [66.185.133.10]

14    63 ms    62 ms    62 ms  pos9-0.ncntoh1-rtr2.neo.rr.com [65.25.128.250]

15    56 ms    54 ms    55 ms  srp1-0.polkoh1-rtr1.neo.rr.com [24.164.96.101]

16    56 ms    57 ms    56 ms  srp1-0.mnfdoh3-ubr1.neo.rr.com [24.164.96.71]

17    77 ms    69 ms    74 ms  rrcs-24-172-209-130.central.biz.rr.com [24.172.2

09.130]

Max throughput we were able to pull:  100 Kb/s

----------------------------

Test from XO

Connection Speed    4.5Mb / 4.5Mb

Tracing route to rrcs-24-172-209-131.central.biz.rr.com [24.172.209.131]

over a maximum of 30 hops:

  1    1 ms  <10 ms  <10 ms  192.168.2.1

  2    1 ms    1 ms    1 ms  67.109.82.1.ptr.us.xo.net [67.109.82.1]

  3    11 ms    10 ms    10 ms  65.106.144.57.ptr.us.xo.net [65.106.144.57]

  4    12 ms    10 ms    9 ms  p6-2-0.mar2.cleveland-oh.us.xo.net [207.88.87.85

]

  5    23 ms    17 ms    16 ms  p5-1-0-0.rar2.washington-dc.us.xo.net [65.106.3.

161]

  6    19 ms    17 ms    17 ms  p1-0.ir1.ashburn-va.us.xo.net [65.106.3.138]

  7    17 ms    17 ms    17 ms  pop1-ash-g2-2-3.atdn.net [66.185.144.145]

  8    23 ms    17 ms    25 ms  bb2-ash-p0-0.atdn.net [66.185.144.194]

  9    38 ms    37 ms    46 ms  bb2-cin-p3-0.atdn.net [66.185.153.61]

10    37 ms    37 ms    39 ms  pop1-cin-p1-0.atdn.net [66.185.133.3]

11    45 ms    45 ms    45 ms  rr-cincinnati.atdn.net [66.185.133.6]

12    53 ms    53 ms    53 ms  pos9-0.ncntoh1-rtr2.neo.rr.com [65.25.128.250]

13    68 ms    58 ms    54 ms  srp1-0.polkoh1-rtr1.neo.rr.com [24.164.96.101]

14    47 ms    46 ms    46 ms  srp1-0.mnfdoh3-ubr1.neo.rr.com [24.164.96.71]

15    83 ms    78 ms    78 ms  rrcs-24-172-209-130.central.biz.rr.com [24.172.2

09.130]

Max throughput we were able to pull:  170 Kb/s

----------------------------

Anyone else experiencing this with RR?

####

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...