+ Reply to Thread
Results 1 to 8 of 8

Thread: Bad Pings and broken links

  1. #1
    Junior Member DireVisitor is on a distinguished road
    Join Date
    Sep 2010
    Posts
    11

    Bad Pings and broken links

    I used to ping 40 in Seattle and 49 in LA now it blows I cant get a trace to send through support
    So here is my Trace to the Seattle server
    Tracing route to 50.22.184.114-static.reverse.softlayer.com [50.22.184.114]
    over a maximum of 30 hops:

    1 7 ms 7 ms 7 ms Dire13 [0.0.0.0]
    2 9 ms 9 ms 8 ms 67.204.187.63
    3 11 ms 13 ms 12 ms por-edge-12.inet.qwest.net [65.121.148.253]
    4 16 ms 14 ms 16 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
    5 * * * Request timed out.
    6 26 ms 211 ms 75 ms ae-24-52.car4.Seattle1.Level3.net [4.69.147.166]

    7 91 ms 84 ms 85 ms te2-5.bbr01.wb01.sea01.networklayer.com [4.71.152.138]
    8 82 ms 85 ms 92 ms ae1.dar01.sr01.sea01.networklayer.com [173.192.18.143]
    9 72 ms 71 ms 74 ms po1.fcr02.sr03.sea01.networklayer.com [67.228.118.225]
    10 83 ms 74 ms 77 ms 50.22.184.114-static.reverse.softlayer.com [50.2
    2.184.114]

    Trace complete.
    Can you incompetent I.T People fix it. WHY DID I GO PRO FOR THIS S**T

  2. #2
    Senior Member Lorfa is a jewel in the rough Lorfa is a jewel in the rough Lorfa is a jewel in the rough Lorfa's Avatar
    Join Date
    Aug 2010
    Location
    Kepler-22b
    Posts
    8,365
    They very well might not have any control over that.

    What is your trace times to 4.69.147.166? Seems pretty unstable, here it is 26 211 and 75 ms.

  3. #3
    Junior Member DireVisitor is on a distinguished road
    Join Date
    Sep 2010
    Posts
    11
    C:\Users\Dire>tracert 4.69.147.166

    Tracing route to ae-24-52.car4.Seattle1.Level3.net [4.69.147.166]
    over a maximum of 30 hops:

    1 9 ms 7 ms 12 ms Dire13 [0.0.0.0]
    2 9 ms 9 ms 7 ms qwest-border.bendcable.com [216.228.160.63]
    3 9 ms 7 ms 7 ms 172.16.100.41
    4 16 ms 17 ms 16 ms vlan186.car1.Seattle1.Level3.net [4.53.151.9]
    5 91 ms 92 ms 87 ms ae-24-52.car4.Seattle1.Level3.net [4.69.147.166]


    Trace complete.
    Still a pretty high ping

  4. #4
    Senior Member Lorfa is a jewel in the rough Lorfa is a jewel in the rough Lorfa is a jewel in the rough Lorfa's Avatar
    Join Date
    Aug 2010
    Location
    Kepler-22b
    Posts
    8,365
    Ugh, that's terrible. Looks like level3 is all messed up again.

    I saw this kind of thing when people in New York had trouble getting good pings to the NY server when it was up. Level3 would go in circles and one of its hops would suddenly add like 80 ms. The sad thing is that they both appear to be in Seattle. It makes you wonder if your ping would drop if it could connect directly from car1.seattle.level3 to networklayer.com.

    I wonder if it's possible for a random user to get a response from level3 on such a thing.. probably not.

  5. #5
    Senior Member FlashSoul will become famous soon enough FlashSoul will become famous soon enough FlashSoul's Avatar
    Join Date
    Aug 2010
    Posts
    3,223
    He can always try but ISP and backbones hardly care about latency.

  6. #6
    Junior Member DireVisitor is on a distinguished road
    Join Date
    Sep 2010
    Posts
    11
    Well after this latest update and direct email to tech support all is working well again pings are back to normal thank you FlashSoul and Lorfa. Now how do I close the thread????
    Last edited by DireVisitor; 07-16-2013 at 11:40 AM.

  7. #7
    Junior Member DireVisitor is on a distinguished road
    Join Date
    Sep 2010
    Posts
    11
    need to edit my last statement my ping went back up only an hour or so after the update

  8. #8
    Junior Member DireVisitor is on a distinguished road
    Join Date
    Sep 2010
    Posts
    11
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Dire>tracert 4.69.147.166

    Tracing route to ae-24-52.car4.Seattle1.Level3.net [4.69.147.166]
    over a maximum of 30 hops:

    1 10 ms 13 ms 10 ms Dire13 [0.0.0.0]
    2 8 ms 11 ms 8 ms 360-border.bendcable.com [216.228.160.67]
    3 202 ms 214 ms 208 ms vlan186.car1.Seattle1.Level3.net [4.53.151.9]
    4 220 ms 224 ms 215 ms ae-24-52.car4.Seattle1.Level3.net [4.69.147.166]


    Trace complete.

    Still a really crappy ping

+ Reply to Thread

Posting Permissions

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