Results 1 to 7 of 7
  1. #1

    Exclamation need help getting level3 to fix hop problem

    I'm asking fellow webhosting, website admin, server using types of people to help me out. Their connection has gotten horrible to my server the past few weeks and it doesnt seem many people are complaining yet or they just don't care to fix it.

    The MS latency has gone from 30ms to 80ms constantly, many are experiencing over 110ms. The problem is located on the hop dubbed as-1-0.mp1.Miami1.Level3.net and that's just a few hops above my machine. This connection has been known to be bad by Level3 and never fixed.

    It's really destroying my voice communcation and web applications that my clients, friends, and family utilize for their everyday internet experience.

    Their email is: [email protected]

    Here are some traceroutes to show my point:
    1 lpagwb01-vlan151-phy.hpl.hp.com (192.6.19.2) * * 0.977 ms
    2 * * *
    3 * * *
    4 svl-edge-15.inet.qwest.net (65.115.64.25) 1.95 ms 0.976 ms 1.95 ms
    5 svl-core-02.inet.qwest.net (205.171.14.150) 1.95 ms (ttl=250!) 0.976 ms (ttl=250!) 0.976 ms (ttl=250!)
    6 svx-core-01.inet.qwest.net (205.171.14.78) 2.93 ms (ttl=249!) 2.93 ms (ttl=249!) 1.95 ms (ttl=249!)
    7 sjp-brdr-01.inet.qwest.net (205.171.214.134) 2.93 ms 1.95 ms 2.92 ms
    8 so-2-0-0.edge1.SanJose1.Level3.net (209.245.146.229) 1.95 ms (ttl=247!) 2.92 ms (ttl=247!) 1.95 ms (ttl=247!)
    9 so-1-2-0.bbr2.SanJose1.Level3.net (209.244.3.141) 65.4 ms (ttl=246!) 2.92 ms (ttl=246!) 2.93 ms (ttl=246!)
    10 as-0-0.mp2.Miami1.Level3.net (64.159.3.249) 90.8 ms (ttl=242!) as-1-0.mp1.Miami1.Level3.net (64.159.0.1) 91.7 ms (ttl=242!) 91.7 ms (ttl=242!)
    11 ge-10-1.hsa2.Miami1.Level3.net (64.159.1.102) 91.7 ms (ttl=242!) ge-9-0.hsa2.Miami1.Level3.net (64.159.0.14) 91.7 ms (ttl=242!) unknown.Level3.net (64.159.1.178) 90.8 ms (ttl=242!)


    here's a clip someone sent in:
    7 * so-2-1-0.bbr2.Chicago1.Level3.net (209.244.8.13) 14.294 ms
    8 as-1-0.mp1.Miami1.Level3.net (64.159.0.1) 60.087 ms
    9 as-0-0.mp2.Miami1.Level3.net (64.159.3.249) 61.158 ms
    10 as-1-0.mp1.Miami1.Level3.net (64.159.0.1) 109.525 ms



    2 48 ms 47 ms 47 ms adsl-208-191-53-254.dsl.fyvlar.swbell.net [208.
    91.53.254]
    3 48 ms 47 ms 49 ms dist2-vlan60.fyvlar.sbcglobal.net [151.164.169.
    47]
    4 47 ms 47 ms 48 ms bb1-g1-0.fyvlar.sbcglobal.net [151.164.169.225]
    5 59 ms 58 ms 59 ms bb1-p4-0.dllstx.sbcglobal.net [151.164.189.142]
    6 58 ms 58 ms 62 ms bb2-p10-0.dllstx.sbcglobal.net [151.164.40.210]
    7 59 ms 60 ms 58 ms ex2-p12-0.eqdltx.sbcglobal.net [151.164.42.19]
    8 58 ms 60 ms 59 ms ex1-p3-0.eqdltx.sbcglobal.net [151.164.41.154]
    9 60 ms 59 ms 60 ms sl-st20-dal-4-0.sprintlink.net [144.228.250.109
    10 59 ms 60 ms 60 ms interconnect-eng.Dallas1.Level3.net [64.158.168
    73]
    11 * 59 ms 59 ms so-1-2-0.bbr1.Dallas1.Level3.net [209.244.15.16
    ]
    12 106 ms 105 ms 106 ms as-1-0.mp1.Miami1.Level3.net [64.159.0.1]
    13 106 ms 107 ms 106 ms ge-10-0.hsa2.Miami1.Level3.net [64.159.1.94]
    14 107 ms 107 ms 106 ms 4.79.98.2



    1 gige-g9-0-20.gsr12012.sjc.he.net (66.220.6.129) 1.101 ms 0.806 ms 0.640 ms
    2 pos1-2.gsr12416.fmt.he.net (64.71.128.182) 1.771 ms 1.442 ms 2.765 ms
    3 pos0-0.gsr12416.sjc2.he.net (66.220.10.126) 2.155 ms 4.241 ms 2.239 ms
    4 216.218.214.222 (216.218.214.222) 2.181 ms 2.160 ms 2.221 ms
    5 so-1-2-0.bbr2.SanJose1.Level3.net (209.244.3.141) 2.662 ms 2.650 ms 27.999 ms
    6 as-0-0.mp2.Miami1.Level3.net (64.159.3.249) 167.817 ms as-1-0.mp1.Miami1.Level3.net (64.159.0.1) 86.268 ms 86.220 ms
    7 ge-9-1.hsa2.Miami1.Level3.net (64.159.0.22) 85.961 ms ge-10-0.hsa2.Miami1.Level3.net (64.159.1.94) 86.192 ms ge-10-1.hsa2.Miami1.Level3.net (64.159.1.102) 86.106 ms


    Thanks a lot for all of you who aid me. This hopefully will be enough to make them listen!

  2. #2
    Join Date
    Aug 2001
    Location
    Denver, CO
    Posts
    273
    There are only two traces that demonstrate latency..
    9 as-0-0.mp2.Miami1.Level3.net (64.159.3.249) 61.158 ms
    10 as-1-0.mp1.Miami1.Level3.net (64.159.0.1) 109.525 ms

    6 as-0-0.mp2.Miami1.Level3.net (64.159.3.249) 167.817 ms as-1-0.mp1.Miami1.Level3.net (64.159.0.1) 86.268 ms 86.220 ms
    I don't know how long it takes to go from what I assume is CA to Miami but about 85 ms sounds about right (I'd assume 70 ms to be more normal) the 40 ms hop from dallas to miami I would also assume is normal

    If the 61 to 109 ms trace is correct for Miami then that's quite latent and one spike of 167 ms going from san jose to miami isn't that awful..

    I think you need to take time and do more latency checks even you naming the mp1 router as the problem only conforms to one trace as mp2 is the 167 ms spiker in the other trace I see..

  3. #3
    Well I'm not the only one with this problem. Level3 acknowledged a routing problem, they just aren't really trying to fix it yet. They've been talking about switching routes around for about two weeks but haven't really made an effort to do anything. Actually when my uplink called, they basically told them it is on-hold right now. That just ticks me off that Level3 is sitting on its hands instead of working this out.


    Also, I did a lot of traceroutes from traceroute.org and so long as the hop didn't include that particular router, the MS was very low. However, if any traceroute hit that hop I named the latency shot up at least 30-40MS. The unfortunate part is most of the users of my system hit the hop that needs repaired.

  4. #4
    Join Date
    Dec 2004
    Location
    Chicago
    Posts
    986
    If you've already informed them of the problem, what more are you looking to do?
    Corey Northcutt | Northcutt
    Competitive inbound marketing with a hosting industry competency.
    Social | Content | Optimization | Outreach

  5. #5
    Join Date
    Nov 2002
    Posts
    2,780
    They may affect another route if they fix this for you. Just hang on and they should have it fix. The L3 network is having minor problem here and there nowadays.

  6. #6
    Join Date
    Apr 2005
    Location
    Jacksonville, FL
    Posts
    977
    Originally posted by encrypted
    Well I'm not the only one with this problem. Level3 acknowledged a routing problem, they just aren't really trying to fix it yet. They've been talking about switching routes around for about two weeks but haven't really made an effort to do anything. Actually when my uplink called, they basically told them it is on-hold right now. That just ticks me off that Level3 is sitting on its hands instead of working this out.
    First of all, you haven't demonstrated a problem. Secondly, if there is a problem, don't be mad at the carrier, be mad at the ones who continue to route your bits down (what you think is) a broken link. Honestly.. what is it that you expect anyone on this forum to do?

  7. #7
    Join Date
    Jan 2004
    Location
    North Yorkshire, UK
    Posts
    4,163

Posting Permissions

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