View All Products
Compute
Storage
Networking
Databases
Services
Developer Tools
Industries
Pricing
Community
Engage With Us
Community ▶ Questions ▶ Fremont Connectivity Issue - 4/5/12
Log in to Ask a Question

Fremont Connectivity Issue - 4/5/12

general

Had an email from pingdom that my node was "down" for 10-15 minutes this morning and there is this on the status blog:

8:43am (EST): The issue has been resolved at this time, and connectivity has been restored for all affected Linodes.

7:34am (EST): We are aware of an issue affecting connectivity for Linodes in the Fremont datacenter. We are investigating and will post an update with more information shortly. There is no reason to issue reboot jobs at this time.

Is any additional information on this latest Fremont downtime going to be made available?

3 Replies

> Is any additional information on this latest Fremont downtime going to be made available?

Probably not. It's usually issue and then resolution.

Out of curiosity, what additional information would you want to get, and how would it assist you?

What caused the connectivity problems? Was it a Linode problem or and HE problem? Was anything done to help prevent the cause of the issue from happening again?

It's mostly curiosity, but more information provides for better transparency and confidence in Linode - something that people have asked for in the "Three things Linode should improve upon?" thread.

Well, I have another VM hosted on a different provider in HE's FMT1 and it didn't have any connection issues. I'm thinking it must have either been a problem on Linode's side (a router maybe?) or a problem on HE's side that somehow only affected Linode. I guess it could be Linode's bandwidth provider?

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Log in to Reply
Community Code of Conduct