Linode was down

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

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.

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

My existing SSH connections are still up, must be a DNS issue.

That explains the pingdom notification.<p>So, Digital Ocean is looking pretty good right now.<p>Edit: New Jersey data center.

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

Back up now. Linode has definitely been doing all they can to scare me off!

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

Must have been very short, I can access my sites, login to admin, and see all of Linode's pages as of 3:49 CDT

Pingdom detected no downtime for beeminder.com, hosted in Linode's New Jersey datacenter (I think).

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

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

DNS issues seem to be resolved now.

No downtime from London