Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


DelimiterVPS Atom Dedi down
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

DelimiterVPS Atom Dedi down

So... it looks like my DelimiterVPS Atom Dedicated has been down for the past 12 hours.

I submitted a ticket around 8 hours ago when I became aware of the problem... 2-3 hours later, I got a reply asking me to power cycle the server (which I had done already). They then referred my problem to the DC... after 12 hours of downtime already.

Network status shows no signs of issues, other than a packet dropping issue which was "rectified".

Power status shows "on" but all attempts to connect to the server times out.

Is anyone else having a similar downtime currently?

Comments

  • I don't have an ATOM setup but earlier today there was a 4 minute outage that was part of the issue you spoke of I'm guessing, I was literally back online within 5 minutes.

    I opened a ticket with outages, crew explained some things were wonky and that there would be a RFO later, never saw the RFO myself, but then again I'm online so haven't been looking.

    I'd say open a ticket with the outage dept. response time was good.

  • Monsta_AUMonsta_AU Member
    edited September 2014

    I am also down, however I am coming through their Level3 transit like @tsangk is. Looks like their Level3 transit is down:

    11 200 ms 201 ms 201 ms ae-3-3.ebr3.dallas1.level3.net [4.69.132.78] 12 * * * Request timed out. 13 217 ms 201 ms 201 ms ae-2-3508.edge4.atlanta2.level3.net [4.69.150.141] 14 230 ms 248 ms 230 ms yomura-asso.edge4.atlanta2.level3.net [4.34.137.134] 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out.

    My ticket has been open for 4 hours without response. Seems pretty normal in my experiences with them. So much for their 24x7 Support.....

    @MarkTurner has said he is responsible for the network - would love to hear what is going on, and why other routes are not being advertised.

  • Yes down here for Atom.

  • My Atom is down now too. X5120(?) has restarted too.

  • @Monsta_AU said:
    My ticket has been open for 4 hours without response. Seems pretty normal in my experiences with them. So much for their 24x7 Support.....

    24/7 support doesn't mean you'll get a reply in 5 minutes...

  • Monsta_AUMonsta_AU Member
    edited September 2014

    @ATHK said:
    24/7 support doesn't mean you'll get a reply in 5 minutes...

    Never said I wanted a 5min response. However an "ok, we are investigating" should happen with 4 hours.

    They have finally gotten back to me after 9 hours (after 8am, so it appears that nobody is staffing the outages queue overnight) and they are blaming the server.

    That appears to be completely wrong. I have the next IP after @tsangk, and he has another that be bought 3 months later. Both are down.

    Either it is an internal router or major distribution switch which has fallen over, but it is quite disconcerting to know that they have no clue about it almost 16 hours ago which is when UptimeRobot tells me it went down and has been unreachable since.

  • @Monsta_AU said:
    Never said I wanted a 5min response. However an "ok, we are investigating" should happen with 4 hours.

    Yeah, exactly. And while I did get an acknowledgement 2-3 hours after my ticket, surely they would have some mechanism / status checking system to see that an entire cluster of dedicated servers are offline. And surely it doesn't take 12 hours for DelimiterVPS to request their DC/upstream to take a look at what's going on?

  • catalystiumcatalystium Member
    edited September 2014

    Just checked, mine is down as well.

    Unreachable via ping or trace (mine is also going through level 3):

    1  192.168.1.1 (192.168.1.1)  0.564 ms  1.492 ms  1.474 ms
     2  192.168.0.1 (192.168.0.1)  3.438 ms  3.422 ms  3.401 ms
     3  10.213.52.1 (10.213.52.1)  15.357 ms  15.341 ms  15.322 ms
     4  dtr01lenrnc-tge-0-1-1-2.lenr.nc.charter.com (96.34.67.140)  15.302 ms  15.282 ms  16.229 ms
     5  dtr02hckrnc-tge-0-3-0-7.hckr.nc.charter.com (96.34.67.45)  16.220 ms dtr02hckrnc-tge-0-3-0-2.hckr.nc.charter.com (96.34.66.241)  16.189 ms  16.168 ms
     6  crr02hckrnc-bue-20.hckr.nc.charter.com (96.34.64.50)  16.137 ms  11.582 ms  18.762 ms
     7  crr12spbgsc-bue-10.spbg.sc.charter.com (96.34.64.49)  20.724 ms  21.703 ms  21.685 ms
     8  bbr01spbgsc-bue-4.spbg.sc.charter.com (96.34.2.50)  27.648 ms  23.622 ms  22.598 ms
     9  bbr01gnvlsc-bue-1.gnvl.sc.charter.com (96.34.0.43)  28.572 ms *  28.531 ms
    10  * * *
    11  * * *
    12  ae-2-3508.edge4.Atlanta2.Level3.net (4.69.150.141)  16.906 ms  16.782 ms  27.756 ms
    13  YOMURA-ASSO.edge4.Atlanta2.Level3.net (4.34.137.134)  27.746 ms  27.732 ms  27.702 ms
    14  * * *
    15  * * *
    

    EDIT: Did a restart through the control panel and seems to be working now.

  • "We are aware of 9 different Atom issues at the moment, spread across 7 racks. Only one rack has 2 Atoms down in it. We're waiting for the DC team to get to the bottom of it. Its not a specific group of IPs and not a specific VLAN."

    "They are going to check the hardware of these servers in case the power surge last evening has damaged the PSUs on them."

  • @tsangk said:
    And while I did get an acknowledgement 2-3 hours after my ticket, surely they would have some mechanism / status checking system to see that an entire cluster of dedicated servers are offline. And surely it doesn't take 12 hours for DelimiterVPS to request their DC/upstream to take a look at what's going on?

    Pay peanuts, get monkeys. Service costs money to provide.

  • While i think the atom and x5150 is great deal for the price, And the X5150 very useful for me, I had to cancel it - because in period of 4ish weeks I had 4 outages which spanned several hours. I needed the box for more reliable purposes. Support told me that there is no SLA.

  • Monsta_AU said: why other routes are not being advertised.

    We have had NO BGP disturbances. Your traceroute shows that packets destined for your server arrived at one of our routers in Atlanta (4.34.137.134 which is our side of the /30) and then dropped.

    Your server was down and therefore the internal OSPF route for your server was no longer propagated within the internal network. So these routers had no idea where to send your packets and therefore returned an ICMP unreachable.

    The actual issue yesterday started around 17:05 EDT when there was a lightning strike on Georgia Power's grid. Georgia Power stated:

    Yes - this event was weather related. We had lightning strikes occur on our lines, at
    approximately 5:05 pm yesterday afternoon. We did not see widespread outages for
    the area, but did experience a voltage fluctuation as a result of the lightning.

    The reality was that two phases surged within seconds of each other which caused some blade chassis to try to balance power from three phases to two phases and then less than second later when the second phase failed, balance onto the third phase. I estimate about 75-100 blades rebooted last evening and approximately 40 Atom servers rebooted.

    The blade servers that rebooted, immediately came back online and with the exception of one blade server required no hardware intervention on our part

    Half a dozen Atom servers required replacement power supplies which has been done during the day today.

  • Caveman122Caveman122 Member
    edited September 2014

    I love Mark's answers, simple, right to the point. I wish delimiter have a channel to display this kind of answers/announcements. It certainly would help easy people's minds and reduce the number of tickets.

    https://status.online.net

    http://status.ovh.com/

  • MarkTurner said: We have had NO BGP disturbances. Your traceroute shows that packets destined for your server arrived at one of our routers in Atlanta (4.34.137.134 which is our side of the /30) and then dropped.

    By the look of the DNS name, it appeared to me that it was not your side. Thanks for clearing that up.

    MarkTurner said: Half a dozen Atom servers required replacement power supplies which has been done during the day today.

    Yes, mine is back up now.

  • The transit provider will provide a /30 in most cases for an interconnect:

    .133 = Level 3's router
    .134 = Yomura's router

  • mee too for Dedicated server HP BL460C

Sign In or Register to comment.