Results 1 to 18 of 18
  1. #1

    [My server at] BurstNet Scranton downtimes for last week?

    host-tracker dot com/check_res_ajx/6748526-0/
    Support say all ok! Is burstnet support st**id?

  2. #2
    there is nothing clear in your message, what you want to ask really?

  3. #3
    Am I righ saing that some **** happens with Scanton network or not?
    now url: host-tracker dot com/check_res_ajx/6748606-0/
    Location Result Page Size Response time KB/sec IP Partner
    Received responses: 55 Ok Average: 0.49 sec 13.67

    was
    url
    host-tracker dot com/check_res_ajx/6748526-0/
    Location Result Page Size Response time KB/sec IP Partner
    Received responses: 38 Ok 12 Fail Average: 2.61 sec 23.28

    Becouse now (after 10 minutes) it's looks ok...
    And what write to support of it network, becouse they don't see any problems...

  4. #4
    Join Date
    Apr 2007
    Posts
    3,513
    May be you would be better sending their support that link?
    - Buying up websites, side-projects and companies - PM Me! -

  5. #5
    I did and allways I get same answer....

    As I said previously, this issue should have resolved itself for you now. If you still experiencing this, please provide me with a traceroute.

  6. #6
    Join Date
    Jun 2001
    Location
    Gotham City
    Posts
    1,849
    Have you been able to provide them with a traceroute ? It does usually help a lot in tracking down problems.

    We host quite a few servers at BurstNET and have not had any downtimes recently.
    [[ Reyox Communications / USA based cloud servers & support / 9 years of hosting websites ]]
    [[ Affordable ASP.NET4, ColdFusion, PHP & MS-SQL, MySQL, cPanel/WHM & Windows Reseller Hosting + Virtual Private Servers ]]
    (www.reyox.com) - Mention WHT and get a discount on your first month!

  7. #7
    Join Date
    Apr 2000
    Location
    Nevada, US
    Posts
    5,433
    There has been no such network-wide issues.
    Checking one specific website has absolutely nothing to do with a network performance/uptime as a whole.
    At the specific moment you check, some backbone on the Internet could have been having an issue routing to us 2000 miles away, affecting those few ISPs that reported such, whereas the same time the majority of other networks you tested could access us just fine.
    Send some traceroutes if you want to have an educated discussion, otherwise, this is nothing more than some local ISPs with overloaded pipes somewhere, having nothing to do with us.
    .
    .

  8. #8
    For example I'd post trace to ticket but did not get any comments...
    traceroute to 213.174.155.213 (213.174.155.213), 30 hops max, 40 byte packets
    1 64-191-40-17.hostnoc.net (64.191.40.17) 0.400 ms 0.462 ms 0.516 ms
    2 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 85.684 ms 85.744 ms 85.799 ms
    3 nyiix.he.net (198.32.160.61) 15.339 ms 15.251 ms 15.200 ms
    4 10gigabitethernet1-1.core1.nyc4.he.net (72.52.92.45) 11.047 ms 11.192 ms 11.084 ms
    5 10gigabitethernet2-3.core1.ash1.he.net (72.52.92.86) 19.426 ms 19.793 ms 20.265 ms
    6 209.51.184.194 (209.51.184.194) 90.216 ms 90.350 ms 90.258 ms
    7 213.174.155.213 (213.174.155.213) 92.979 ms 92.323 ms 90.866 ms

    What do you think about
    2 xe2-03.gwy03.sctn01.hostnoc.net (64.120.243.29) 85.684 ms 85.744 ms 85.799 ms is it ok?

    Cylestyne do you host at scranton?

  9. #9
    Join Date
    Jun 2001
    Location
    Gotham City
    Posts
    1,849
    Yes, we have several servers in Scranton.
    [[ Reyox Communications / USA based cloud servers & support / 9 years of hosting websites ]]
    [[ Affordable ASP.NET4, ColdFusion, PHP & MS-SQL, MySQL, cPanel/WHM & Windows Reseller Hosting + Virtual Private Servers ]]
    (www.reyox.com) - Mention WHT and get a discount on your first month!

  10. #10
    Start ping your servers and you will see that some times there is a lot of packet loss...

  11. #11
    Join Date
    Jun 2001
    Location
    Gotham City
    Posts
    1,849
    Nope, no packet loss. I tried pinging your IP-- while there isn't any packet loss ping times aren't consistent.
    [[ Reyox Communications / USA based cloud servers & support / 9 years of hosting websites ]]
    [[ Affordable ASP.NET4, ColdFusion, PHP & MS-SQL, MySQL, cPanel/WHM & Windows Reseller Hosting + Virtual Private Servers ]]
    (www.reyox.com) - Mention WHT and get a discount on your first month!

  12. #12
    Singapore, Singapore: Okay 299.4 299.8 300.4 66.96.192.202
    Amsterdam2, Netherlands: Okay 91.3 91.4 91.5 66.96.192.202
    Florida, U.S.A.: Okay 57.5 57.7 57.8 66.96.192.202
    Amsterdam3, Netherlands: Okay 91.0 91.2 91.5 66.96.192.202
    Hong Kong, China: Packets lost (60%) 246.4 247.8 248.7 2607:f878:1:634::2
    Sydney, Australia: Okay 242.3 242.9 244.9 66.96.192.202
    München, Germany: Packets lost (100%) 2607:f878:1:634::2
    Cologne, Germany: Packets lost (100%) 2607:f878:1:634::2
    New York, U.S.A.: Packets lost (60%) 92.9 93.9 95.0 2607:f878:1:634::2
    Cairo, Egypt: Okay 157.2 163.0 186.6 66.96.192.202
    Amsterdam, Netherlands: Okay 96.7 96.8 97.2 66.96.192.202
    Stockholm, Sweden: Okay 112.1 112.2 112.4 2607:f878:1:634::2
    Santa Clara, U.S.A.: Okay 91.0 94.0 96.2 66.96.192.202
    Vancouver, Canada: Okay 99.9 100.4 100.7 2607:f878:1:634::2
    Krakow, Poland: Okay 132.0 132.1 132.2 66.96.192.202
    London, United Kingdom: Packets lost (100%) 2607:f878:1:634::2
    Madrid, Spain: Packets lost (10%) 151.8 155.3 161.4 66.96.192.202
    Padova, Italy: Packets lost (50%) 207.8 210.2 214.3 2607:f878:1:634::2
    Austin, U.S.A.: Okay 38.8 38.9 38.9 66.96.192.202
    Amsterdam, Netherlands: Packets lost (50%) 165.0 167.0 169.6 2607:f878:1:634::2
    Paris, France: Okay 94.7 95.2 97.2 2607:f878:1:634::2
    Melbourne, Australia: Okay 253.2 254.4 257.5 2607:f878:1:634::2
    Shanghai, China: Checkpoint temporarily not available - - - -
    Copenhagen, Denmark: Okay 148.9 150.1 151.0 2607:f878:1:634::2
    Lille, France: Okay 90.4 90.6 91.0 66.96.192.202
    San Francisco, U.S.A.: Packets lost (60%) 100.7 102.1 105.5 2607:f878:1:634::2
    Zurich, Switzerland: Packets lost (10%) 237.9 240.8 243.8 66.96.192.202
    Mumbai, India: Okay 287.7 289.9 305.1 66.96.192.202
    Chicago, U.S.A.: Packets lost (70%) 98.6 99.6 101.0 2607:f878:1:634::2
    Nagano, Japan: Okay 185.2 185.2 185.4 66.96.192.202
    Haifa, Israel: Packets lost (60%) 229.6 230.3 231.6 66.96.192.202
    Auckland, New Zealand: Okay 212.4 212.8 213.7 66.96.192.202
    Antwerp, Belgium: Okay 89.8 89.9 90.0 66.96.192.202
    Groningen, Netherlands: Okay 95.1 95.6 96.4 66.96.192.202
    Moscow, Russia: Okay 207.3 207.5 207.7 2607:f878:1:634::2
    Dublin, Ireland: Okay 90.3 90.7 91.1 66.96.192.202
    Oslo, Norway: Okay 115.5 115.7 115.8 66.96.192.202
    Kharkov, Ukraine: Okay 189.1 190.0 192.8 66.96.192.202
    Manchester, United Kingdom: Okay 80.4 80.4 80.6 66.96.192.202
    Vilnius, Lithuania: Packets lost (70%) 217.8 219.2 220.7 66.96.192.202
    Ashburn, U.S.A.: Packets lost (30%) 98.0 99.2 101.0 2607:f878:1:634::2
    Bucharest, Romania: Packets lost (10%) 156.5 161.1 164.6 66.96.192.202
    Bangkok, Thailand: Okay 275.3 275.6 276.0 66.96.192.202
    Kuala Lumpur, Malaysia: Packets lost (10%) 270.4 272.4 277.5 66.96.192.202
    Jakarta, Indonesia: Okay 260.9 263.3 269.3 66.96.192.202
    Cape Town, South Africa: Okay 246.7 246.9 247.1 66.96.192.202
    Glasgow, United Kingdom: Okay 96.5 96.6 96.7 66.96.192.202
    Lisbon, Portugal: Okay 134.9 135.3 135.7 66.96.192.202
    Chicago, U.S.A.: Packets lost (80%) 102.5 102.8 103.0 66.96.192.202
    Dallas, U.S.A.: Packets lost (60%) 94.7 95.5 96.2 66.96.192.202
    Buenos Aires, Argentina: Unknown result from ping 2607:f878:1:634::2
    Istanbul, Turkey: Packets lost (10%) 143.5 144.0 144.3 66.96.192.202
    Gdansk, Poland: Okay 124.7 134.4 152.2 66.96.192.202
    Beijing, China: Checkpoint temporarily not available - - - -

    http://just-ping.com/index.php?vh=burst.net&c=&s=ping!


    at same time I ping

    Location Result min. rrt avg. rrt max. rrt IP
    Singapore, Singapore: Okay 344.2 345.7 348.6 178.238.129.83
    Amsterdam2, Netherlands: Okay 15.8 16.9 21.0 178.238.129.83
    Florida, U.S.A.: Okay 141.2 143.1 150.3 178.238.129.83
    Amsterdam3, Netherlands: Okay 15.5 17.8 27.9 178.238.129.83
    Hong Kong, China: Okay 269.9 274.0 278.5 178.238.129.83
    Sydney, Australia: Okay 311.3 313.7 318.0 178.238.129.83
    München, Germany: Okay 41.0 45.6 48.5 178.238.129.83
    Cologne, Germany: Okay 23.9 26.5 29.3 178.238.129.83
    New York, U.S.A.: Okay 87.4 96.2 106.5 178.238.129.83
    Cairo, Egypt: Okay 62.1 70.8 108.1 178.238.129.83
    Amsterdam, Netherlands: Okay 15.3 17.3 24.4 178.238.129.83
    Stockholm, Sweden: Okay 40.0 42.9 50.6 178.238.129.83
    Santa Clara, U.S.A.: Okay 148.8 150.3 154.0 178.238.129.83
    Vancouver, Canada: Okay 188.7 191.4 195.7 178.238.129.83
    Krakow, Poland: Okay 49.4 51.9 59.0 178.238.129.83
    London, United Kingdom: Packets lost (10%) 9.5 13.5 16.4 178.238.129.83
    Madrid, Spain: Okay 62.2 67.1 71.9 178.238.129.83
    Padova, Italy: Okay 39.6 42.2 46.6 178.238.129.83
    Austin, U.S.A.: Okay 127.6 130.8 133.9 178.238.129.83
    Amsterdam, Netherlands: Okay 15.5 19.8 23.6 178.238.129.83
    Paris, France: Okay 18.0 21.9 25.3 178.238.129.83
    Melbourne, Australia: Okay 332.1 335.7 338.7 178.238.129.83
    Shanghai, China: Okay 455.9 465.9 473.2 178.238.129.83
    Copenhagen, Denmark: Okay 27.3 31.8 34.8 178.238.129.83
    Lille, France: Okay 12.3 15.1 17.3 178.238.129.83
    San Francisco, U.S.A.: Packets lost (10%) 147.8 150.9 153.9 178.238.129.83
    Zurich, Switzerland: Okay 56.3 59.6 64.2 178.238.129.83
    Mumbai, India: Packets lost (10%) 181.2 184.2 186.5 178.238.129.83
    Chicago, U.S.A.: Okay 104.6 107.7 112.1 178.238.129.83
    Nagano, Japan: Packets lost (10%) 257.6 260.6 262.9 178.238.129.83
    Haifa, Israel: Okay 87.3 91.6 95.3 178.238.129.83
    Auckland, New Zealand: Okay 284.8 287.4 290.6 178.238.129.83
    Antwerp, Belgium: Okay 23.4 26.7 29.9 178.238.129.83
    Groningen, Netherlands: Okay 31.9 34.8 37.7 178.238.129.83
    Moscow, Russia: Okay 60.9 64.2 66.2 178.238.129.83
    Dublin, Ireland: Okay 23.5 25.6 27.4 178.238.129.83
    Oslo, Norway: Okay 37.5 41.3 43.2 178.238.129.83
    Kharkov, Ukraine: Okay 62.1 65.7 68.8 178.238.129.83
    Manchester, United Kingdom: Okay 16.9 20.4 23.2 178.238.129.83
    Vilnius, Lithuania: Okay 53.4 57.3 61.8 178.238.129.83
    Ashburn, U.S.A.: Okay 83.0 86.4 89.3 178.238.129.83
    Bucharest, Romania: Okay 64.2 68.7 71.8 178.238.129.83
    Bangkok, Thailand: Okay 307.8 311.1 317.6 178.238.129.83
    Kuala Lumpur, Malaysia: Okay 333.7 336.5 339.0 178.238.129.83
    Jakarta, Indonesia: Okay 231.8 234.9 239.6 178.238.129.83
    Cape Town, South Africa: Okay 159.2 163.2 167.3 178.238.129.83
    Glasgow, United Kingdom: Okay 21.4 23.5 25.8 178.238.129.83
    Lisbon, Portugal: Okay 60.3 63.7 67.5 178.238.129.83
    Chicago, U.S.A.: Okay 103.0 105.9 108.1 178.238.129.83
    Dallas, U.S.A.: Okay 114.7 118.4 120.8 178.238.129.83
    Buenos Aires, Argentina: Okay 234.6 237.9 239.9 178.238.129.83
    Istanbul, Turkey: Okay 75.6 78.6 82.2 178.238.129.83
    Gdansk, Poland: Packets lost (10%) 50.4 66.2 124.6 178.238.129.83
    Beijing, China: Okay 360.4 364.2 370.1 178.238.129.83
    http://just-ping.com/index.php?vh=bu...511&vhost=_&c=

    Now say... is it problem with Scranton or with local providers?

  13. #13
    Cylestyne could you plz ping a little longer burst.net and post it here?
    Thanks a lot for helping!

  14. #14
    Join Date
    Feb 2008
    Location
    Houston, Texas, USA
    Posts
    2,955
    Try: pathping <destination ip>

    It'll give you a complete report of packet loss along the route.

    Regards
    Joe
    UNIXy - Fully Managed Servers and Clusters - Established in 2006
    [ cPanel Varnish Nginx Plugin ] - Enhance LiteSpeed and Apache Performance
    www.unixy.net - Los Angeles | Houston | Atlanta | Rotterdam
    Love to help pro bono (time permitting). joe > unixy.net

  15. #15
    Join Date
    Jun 2003
    Location
    California
    Posts
    2,766
    I just used the pathping command from here in SoCal:

    Regular ping:

    C:\Users\Frank>ping 213.174.155.213

    Pinging 213.174.155.213 with 32 bytes of data:
    Reply from 213.174.155.213: bytes=32 time=94ms TTL=51
    Reply from 213.174.155.213: bytes=32 time=101ms TTL=51
    Reply from 213.174.155.213: bytes=32 time=93ms TTL=51
    Reply from 213.174.155.213: bytes=32 time=93ms TTL=51

    Ping statistics for 213.174.155.213:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 93ms, Maximum = 101ms, Average = 95ms

    C:\Users\Frank>pathping 213.174.155.213

    Tracing route to 213.174.155.213 over a maximum of 30 hops

    0 Acer [192.168.1.104]
    1 192.168.1.1
    2 cpe-76-167-208-1.socal.res.rr.com [xx.xxx.xxx.x]
    3 76.167.20.29
    4 ae4.vnnyca2-rtr1.socal.rr.com [66.75.147.30]
    5 BE13-lsanca4-rtr3.socal.rr.com [66.75.147.3]
    6 BE25-lsanca4-rt1.socal.rr.com [66.75.161.156]
    7 ae-6-0.cr0.lax00.tbone.rr.com [66.109.6.212]
    8 ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
    9 xe-8-1-0.edge1.LosAngeles6.Level3.net [4.26.0.17]
    10 vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
    11 ae-73-73.ebr3.LosAngeles1.Level3.net [4.69.137.37]
    12 ae-4-4.ebr4.Washington1.Level3.net [4.69.132.82]
    13 ae-64-64.csw1.Washington1.Level3.net [4.69.134.178]
    14 ae-13-60.car3.Washington1.Level3.net [4.69.149.5]
    15 IPTRIPLEPLA.car3.Washington1.Level3.net [4.79.169.78]
    16 ah.r0.101.eq.ash.va.us.iptp.net [98.158.98.254]
    17 213.174.155.213

    Computing statistics for 425 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Acer [192.168.1.104]
    0/ 100 = 0% |
    1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
    0/ 100 = 0% |
    2 11ms 0/ 100 = 0% 0/ 100 = 0% cpe-xx-xxx-xxx-x.socal.res.rr.com
    [xx.xxx.xxx.x]
    0/ 100 = 0% |
    3 11ms 0/ 100 = 0% 0/ 100 = 0% 76.167.20.29
    0/ 100 = 0% |
    4 16ms 0/ 100 = 0% 0/ 100 = 0% ae4.vnnyca2-rtr1.socal.rr.com [66.
    75.147.30]
    0/ 100 = 0% |
    5 18ms 0/ 100 = 0% 0/ 100 = 0% BE13-lsanca4-rtr3.socal.rr.com [66
    .75.147.3]
    0/ 100 = 0% |
    6 18ms 0/ 100 = 0% 0/ 100 = 0% BE25-lsanca4-rt1.socal.rr.com [66.
    75.161.156]
    0/ 100 = 0% |
    7 19ms 0/ 100 = 0% 0/ 100 = 0% ae-6-0.cr0.lax00.tbone.rr.com [66.
    109.6.212]
    0/ 100 = 0% |
    8 19ms 0/ 100 = 0% 0/ 100 = 0% ae-0-0.pr0.lax00.tbone.rr.com [66.
    109.6.135]
    0/ 100 = 0% |
    9 21ms 0/ 100 = 0% 0/ 100 = 0% xe-8-1-0.edge1.LosAngeles6.Level3.
    net [4.26.0.17]
    0/ 100 = 0% |
    10 19ms 0/ 100 = 0% 0/ 100 = 0% vlan70.csw2.LosAngeles1.Level3.net
    [4.69.144.126]
    0/ 100 = 0% |
    11 20ms 0/ 100 = 0% 0/ 100 = 0% ae-73-73.ebr3.LosAngeles1.Level3.n
    et [4.69.137.37]
    0/ 100 = 0% |
    12 92ms 0/ 100 = 0% 0/ 100 = 0% ae-4-4.ebr4.Washington1.Level3.net
    [4.69.132.82]
    0/ 100 = 0% |
    13 88ms 0/ 100 = 0% 0/ 100 = 0% ae-64-64.csw1.Washington1.Level3.n
    et [4.69.134.178]
    0/ 100 = 0% |
    14 97ms 0/ 100 = 0% 0/ 100 = 0% ae-13-60.car3.Washington1.Level3.n
    et [4.69.149.5]
    0/ 100 = 0% |
    15 89ms 2/ 100 = 2% 2/ 100 = 2% IPTRIPLEPLA.car3.Washington1.Level
    3.net [4.79.169.78]
    0/ 100 = 0% |
    16 93ms 1/ 100 = 1% 1/ 100 = 1% ah.r0.101.eq.ash.va.us.iptp.net [9
    8.158.98.254]
    0/ 100 = 0% |
    17 98ms 0/ 100 = 0% 0/ 100 = 0% 213.174.155.213

    Trace complete.
    I certainly don't see anything wrong with the response from Southern California.

    "ms" stands for "milliseconds", a measure of time 1,000th second in length. IIRC, when you blink, you are "blind" for about 400ms.

  16. #16
    fshagan plz try ping burst.net
    I traced from burst to my server...

  17. #17
    -sh-3.2$ traceroute burst.net
    traceroute to burst.net (66.96.192.202), 30 hops max, 40 byte packets
    1 174.37.16.65-static.reverse.softlayer.com (174.37.16.65) 0.336 ms 0.424 ms 0.509 ms
    2 po104.dar02.sr01.dal01.networklayer.com (66.228.118.217) 0.399 ms 0.438 ms 0.528 ms
    3 ae6.bbr02.eq01.dal03.networklayer.com (173.192.18.212) 0.470 ms 0.464 ms 0.456 ms
    4 po2.bbr02.tl01.atl01.networklayer.com (173.192.18.135) 20.154 ms 20.193 ms 20.233 ms
    5 po5.bbr01.eq01.wdc02.networklayer.com (173.192.18.152) 32.853 ms 32.894 ms 32.983 ms
    6 vl0020.gwy01.sctn01.hostnoc.net (206.223.115.210) 42.160 ms 42.027 ms 42.043 ms
    7 ec1-25.grd01.sctn01.hostnoc.net (96.9.191.142) 42.336 ms 42.258 ms 42.250 ms
    8 vl0190.grd01.sctn01.hostnoc.net (96.9.191.120) 42.392 ms 42.630 ms 42.371 ms
    9 tn0-01.agg01.sctn01.hostnoc.net (96.9.191.46) 42.371 ms 42.104 ms 42.355 ms
    10 * * *
    11 * * *
    12 * * *
    13 * * *
    14 * * *
    15 * * *
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *

    traceroute to burst.net (66.96.192.202), 30 hops max, 40 byte packets
    1 66.230.167.1 (66.230.167.1) 1.630 ms 1.850 ms 2.081 ms
    2 ge9-45.xbr1.whk1.as23393.net (64.111.192.217) 0.569 ms 0.562 ms 0.554 ms
    3 vl501.te1-4.xbr1.25b.as23393.net (64.111.192.205) 1.028 ms vl506.te1-1.xbr1.25b.as23393.net (66.230.128.253) 1.513 ms vl501.te1-4.xbr1.25b.as23393.net (64.111.192.205) 1.486 ms
    4 198.32.229.22 (198.32.229.22) 0.492 ms 0.719 ms 0.701 ms
    5 10gigabitethernet1-1.core1.nyc4.he.net (72.52.92.45) 0.937 ms 0.929 ms 0.670 ms
    6 10gigabitethernet5-3.core1.lax1.he.net (72.52.92.226) 61.858 ms 68.868 ms 61.851 ms
    7 10gigabitethernet1-3.core1.lax2.he.net (72.52.92.122) 62.088 ms 62.082 ms 61.916 ms
    8 burstnet-technologies-inc.gigabitethernet4-20.core1.lax2.he.net (66.160.192.62) 78.385 ms 78.378 ms 78.399 ms
    9 xe1-01.gwy01.sctn01.hostnoc.net (96.9.191.77) 85.379 ms 85.371 ms 85.388 ms
    10 ec1-24.grd01.sctn01.hostnoc.net (96.9.191.138) 85.614 ms 85.602 ms 85.066 ms
    11 vl0190.grd01.sctn01.hostnoc.net (96.9.191.120) 85.291 ms 85.408 ms 85.633 ms
    12 tn0-01.agg01.sctn01.hostnoc.net (96.9.191.46) 85.614 ms 85.352 ms 85.590 ms
    13 * * *
    14 * * *
    15 * * *
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *


    traceroute to burst.net (66.96.192.202), 30 hops max, 40 byte packets
    1 195.178.4.1 (195.178.4.1) 0.599 ms 0.634 ms 0.683 ms
    2 78.140.169.21 (78.140.169.21) 0.695 ms 0.709 ms *
    3 * * *
    4 * * *
    5 * * *
    6 * * *
    7 * * *
    8 10gigabitethernet4-4.core1.nyc4.he.net (72.52.92.241) 98.735 ms 98.605 ms 98.922 ms
    9 * * *
    10 10gigabitethernet1-3.core1.lax2.he.net (72.52.92.122) 168.504 ms 168.471 ms *
    11 * * *
    12 * * *
    13 * * *
    14 vl0190.grd01.sctn01.hostnoc.net (96.9.191.120) 176.962 ms * *
    15 * * *
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *

    traceroute to burst.net (66.96.192.202), 64 hops max, 40 byte packets
    1 88.208.22.252 (88.208.22.252) 0.280 ms 0.346 ms 0.287 ms
    2 4004.r0.nkf.ams.nl.iptp.net (91.194.117.155) 0.293 ms 0.336 ms 0.310 ms
    3 amsix.r2.am.hwng.net (195.69.145.70) 0.606 ms 10.082 ms 6.104 ms
    4 5-1.r2.dc.hwng.net (69.16.190.38) 128.200 ms 87.400 ms 85.669 ms
    5 2-3.r1.dc.hwng.net (69.16.190.25) 79.301 ms 83.757 ms 79.303 ms
    6 209.197.18.18 (209.197.18.18) 85.433 ms 85.553 ms 85.657 ms
    7 209.197.18.22 (209.197.18.22) 86.446 ms 86.766 ms 86.139 ms
    8 ec1-24.grd01.sctn01.hostnoc.net (96.9.191.138) 86.175 ms 86.264 ms 86.332 ms
    9 vl0190.grd01.sctn01.hostnoc.net (96.9.191.120) 86.155 ms 86.127 ms 86.302 ms
    10 tn0-01.agg01.sctn01.hostnoc.net (96.9.191.46) 86.421 ms 86.101 ms 86.307 ms
    11 * * *
    12 * * *
    13 * * *
    14 * * *
    15 * * *
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *
    31 * * *
    32 * * *
    Next time I'll add trace when burstnet have problem with network again...

  18. #18
    Hello,

    Please provide the requested details next time this issue happens: traceroutes from the server to your location and vice-versa(from your location to the server).

    Please understand that we can't just resolve an issue you have with no details if we can't actually see the issue form our side so we have to rely on the data you can provide in order to check for a possible problem.

    Thank you!

    Florian N
    Burstnet Engineering

Similar Threads

  1. BurstNet - After one week... no server yet
    By MarcioSantos in forum Dedicated Server
    Replies: 11
    Last Post: 10-04-2010, 11:32 AM
  2. BurstNET Scranton PA Facility - Power Issue
    By NWSTech in forum Providers and Network Outages and Updates
    Replies: 116
    Last Post: 05-28-2010, 09:15 AM
  3. Replies: 34
    Last Post: 04-06-2010, 01:55 PM
  4. Replies: 13
    Last Post: 10-29-2008, 09:34 PM
  5. Burstnet and downtimes
    By Jumper007 in forum Dedicated Server
    Replies: 5
    Last Post: 10-05-2008, 04:02 PM

Posting Permissions

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