Page 1 of 2 12 LastLast
Results 1 to 25 of 33
  1. #1
    Join Date
    Jul 2004
    Location
    New York, NY
    Posts
    2,181

    Peer 1 routing screwing the pooch?

    Can you guys post traceroutes to 69.25.118.70

    Everyday at night or early morning, the last hop goes crazy (216.xx.xx.xx) Peer 1 switch // router.

    Also, Peer 1 and their peering with cogent is creating problems as cogent is routing traffic any way they can to save cash.

    OR

    Could this be a capacity issue with Savvis. I've seen tons of savvis problems in the last 2 months.

    traceroute to www.steadfastnetworks.com (205.218.64.7), 30 hops max, 38 byte packets
    1 69.25.118.65 (69.25.118.65) 0.232 ms 0.136 ms 0.127 ms
    2 216.187.123.26 (216.187.123.26) 47.207 ms 64.854 ms 54.538 ms
    3 aer1-gigabitethernet2-3.NewYork.savvis.net (206.24.195.133) 41.320 ms 25.766 ms 9.717 ms
    4 dcr3-ae2.NewYork.savvis.net (208.174.228.9) 10.074 ms 25.719 ms 36.672 ms
    5 bcs1-so-1-1-0-500.NewYork.savvis.net (204.70.192.186) 46.874 ms bcs1-so-3-0-0-500.NewYork.savvis.net (204.70.192.194) 51.280 ms bcs2-so-3-0-0-500.NewYork.savvis.net (204.70.192.202) 4.351 ms
    6 dcr2-so-3-0-0.Chicago.savvis.net (204.70.192.101) 170.505 ms dcr1-so-1-2-0.Chicago.savvis.net (204.70.192.105) 56.419 ms dcr2-so-3-0-0.Chicago.savvis.net (204.70.192.101) 86.945 ms
    7 dcr2-so-5-0-0.Chicago.savvis.net (204.70.192.46) 52.309 ms bpr1-so-0-0-0.ChicagoEquinix.savvis.net (208.175.10.238) 74.891 ms *
    8 aer1-po10.ChicagoEquinix.savvis.net (208.175.9.133) 28.492 ms bpr2-so-3-0-0.ChicagoEquinix.savvis.net (208.175.10.254) 23.715 ms aer1-po10.ChicagoEquinix.savvis.net (208.175.9.133) 24.477 ms
    9 aer1-po20.ChicagoEquinix.savvis.net (208.175.9.137) 28.808 ms steadfast-networks.ChicagoEquinix.savvis.net (208.174.226.26) 23.970 ms aer1-po10.ChicagoEquinix.savvis.net (208.175.9.133) 24.593 ms
    10 63.208.72.110 (63.208.72.110) 23.581 ms steadfast-networks.ChicagoEquinix.savvis.net (208.174.226.26) 25.222 ms 26.033 ms
    11 * * 63.208.72.110 (63.208.72.110) 91.922 ms


    The above is a trace to www.steadfastnetworks.com

    Target Name: N/A
    IP: 69.25.118.70
    Date/Time: 5/24/2005 10:15:17 PM

    1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms e-wheelock.fairchild1-crt.Dartmouth.EDU [129.170.246.1]
    2 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms ropeferry-fairchild.ropeferry1-crt.dartmouth.edu [129.170.2.17]
    3 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms core.border1-rt.dartmouth.edu [129.170.2.195]
    4 4 ms 4 ms 4 ms 56 ms 4 ms 4 ms 4 ms 4 ms 4 ms 4 ms vtelinet-216-66-108-221.vermontel.net [216.66.108.221]
    5 18 ms 19 ms 19 ms 18 ms 19 ms 19 ms 18 ms 18 ms 18 ms 18 ms g11-2.core01.bos01.atlas.cogentco.com [38.112.23.169]
    6 39 ms 39 ms 39 ms 39 ms 39 ms 39 ms 39 ms 39 ms 39 ms 39 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.110]
    7 39 ms 39 ms 39 ms 39 ms 39 ms 39 ms 39 ms 39 ms 39 ms 39 ms p6-0.core01.ord03.atlas.cogentco.com [154.54.2.238]
    8 39 ms 40 ms 39 ms 40 ms 39 ms 40 ms 39 ms 40 ms 40 ms 39 ms peer1.ord03.atlas.cogentco.com [154.54.10.158]
    9 51 ms 51 ms 52 ms 51 ms 52 ms 51 ms 51 ms 51 ms 51 ms 51 ms OC48POS6-0.tor-core-1.peer1.net [216.187.114.142]
    10 52 ms 51 ms 52 ms 52 ms 52 ms 51 ms 51 ms 52 ms 52 ms 52 ms OC48POS1-0.tor-core-2.peer1.net [216.187.114.134]
    11 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 46 ms OC48POS3-0.mtl-core-b.peer1.net [216.187.68.93]
    12 47 ms 47 ms 47 ms 46 ms 47 ms 47 ms 47 ms 47 ms 46 ms 47 ms OC48POS4-0.mtl-core-a.peer1.net [216.187.90.45]
    13 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms OC48-POS2-0.nyc-telx-dis-a.peer1.net [216.187.115.130]
    14 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms OC48-POS3-0.nyc-teleh-dis-2.peer1.net [216.187.115.166]
    15 47 ms 48 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms 47 ms GIG6-0.nyc-gsr-a.peer1.net [216.187.123.17]
    16 79 ms 104 ms 101 ms 48 ms 57 ms 65 ms 110 ms 66 ms 48 ms 111 ms [216.187.123.44]
    17 90 ms 94 ms 109 ms 48 ms 56 ms 61 ms 112 ms 49 ms 49 ms 95 ms [69.25.118.70]


    Ignore the fact that cogent routes me to montreal then back, look at the last hop. Jumps from 47 ms to 101


    Now finally, if I ping thenynoc.com or any other Peer 1 IP direct, I get

    Target Name: thenynoc.com
    IP: 64.34.84.190
    Date/Time: 5/24/2005 10:16:02 PM

    1 0 ms 0 ms e-wheelock.fairchild1-crt.Dartmouth.EDU [129.170.246.1]
    2 0 ms 0 ms ropeferry-fairchild.ropeferry1-crt.dartmouth.edu [129.170.2.17]
    3 0 ms 0 ms core.border1-rt.dartmouth.edu [129.170.2.195]
    4 4 ms 4 ms vtelinet-216-66-108-221.vermontel.net [216.66.108.221]
    5 18 ms 18 ms g11-2.core01.bos01.atlas.cogentco.com [38.112.23.169]
    6 24 ms 23 ms p5-0.core01.jfk02.atlas.cogentco.com [66.28.4.118]
    7 29 ms 29 ms p4-0.core02.dca01.atlas.cogentco.com [66.28.4.81]
    8 30 ms 30 ms p14-0.core01.iad01.atlas.cogentco.com [154.54.2.198]
    9 26 ms 26 ms peer1.iad01.atlas.cogentco.com [154.54.10.110]
    10 26 ms 26 ms OC48-POS0-0.wdc-sp2-cor-1.peer1.net [216.187.115.234]
    11 26 ms 26 ms OC48-POS2-0.wdc-sp2-cor-2.peer1.net [216.187.115.246]
    12 31 ms 31 ms OC48POS3-0.nyc-telx-dis-1.peer1.net [216.187.115.221]
    13 31 ms 31 ms OC48-POS3-0.nyc-dis-b.peer1.net [216.187.115.134]
    14 33 ms 32 ms [216.187.115.162]
    15 32 ms 32 ms xeon.thenynoc.com [64.34.84.190]


    32 MS - why would Peer 1 direct ping any different than Peer 1 in a BGP mix?

    Does anyone have any explanations for these things
    Last edited by The Broadband Man; 05-24-2005 at 10:19 PM.
    ServGrid - www.servgrid.com - Affordable and Reliable SSD Cloud Solutions
    Premium 10G Network, 2(N+1) Powerplant and SSD Performance
    Web, Reseller, KVM VPS, Storage and Private Cloud Hosting
    Click here to see our SSD Benchmarks!

  2. #2
    Join Date
    May 2005
    Posts
    95

    Re: Peer 1 routing screwing the pooch?

    Originally posted by The Broadband Man
    Also, Peer 1 and their peering with cogent is creating problems as cogent is routing traffic any way they can to save cash.
    Nice intelligent statement.

  3. #3
    Join Date
    Jul 2004
    Location
    New York, NY
    Posts
    2,181
    ...

    how is that not intelligent? Transit providers have been known to reroute traffic through the cheapest way possible (1st to their peers) than through actual transit ... so what's your point
    ServGrid - www.servgrid.com - Affordable and Reliable SSD Cloud Solutions
    Premium 10G Network, 2(N+1) Powerplant and SSD Performance
    Web, Reseller, KVM VPS, Storage and Private Cloud Hosting
    Click here to see our SSD Benchmarks!

  4. #4
    Join Date
    May 2005
    Posts
    95
    traceroute to 69.25.118.65 (69.25.118.65), 30 hops max, 38 byte packets
    1 66.28.200.1 (66.28.200.1) 0.383 ms 0.293 ms 0.337 ms
    2 g2.ba21.b001027-0.iah01.atlas.cogentco.com (38.112.4.157) 0.515 ms g1.ba21.b001027-0.iah01.atlas.cogentco.com (38.112.12.245) 0.831 ms g10-2.core01.iah01.atlas.cogentco.com (38.112.20.193) 0.808 ms
    3 p13-0.core01.mci01.atlas.cogentco.com (66.28.4.106) 26.448 ms 26.468 ms *
    4 p5-0.core02.ord01.atlas.cogentco.com (66.28.4.34) 186.110 ms 115.478 ms 64.947 ms
    MPLS Label=16 CoS=6 TTL=1 S=0
    5 p15-0.core01.ord03.atlas.cogentco.com (154.54.2.242) 26.281 ms 26.287 ms 26.045 ms
    6 peer1.ord03.atlas.cogentco.com (154.54.10.158) 26.253 ms 26.096 ms 26.344 ms
    7 oc48pos6-0.tor-core-1.peer1.net (216.187.114.142) 38.599 ms 38.533 ms 37.963 ms
    8 oc48pos1-0.tor-core-2.peer1.net (216.187.114.134) 38.195 ms 38.010 ms 38.323 ms
    9 oc48pos3-0.mtl-core-b.peer1.net (216.187.68.93) 51.266 ms 51.977 ms 51.785 ms
    10 oc48pos5-0.mtl-core-a.peer1.net (65.39.166.173) 51.609 ms 51.499 ms 51.744 ms
    11 oc48-pos2-0.nyc-telx-dis-a.peer1.net (216.187.115.130) 51.466 ms 51.650 ms 51.489 ms
    12 oc48-pos3-0.nyc-teleh-dis-2.peer1.net (216.187.115.166) 51.497 ms 51.615 ms 51.669 ms
    13 gig6-0.nyc-gsr-a.peer1.net (216.187.123.17) 51.459 ms 52.298 ms 51.799 ms
    14 69.25.118.65 (69.25.118.65) 91.972 ms 62.785 ms 80.984 ms

  5. #5
    Join Date
    Jan 2005
    Posts
    296
    From Sago:

    Tracing route to 69.25.118.70 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms unknown.sagonet.net [66.118.175.37]
    2 1 ms <1 ms <1 ms 65.77.96.149
    3 11 ms 11 ms 11 ms drvlga1wcx2-pos15-2-oc48.wcg.net [64.200.240.29]

    4 22 ms 22 ms 22 ms hrndva1wcx3-pos14-0-oc192.wcg.net [64.200.210.23
    8]
    5 23 ms 22 ms 23 ms washdc5lce1-pos4-0-oc48.wcg.net [64.200.95.118]

    6 23 ms 22 ms 22 ms equinixexchange.peer1.net [206.223.115.30]
    7 23 ms 23 ms 23 ms OC48-POS0-0.wdc-sp2-cor-1.peer1.net [216.187.115
    .234]
    8 23 ms 23 ms 23 ms OC48-POS2-0.wdc-sp2-cor-2.peer1.net [216.187.115
    .246]
    9 28 ms 28 ms 28 ms OC48POS3-0.nyc-telx-dis-1.peer1.net [216.187.115
    .221]
    10 28 ms 28 ms 28 ms OC48-POS3-0.nyc-teleh-dis-2.peer1.net [216.187.1
    15.166]
    11 28 ms 28 ms 28 ms GIG6-0.nyc-gsr-a.peer1.net [216.187.123.17]
    12 65 ms 68 ms 67 ms 216.187.123.44
    13 74 ms 31 ms 31 ms 69.25.118.70

    Trace complete.


    From Superb:

    Tracing route to 69.25.118.70 over a maximum of 30 hops

    1 2 ms <1 ms <1 ms c-vl102-d1.acc.dca2.hopone.net [66.36.240.2]
    2 <1 ms <1 ms <1 ms ge4-0.core1.dca2.hopone.net [66.36.224.226]
    3 <1 ms <1 ms <1 ms ge3-0.core1.iad1.hopone.net [66.36.224.18]
    4 <1 ms <1 ms <1 ms equinixexchange.peer1.net [206.223.115.30]
    5 1 ms 1 ms 1 ms OC48-POS0-0.wdc-sp2-cor-1.peer1.net [216.187.115
    .234]
    6 1 ms 1 ms 1 ms OC48-POS2-0.wdc-sp2-cor-2.peer1.net [216.187.115
    .246]
    7 6 ms 6 ms 6 ms OC48POS3-0.nyc-telx-dis-1.peer1.net [216.187.115
    .221]
    8 6 ms 6 ms 6 ms OC48-POS3-0.nyc-teleh-dis-2.peer1.net [216.187.1
    15.166]
    9 6 ms 6 ms 6 ms GIG6-0.nyc-gsr-a.peer1.net [216.187.123.17]
    10 7 ms 7 ms 7 ms 216.187.123.44
    11 7 ms 7 ms 8 ms 69.25.118.70

    Trace complete.


    From FDC:

    Tracing route to 69.25.118.70 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 66.90.64.1 [66.90.64.1]
    2 <1 ms <1 ms <1 ms g0-8.na21.b000268-0.ord01.atlas.cogentco.com [38
    .112.0.181]
    3 9 ms 7 ms 8 ms g9-3.core01.ord01.atlas.cogentco.com [66.28.64.1
    29]
    4 4 ms 5 ms 4 ms p6-0.core01.ord03.atlas.cogentco.com [154.54.2.2
    38]
    5 6 ms 6 ms 18 ms peer1.ord03.atlas.cogentco.com [154.54.10.158]
    6 16 ms 16 ms 15 ms OC48POS6-0.tor-core-1.peer1.net [216.187.114.142
    ]
    7 13 ms 13 ms 14 ms OC48POS1-0.tor-core-2.peer1.net [216.187.114.134
    ]
    8 39 ms 39 ms 39 ms OC48POS3-0.mtl-core-b.peer1.net [216.187.68.93]

    9 36 ms 37 ms 38 ms OC48POS4-0.mtl-core-a.peer1.net [216.187.90.45]

    10 34 ms 34 ms 35 ms OC48-POS2-0.nyc-telx-dis-a.peer1.net [216.187.11
    5.130]
    11 34 ms 34 ms 35 ms OC48-POS3-0.nyc-teleh-dis-2.peer1.net [216.187.1
    15.166]
    12 36 ms 35 ms 35 ms GIG6-0.nyc-gsr-a.peer1.net [216.187.123.17]
    13 53 ms 29 ms 33 ms 216.187.123.44
    14 40 ms 28 ms 26 ms 69.25.118.70

    Trace complete.
    Last edited by tkam; 05-24-2005 at 10:30 PM.

  6. #6
    Join Date
    Jul 2004
    Location
    New York, NY
    Posts
    2,181
    Thanks guys -

    "12 65 ms 68 ms 67 ms 216.187.123.44
    13 74 ms 31 ms 31 ms 69.25.118.70"

    in tkam's trace ... <Sigh>
    ServGrid - www.servgrid.com - Affordable and Reliable SSD Cloud Solutions
    Premium 10G Network, 2(N+1) Powerplant and SSD Performance
    Web, Reseller, KVM VPS, Storage and Private Cloud Hosting
    Click here to see our SSD Benchmarks!

  7. #7
    Join Date
    Mar 2003
    Location
    California USA
    Posts
    13,681
    Tracing route to thenynoc.com [64.34.84.190]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms 192.168.2.1
    2 10 ms 13 ms 10 ms 10.237.128.1
    3 11 ms 10 ms 14 ms 68-190-192-77.riv-nod.charterpipeline.net [68.19
    0.192.77]
    4 9 ms 9 ms 16 ms 68-190-192-182.riv-nod.charterpipeline.net [68.1
    90.192.182]
    5 13 ms 34 ms 15 ms so-6-0-0-0.gar2.LosAngeles1.Level3.net [67.72.11
    6.5]
    6 12 ms 11 ms 12 ms 4.68.127.190
    7 12 ms 12 ms 13 ms dcr2-so-5-0-0.LosAngeles.savvis.net [204.70.192.
    118]
    8 46 ms 47 ms 47 ms bcs1-so-2-0-0.Dallas.savvis.net [204.70.192.85]

    9 43 ms 44 ms 45 ms bcs2-so-6-0-0.Dallas.savvis.net [204.70.192.50]

    10 66 ms 65 ms 63 ms dcr2-so-6-0-0.Atlanta.savvis.net [204.70.192.69]

    11 80 ms 79 ms 77 ms bcs2-so-1-2-0.Washington.savvis.net [204.70.192.
    62]
    12 79 ms 84 ms 79 ms bcs2-so-2-0-0.NewYork.savvis.net [204.70.192.2]

    13 83 ms 99 ms 79 ms dcr4-so-1-1-0-500.NewYork.savvis.net [204.70.192
    .213]
    14 94 ms 83 ms 83 ms aer1-port-channel-2-0.NewYork.savvis.net [208.17
    4.228.22]
    15 83 ms 80 ms 82 ms peer-1-networks.NewYork.savvis.net [206.24.195.1
    34]
    16 83 ms 87 ms 89 ms GIG4-0.nyc-gsr-c.peer1.net [216.187.123.14]
    17 80 ms 94 ms 85 ms 216.187.115.158
    18 81 ms 85 ms 83 ms 216.187.115.162
    19 103 ms 83 ms 82 ms xeon.thenynoc.com [64.34.84.190]

    Trace complete.
    Steven Ciaburri | Industry's Best Server Management - Rack911.com
    Software Auditing - 400+ Vulnerabilities Found - Quote @ https://www.RACK911Labs.com
    Fully Managed Dedicated Servers (Las Vegas, New York City, & Amsterdam) (AS62710)
    FreeBSD & Linux Server Management, Security Auditing, Server Optimization, PCI Compliance

  8. #8
    Join Date
    Jul 2004
    Location
    New York, NY
    Posts
    2,181
    Steve, can you trace the other IP - not thenynoc.com but 69.25.118.70
    ServGrid - www.servgrid.com - Affordable and Reliable SSD Cloud Solutions
    Premium 10G Network, 2(N+1) Powerplant and SSD Performance
    Web, Reseller, KVM VPS, Storage and Private Cloud Hosting
    Click here to see our SSD Benchmarks!

  9. #9
    Join Date
    Mar 2003
    Location
    California USA
    Posts
    13,681
    okay:

    Tracing route to 69.25.118.70 over a maximum of 30 hops

    1 1 ms 1 ms 1 ms 192.168.2.1
    2 9 ms 13 ms 14 ms 10.237.128.1
    3 9 ms 10 ms 13 ms 68-190-192-77.riv-nod.charterpipeline.net [68.19
    0.192.77]
    4 8 ms 9 ms 8 ms 68-190-192-182.riv-nod.charterpipeline.net [68.1
    90.192.182]
    5 20 ms 12 ms 11 ms so-6-1-0-0.gar2.LosAngeles1.Level3.net [4.78.202
    .33]
    6 12 ms 15 ms 13 ms so-0-1-0.bbr1.LosAngeles1.Level3.net [4.68.96.81
    ]
    7 79 ms 79 ms 80 ms as-1-0.bbr2.NewYork1.Level3.net [64.159.1.85]
    8 78 ms 92 ms 92 ms ae-20-52.car2.NewYork1.Level3.net [4.68.97.53]
    9 79 ms 85 ms 79 ms 4.78.132.2
    10 80 ms 81 ms 81 ms border11.ge3-0-bbnet2.nyc.pnap.net [209.191.128.
    145]
    11 98 ms 130 ms * fluidhosting-3.border22.nyc.pnap.net [72.5.142.6
    2]
    12 81 ms 82 ms 80 ms 69.25.118.70

    Trace complete.
    Steven Ciaburri | Industry's Best Server Management - Rack911.com
    Software Auditing - 400+ Vulnerabilities Found - Quote @ https://www.RACK911Labs.com
    Fully Managed Dedicated Servers (Las Vegas, New York City, & Amsterdam) (AS62710)
    FreeBSD & Linux Server Management, Security Auditing, Server Optimization, PCI Compliance

  10. #10
    Join Date
    May 2005
    Posts
    95
    6 peer1.ord03.atlas.cogentco.com (154.54.10.158) 26.324 ms 26.403 ms 26.242 ms
    7 oc48pos6-0.tor-core-1.peer1.net (216.187.114.142) 38.668 ms 38.076 ms 38.193 ms
    8 oc48pos1-0.tor-core-2.peer1.net (216.187.114.134) 38.160 ms * 38.279 ms
    9 oc48pos3-0.mtl-core-b.peer1.net (216.187.68.93) 51.895 ms 52.451 ms 53.173 ms
    10 oc48pos4-0.mtl-core-a.peer1.net (216.187.90.45) 51.494 ms 52.151 ms 51.672 ms
    11 oc48-pos2-0.nyc-telx-dis-a.peer1.net (216.187.115.130) 52.253 ms 52.144 ms 52.279 ms
    12 oc48-pos3-0.nyc-teleh-dis-2.peer1.net (216.187.115.166) 51.613 ms 51.852 ms 51.790 ms
    13 gig6-0.nyc-gsr-a.peer1.net (216.187.123.17) 52.240 ms 51.909 ms 52.148 ms
    14 216.187.123.44 (216.187.123.44) 101.550 ms * 52.497 ms
    15 69.25.118.70 (69.25.118.70) 58.287 ms 87.015 ms 102.603 ms

  11. #11
    Join Date
    Apr 2005
    Location
    Under The Floor Tiles
    Posts
    566
    If the core routers can find a way to get Server A's data to Client B through the most secure route, or avoiding Route C due to congestion, it'll do so. That's the beauty of intelligent routing and self-healing - Fiber cuts and congestion can be bypassed. Now, it sounds like you're doing this at very regular times - Try it during the middle of the day. It's like complaining that the interstate's always crowded, but you only use it during rush hour.

  12. #12
    Join Date
    Jul 2004
    Location
    New York, NY
    Posts
    2,181
    Thank you very much guys. Much appreciated.
    ServGrid - www.servgrid.com - Affordable and Reliable SSD Cloud Solutions
    Premium 10G Network, 2(N+1) Powerplant and SSD Performance
    Web, Reseller, KVM VPS, Storage and Private Cloud Hosting
    Click here to see our SSD Benchmarks!

  13. #13
    Join Date
    Dec 2002
    Location
    Ontario, Canada
    Posts
    178
    Something is definitely a little screwed up... A trace from my cabinet in Peer1 NY results in the following:

    PHP Code:
    root@newyork [/]# traceroute 69.25.118.70
    traceroute to 69.25.118.70 (69.25.118.70), 30 hops max38 byte packets
     1  69.28.218.33 
    (69.28.218.33)  0.478 ms  0.424 ms  0.415 ms
     2  216.187.115.146 
    (216.187.115.146)  0.846 ms  0.755 ms *
     
    3  OC48-POS1-0.nyc-telx-dis-a.peer1.net (216.187.115.133)  1.088 ms  1.039 ms  0.742 ms
     4  OC48
    -POS3-0.nyc-teleh-dis-2.peer1.net (216.187.115.166)  1.413 ms  1.109 ms *
     
    5  GIG6-0.nyc-gsr-a.peer1.net (216.187.123.17)  1.172 ms  0.895 ms  1.390 ms
     6  216.187.123.44 
    (216.187.123.44)  55.098 ms  53.885 ms  48.894 ms
     7  69.25.118.70 
    (69.25.118.70)  31.794 ms  1.925 ms  2.568 ms
    root
    @newyork [/]
    And for comparative sake a trace to The NY Noc:

    PHP Code:

    root
    @newyork [/]# traceroute www.thenynoc.com
    traceroute to thenynoc.com (64.34.84.190), 30 hops max38 byte packets
     1  69.28.218.33 
    (69.28.218.33)  0.460 ms  0.418 ms  0.408 ms
     2  216.187.115.146 
    (216.187.115.146)  1.160 ms  1.248 ms *
     
    3  216.187.115.162 (216.187.115.162)  2.201 ms  1.677 ms  1.992 ms
     4  xeon
    .thenynoc.com (64.34.84.190)  1.775 ms  1.263 ms  1.255 ms
    root
    @newyork [/]
    Last edited by Netivex; 05-24-2005 at 10:42 PM.
    Robert Donaldson | Netivex
    Toronto | Dedicated Servers

  14. #14
    Join Date
    Apr 2005
    Location
    Jacksonville, FL
    Posts
    981

    Re: Peer 1 routing screwing the pooch?

    Originally posted by The Broadband Man
    Ignore the fact that cogent routes me to montreal then back, look at the last hop. Jumps from 47 ms to 101
    First of all, Cogent handed you off to Peer1 in ORD. The fact that Peer1 doesn't show you the ORD hop is nothing new; it's called "hop hiding." Second, the routing that Peer1 uses after Cogent passes them your bits is Peer1's problem, not Cogent's. Based on what you pasted, I'm not even sure that your bits are passing through Toronto OR Montreal based on the latency. If I had to make an educated guess, i'd say that at least one of those cities is mislabeled.

    It's no wonder that Cogent has such a bad rap on these boards. People make blatantly incorrect assumptions about them that simply are not true. There's a word in my vocabulary that adequately describes this behavior, it's called "parroting." To the original poster: Next time, don't be a parrot.
    Last edited by tical; 05-24-2005 at 11:47 PM.

  15. #15
    Join Date
    Jul 2004
    Location
    New York, NY
    Posts
    2,181
    Tical before you go on a crusade to defend Cogent, .ord in Ashburne handed off to Peer 1 in toronto ...
    ServGrid - www.servgrid.com - Affordable and Reliable SSD Cloud Solutions
    Premium 10G Network, 2(N+1) Powerplant and SSD Performance
    Web, Reseller, KVM VPS, Storage and Private Cloud Hosting
    Click here to see our SSD Benchmarks!

  16. #16
    Join Date
    Jul 2004
    Location
    New York, NY
    Posts
    2,181
    Also, with regards to your parroting case, the post wasn't just about cogent, its also about savvis, I am simpy stating my opinions. I didn't know that was frowned upon on this board. Or its maybe just that you have some weird perogative to defend cogent no matter what
    ServGrid - www.servgrid.com - Affordable and Reliable SSD Cloud Solutions
    Premium 10G Network, 2(N+1) Powerplant and SSD Performance
    Web, Reseller, KVM VPS, Storage and Private Cloud Hosting
    Click here to see our SSD Benchmarks!

  17. #17
    Join Date
    Apr 2005
    Location
    Jacksonville, FL
    Posts
    981
    Originally posted by The Broadband Man
    Tical before you go on a crusade to defend Cogent, .ord in Ashburne handed off to Peer 1 in toronto ...
    What on earth are you talking about? Ashburn is a town in Virginia, ORD = Chicago. As for defending Cogent, my only agenda is that the truth be told. I've noticed that many on this board seem to throw truth and common sense out the window.

    Moderators: Any way I can get a trout slapping function?

  18. #18
    Join Date
    Jul 2004
    Location
    New York, NY
    Posts
    2,181
    Right and it is because cogent is such a great company that it goes from boston to chicago for a route that should be going to NY ... good job with that logic.

    Further more, my comment about VA refers to this

    Target Name: thenynoc.com
    IP: 64.34.84.190
    Date/Time: 5/25/2005 12:12:08 AM

    1 0 ms e-wheelock.fairchild1-crt.Dartmouth.EDU [129.170.246.1]
    2 0 ms ropeferry-fairchild.ropeferry1-crt.dartmouth.edu [129.170.2.17]
    3 0 ms core.border1-rt.dartmouth.edu [129.170.2.195]
    4 5 ms vtelinet-216-66-108-221.vermontel.net [216.66.108.221]
    5 18 ms g11-2.core01.bos01.atlas.cogentco.com [38.112.23.169]
    6 24 ms p5-0.core01.jfk02.atlas.cogentco.com [66.28.4.118]
    7 29 ms p4-0.core02.dca01.atlas.cogentco.com [66.28.4.81]
    8 30 ms p14-0.core01.iad01.atlas.cogentco.com [154.54.2.198]
    9 26 ms peer1.iad01.atlas.cogentco.com [154.54.10.110]
    10 26 ms OC48-POS0-0.wdc-sp2-cor-1.peer1.net [216.187.115.234]
    11 27 ms OC48-POS2-0.wdc-sp2-cor-2.peer1.net [216.187.115.246]
    12 37 ms OC48POS3-0.nyc-telx-dis-1.peer1.net [216.187.115.221]
    13 31 ms OC48-POS3-0.nyc-dis-b.peer1.net [216.187.115.134]
    14 32 ms [216.187.115.162]
    15 32 ms xeon.thenynoc.com [64.34.84.190]


    Cogent peers with Peer 1 in VA - IAD and therefore creates extra latency

    Finally, i was talking about savvis and simply taking ganders at different possibilities. So before you ask for a trout slapping function - slap yourself
    ServGrid - www.servgrid.com - Affordable and Reliable SSD Cloud Solutions
    Premium 10G Network, 2(N+1) Powerplant and SSD Performance
    Web, Reseller, KVM VPS, Storage and Private Cloud Hosting
    Click here to see our SSD Benchmarks!

  19. #19
    Join Date
    Jul 2003
    Location
    Texas
    Posts
    787
    From ThePlanet 40 odd packets

    Code:
    Hostname                                %Loss  Rcv  Snt  Last Best  Avg  Worst
     1. 99.69-56-159.reverse.theplanet.com     0%   41   41     0    0    2     37
     2. dsr1-1-v2.dllstx2.theplanet.com        0%   41   41     0    0    9    192
     3. dist-vlan21.dsr3-1.dllstx3.theplane    0%   41   41     0    0    5     87
     4. ae0-0.ibr2.dllstx3.theplanet.com       0%   40   40     0    0    2     12
     5. gw-cr2.dfw2.us.above.net               0%   40   40     0    0    6    107
     6. so-3-2-0.cr2.dca2.us.above.net         0%   40   40    29    0   21     29
     7. so-3-2-0.cr2.dca2.us.above.net         0%   40   40    29   28   31     59
     8. so-3-0-0.mpr1.iad2.us.above.net        0%   40   40    29   29   29     50
     9. so-3-0-0.mpr1.iad2.us.above.net        0%   40   40    31   29   31     95
    10. so-3-0-0.mpr1.iad10.us.above.net       0%   40   40    29   29   29     33
    11. OC48-POS0-0.wdc-sp2-cor-1.peer1.net    0%   40   40    29   29   29     30
    12. OC48-POS2-0.wdc-sp2-cor-2.peer1.net    0%   40   40    29   29   30     30
    13. OC48POS3-0.nyc-telx-dis-1.peer1.net    0%   40   40    30   29   33     35
    14. OC48-POS3-0.nyc-dis-b.peer1.net        0%   40   40    35   34   34     35
    15. 216.187.115.162                        0%   40   40    35   34   35     36
    16. 216.187.115.162                        0%   40   40    35   35   35     36
    17. xeon.thenynoc.com                      0%   40   40    35   35   35     36
    
    From Savvis 40 odd packets
                                               Packets               Pings
    Hostname                                %Loss  Rcv  Snt  Last Best  Avg  Worst
     1. 209.67.208.177                         0%   42   42     0    0    1     14
     2. 10.1.3.5                               0%   42   42     0    0    0      9
     3. 216.39.69.225                          0%   42   42   306    0    7    306
     4. chr1-g5-0.FortWorthda1.savvis.net      0%   42   42     0    0    0      1
     5. bcr1-so-5-0-0.Dallas.savvis.net        0%   42   42     1    1    2     10
     6. bcs2-so-1-0-0-500.Dallas.savvis.net    0%   42   42     1    1   11    109
     7. dcr2-so-6-0-0.Atlanta.savvis.net       0%   42   42    21    1   15     65
     8. dcr2-so-6-0-0.Atlanta.savvis.net       0%   42   42    21   21   30     72
     9. bcs2-so-2-0-0.NewYork.savvis.net       0%   42   42    35   35   38     62
    10. bcs2-so-2-0-0.NewYork.savvis.net       0%   42   42    40   39   39     42
    11. dcr4-so-1-1-0-500.NewYork.savvis.ne    0%   42   42    40   40   43    157
    12. peer-1-networks.NewYork.savvis.net     0%   41   41    40   39   41     88
    13. peer-1-networks.NewYork.savvis.net     0%   41   41    40   39   40     49
    14. 216.187.115.158                        0%   41   41    40   40   41     51
    15. 216.187.115.162                        0%   41   41    40   40   41     49
    16. 216.187.115.162                        0%   41   41    41   40   41     49
    17. xeon.thenynoc.com                      0%   41   41    41   39   41     49
    If possible you should try and use 'mtr' or 'winmtr' and more then 10 packets to give you a better trend. You can run it for longer and get more data. Using standard traceroute you could hit that one router that shows latency when its bursting and get a poor result or the router could just be passing ICMP at a much lower priority and mtr will show you that a lilttle more clearly then plain traceroute.

    Thanks,

    Jeremy

  20. #20
    Join Date
    Apr 2005
    Location
    Jacksonville, FL
    Posts
    981
    Originally posted by The Broadband Man
    Right and it is because cogent is such a great company that it goes from boston to chicago for a route that should be going to NY ... good job with that logic.
    So what you're saying is, Cogent is lame because they don't peer with Peer1 in NYC, right? I'm going to let you in on a little secret, since you obviously know NOTHING about peering. Peering is what companies do when and where they find that the settlement-free exchange of traffic gives mutual benefit to both companies. To say that it's Cogent's fault that they don't peer with Peer1 in NYC is idiotic. You don't work for Cogent, and you don't work for Peer1. You have no inside knowledge as to why there isn't a peer in NYC. The best thing to do is take your slap and sit down.

    *INSERT TROUT SLAP HERE*

  21. #21
    Join Date
    Jul 2004
    Location
    New York, NY
    Posts
    2,181
    WOW - Why am I even bothering ...

    cogent takes the cheap route out and peers with Peer 1 in VA ....

    moreover, I love how you ignore why cogent goes from BOS to Chicago which was my initial problem ...

    so why don't you once again slap yourself
    ServGrid - www.servgrid.com - Affordable and Reliable SSD Cloud Solutions
    Premium 10G Network, 2(N+1) Powerplant and SSD Performance
    Web, Reseller, KVM VPS, Storage and Private Cloud Hosting
    Click here to see our SSD Benchmarks!

  22. #22
    Join Date
    Apr 2005
    Location
    Jacksonville, FL
    Posts
    981
    Originally posted by The Broadband Man
    WOW - Why am I even bothering ...

    cogent takes the cheap route out and peers with Peer 1 in VA ....
    *upgrades the trout to a kingfish tied to the end of a cluebat and commences teh slapping*

    You need to re-read my post again and again until you understand what peering means. Don't talk, just read.

  23. #23
    Join Date
    Jul 2004
    Location
    New York, NY
    Posts
    2,181
    I KNOW WHAT PEERING MEANS - IT SAVES THEM THE MONEY OF BUYING TRANSIT and instead uses it free.

    you seem to want to focus on the VA part. How about you answer my complaint about boston to chicago?

    *takes the cluebat and shoves it up tical's unspeakable nether region
    ServGrid - www.servgrid.com - Affordable and Reliable SSD Cloud Solutions
    Premium 10G Network, 2(N+1) Powerplant and SSD Performance
    Web, Reseller, KVM VPS, Storage and Private Cloud Hosting
    Click here to see our SSD Benchmarks!

  24. #24
    Join Date
    Dec 2002
    Location
    Ontario, Canada
    Posts
    178
    Interesting to note, about 10 minutes ago i was seeing everywhere from 2 to 80% packet loss on that IP 216.187.123.44 when using MTR... (and I am inside Peer1 NY) and pings from 40 to 120ms ... Now however I am seeing 0 packet loss and 0ms pings...
    Robert Donaldson | Netivex
    Toronto | Dedicated Servers

  25. #25
    Join Date
    Jul 2004
    Location
    New York, NY
    Posts
    2,181
    Netivex, its only a few times of the day *shrug* - and its a few of their distribution level routers
    ServGrid - www.servgrid.com - Affordable and Reliable SSD Cloud Solutions
    Premium 10G Network, 2(N+1) Powerplant and SSD Performance
    Web, Reseller, KVM VPS, Storage and Private Cloud Hosting
    Click here to see our SSD Benchmarks!

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •