Page 1 of 2 12 LastLast
Results 1 to 40 of 64
  1. #1
    Join Date
    Aug 2002
    Location
    Chile
    Posts
    43

    burst.net TimedOut

    I cannot connect to burst.net
    And http://centralops.net/co informs:

    Traceroute

    Tracing route to burst.net [66.96.192.201]...
    hop rtt rtt rtt ip address fully qualified domain name
    1 0 0 0 216.46.228.229 port-216-3073253-es128.devices.datareturn.com
    2 0 0 0 64.29.192.145 port-64-1949841-zzt0prespect.devices.datareturn.com
    3 17 0 0 64.29.192.226 daa.g921.ispb.datareturn.com
    4 0 0 0 168.215.241.133 hagg-01-ae0-1001.dlfw.twtelecom.net
    5 0 0 0 66.192.253.124 core-02-ge-3-1-0-504.dlfw.twtelecom.net
    6 0 0 0 66.192.246.53 peer-02-so-0-0-0-0.dlfw.twtelecom.net
    7 0 0 0 206.223.118.48 ge3-0.cr02.dal01.pccwbtn.net
    8 40 41 42 63.218.30.45 pos5-2.cr01.phl02.pccwbtn.net
    9 * * *
    10 * * *
    11 * * *
    12 * * *

    Trace aborted
    Service scan
    FTP - 21 Error: TimedOut
    SMTP - 25 Error: TimedOut
    HTTP - 80 Error: TimedOut
    POP3 - 110 Error: TimedOut
    NNTP - 119 Error: TimedOut

    -- end --

  2. #2
    same here.. no ping

  3. #3
    Join Date
    Aug 2002
    Location
    Chile
    Posts
    43
    Now is ok.

  4. #4
    Dead again?

    Pinging 66.197.173.201 with 32 bytes of data:

    Request timed out.
    Reply from 66.197.173.201: bytes=32 time=1132ms TTL=52
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 66.197.173.201: bytes=32 time=1150ms TTL=52
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 66.197.173.201: bytes=32 time=1105ms TTL=52
    Request timed out.
    Reply from 66.197.173.201: bytes=32 time=1074ms TTL=52
    Request timed out.
    Reply from 66.197.173.201: bytes=32 time=1131ms TTL=52
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 66.197.173.201:
    Packets: Sent = 23, Received = 5, Lost = 18 (78% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1074ms, Maximum = 1150ms, Average = 1118ms
    Control-Break

  5. #5
    Join Date
    Oct 2004
    Location
    Celebration, Florida
    Posts
    209
    Same here...

  6. #6
    Join Date
    Oct 2003
    Location
    Georgetown, Ontario
    Posts
    1,761
    Down here as well.

  7. #7
    Packets: Sent = 20, Received = 7, Lost = 13 (65% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 125ms, Maximum = 126ms, Average = 125ms

  8. #8
    Join Date
    Aug 2002
    Location
    Chile
    Posts
    43
    AGAIN!

    hop rtt rtt rtt ip address fully qualified domain name
    1 0 0 0 216.46.228.229 port-216-3073253-es128.devices.datareturn.com
    2 0 0 0 64.29.192.145 port-64-1949841-zzt0prespect.devices.datareturn.com
    3 0 0 0 64.29.192.226 daa.g921.ispb.datareturn.com
    4 0 0 0 168.215.241.133 hagg-01-ae0-1001.dlfw.twtelecom.net
    5 0 0 0 66.192.253.124 core-02-ge-3-1-0-504.dlfw.twtelecom.net
    6 0 0 0 66.192.246.53 peer-02-so-0-0-0-0.dlfw.twtelecom.net
    7 0 0 0 206.223.118.48 ge3-0.cr02.dal01.pccwbtn.net
    8 41 41 40 63.218.30.45 pos5-2.cr01.phl02.pccwbtn.net
    9 37 37 37 63.218.31.6 hostnoc.ge3-0.2.cr01.phl02.pccwbtn.net
    10 * 44 43 66.197.191.45 ge-7-0-ctsi.rtr0.scra1.hostnoc.net
    11 44 43 * 66.197.191.82 ge-rtr1.scra1.hostnoc.net
    12 * * *
    13 * * *
    14 * * *
    15 * * *

    Trace aborted

  9. #9
    Join Date
    Oct 2004
    Location
    Celebration, Florida
    Posts
    209
    Anyone know what's up or have an eta? This is the forth outage in eight days.

  10. #10
    Did you find out what the problem was

  11. #11
    I just got confirmation it was a Ddos attack - all should be sorted now

  12. #12
    Seems down yet again here I can't ping burst.net or my server located within. Anyone else?

  13. #13
    Join Date
    Apr 2002
    Location
    Here?
    Posts
    2,560
    All good here.

  14. #14
    Join Date
    Dec 2002
    Location
    Canada
    Posts
    89
    yep, down again here

  15. #15
    Join Date
    Aug 2004
    Posts
    1,461
    Down here and from two proxy locations

  16. #16
    Originally posted by thomas.smith
    Down in Europe, however, up in the USA.
    Yeah I'm in Scotland... this is for sure?

  17. #17
    Join Date
    Aug 2004
    Posts
    1,461
    Originally posted by mjzz
    Yeah I'm in Scotland... this is for sure?
    It is really strange. First it was up in the USA but down in Europe. Then it went down in the US, too. Now it is up in the US but down in Europe...

  18. #18
    Join Date
    Sep 2004
    Posts
    53
    Down in NZ and USA.
    Burst any information please?

  19. #19
    Join Date
    Aug 2004
    Posts
    1,461
    Seems to go up and down in the US but in Europe it is constantly down right now.

  20. #20
    Join Date
    Nov 2004
    Location
    Oklahoma
    Posts
    13
    Its still down in the US, timeouts on there support forum and my server.

  21. #21
    Join Date
    Jun 2002
    Location
    Texas
    Posts
    7,953
    Down from Texas also.

  22. #22
    Join Date
    Aug 2004
    Posts
    1,461
    I can occasionally reach it from EV1 but from 1&1 in Europe and my home connection it says down.

  23. #23
    Join Date
    Aug 2004
    Posts
    1,461
    Pings above 2000 from EV1 now and 75% packet loss.

  24. #24
    Join Date
    Aug 2004
    Posts
    1,461
    I am now getting pings around 300 and no packet loss from EV1. Still 90% packet loss from my home connection and 1&1

  25. #25
    Join Date
    Dec 2002
    Location
    Canada
    Posts
    89
    forum.burst.net is down too...

  26. #26
    I can ping my machine but cannot acccess any ports FTP/HTTP etc

  27. #27
    Join Date
    Aug 2004
    Posts
    1,461
    Hm... Can ping it from EV1 but can not reach FTP or Apache from EV1 either. And it is 80% dead from my home connection and 1&1

  28. #28
    Join Date
    Aug 2004
    Posts
    1,461
    Can ping from 1&1 now but no Apache/FTP.

  29. #29
    Traceroute also fails, but ping doesn't So they may be getting attacked and are blocking most everything.

  30. #30
    Join Date
    Aug 2004
    Posts
    1,461
    They do not seem to block it as 1&1 can now reach Apache occasionally. I guess they are under attack or having a hardware problem.

  31. #31
    Join Date
    Sep 2004
    Posts
    53
    any one heared from Burst yet? Customers are asking how long is it going to be!
    I don't know what to say

  32. #32
    A little while yet! -- no I haven't heard from them.

  33. #33
    Join Date
    Aug 2004
    Posts
    1,461
    Just tell them it's a network problem, the DC is working on it and you will contact them again once you know more.

  34. #34
    Join Date
    Aug 2004
    Posts
    1,461
    Must have been 35 minutes now.

  35. #35
    Join Date
    Sep 2004
    Posts
    53
    Originally posted by thomas.smith
    Must have been 35 minutes now.
    An hour would be fine, just that we know. It is really bad when we are left in the dark with no word whatsoever.

  36. #36
    Join Date
    Aug 2004
    Posts
    1,461
    I hope most of my customers are sleeping now. It is 12 AM in the US (east coast)... I hope they are all asleep.

  37. #37
    Official Word From Burst

    Network is being flooded. Should return to normal in 10 to 15 minutes.

    Fred T

  38. #38

    no one on chat either

    AIM chat was good, since atleast burst could inform customers on the nature of the problem - but seems like there is no on chat now. hope it gets sorted out soon. my clients are already at work trying to check their mails!

    SN

  39. #39
    2.30pm here

  40. #40
    Join Date
    Aug 2004
    Posts
    1,461
    Still down here has been 70 minutes now.

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
  •