Linode was down • Hacker News Board

Re: Linode was down

#11

Post by komrade » Mon, May 13, 2013, 9:01 PM UTC

Confirmed. I wasn't able to access my sites for like 5 minutes.

Re: Linode was down

#12

Post by JosephRedfern » Mon, May 13, 2013, 9:01 PM UTC

thekos wrote: post #10

From the #linode IRC channel, caker (CEO) states it was a segfault in bind. 13:53:14 caker@ : They operate completely independently, other than loading from the same zones. This looks to be a segfault in bind itself

Isn't having two independent name-servers supposed to prevent this kind of thing?

Re: Linode was down

#13

Post by kyrra » Mon, May 13, 2013, 9:03 PM UTC

singlow wrote: post #8

My external http monitoring had no issues accessing my websites on linode. I do not user their DNS though. [Edit: My nodes are in the Dallas Datacenter]

I use Linode DNS and I saw no issues from Pingdom either (also in dallas).

Re: Linode was down

#14

Post by zero0 » Mon, May 13, 2013, 9:06 PM UTC

kyrra wrote: post #13

singlow wrote: post #8

My external http monitoring had no issues accessing my websites on linode. I do not user their DNS though. [Edit: My nodes are in the Dallas Datacenter]

I use Linode DNS and I saw no issues from Pingdom either (also in dallas).

fwiw I use the dallas datacenter, linode dns, and pingdom said I was down for 11 minutes.

Re: Linode was down

#15

Post by yankcrime » Mon, May 13, 2013, 9:08 PM UTC

Didn't experience any loss of connectivity from my VPS hosted in their London DC.

Re: Linode was down

#16

Post by thekos » Mon, May 13, 2013, 9:12 PM UTC

JosephRedfern wrote: post #12

thekos wrote: post #10

From the #linode IRC channel, caker (CEO) states it was a segfault in bind. 13:53:14 caker@ : They operate completely independently, other than loading from the same zones. This looks to be a segfault in bind itself

Isn't having two independent name-servers supposed to prevent this kind of thing?

Appears that it cascaded across all of their nameservers. Seems like it could be an attack (remote or local DoS condition bug, since all users can create their own zones), or maybe just a random bug - hopefully they'll update us.

Re: Linode was down

#17

Post by gingerlime » Mon, May 13, 2013, 9:14 PM UTC

We have linodes in London, Newark, Atlanta, Dallas and Tokyo. All monitored by pingdom and none reported downtime... Our DNS is however hosted using Route53 and not Linode.

Re: Linode was down

#18

Post by jaibot » Mon, May 13, 2013, 9:14 PM UTC

That explains the pingdom notification.

So, Digital Ocean is looking pretty good right now.

Edit: New Jersey data center.

Re: Linode was down

#19

Post by jonmarkgo » Mon, May 13, 2013, 9:15 PM UTC

Haven't experienced any downtime for my servers...

Re: Linode was down

#20

Post by UnoriginalGuy » Mon, May 13, 2013, 9:30 PM UTC

The most interesting thing in this thread is frankly how many people seem to be using Pingdom.