LinkedIn confirmed via Twitter that its site suffered an outage due to “a DNS issue.”
Our site is now recovering for some members. We determined it was a DNS issue, and we’re continuing to work on it. Thanks for your patience.
— LinkedIn Help (@LinkedInHelp) June 20, 2013
According to Downrightnow.com, LinkedIn’s service outage began around 6PM PST yesterday and is still continuing, though service has gradually resumed for some users.
Shortly after the outage began, App.net co-founder Bryan Berg wrote on his blog that the site’s DNS may have been hijacked–in other words, its domain name was redirected to a different IP address. In this case, LinkedIn’s traffic was re-routed to a network hosted by http://www.confluence-networks.com, which has phone numbers listed for both India and the U.S (UPDATE: the phone numbers for India have been removed, but they can still be seen in a cached version of the site). A spokesman reached at confluence-networks.com’s India number said that they are investigating why LinkedIn and Fidelity.com’s (see update below) nameservers have been redirected to their Web site.
This is potentially worrisome for LinkedIn users because, Berg writes, the site does not require SSL (secure sockets layer), which means that if you visited it over the last few hours, “your browser sent your long-lived session cookies in plaintext” and a third-party may now have access to your account information.
LinkedIn users may remember that nearly 6.5 million encrypted passwords were compromised in June 2012 when they were dumped onto a Russian hacker forum. That incident occurred around the same time mobile security researchers discovered that calendar entries made on LinkedIn’s iOS apps, including sensitive information like meeting locations and passwords, were transmitted back to LinkedIn’s servers without users’ knowledge.
A spokesman for LinkedIn said: “LinkedIn is experiencing some intermittent issues due to a DNS issue. Our team is working on it right now and we hope to have the issues resolved as soon as possible.”
EDIT: A reader directed us to this comment on Hacker News noting that Fidelity.com also suffered an outage earlier today. According to WhatsMyDNS.com, several of Fidelity.com’s nameservers appear to be routed to 220.127.116.11, which is also owned by confluence-networks.com, according to whois.domaintools.com. This may mean that Fidelity and LinkedIn both pay the same company for DNS services, but it’s impossible to tell from the information available. We’ve also emailed Fidelity.com for more information.