Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Facebook was down

facebook.com

Post reply on HN
Print view View original

241–250 of 294 posts

Re: Facebook was down

#241

Post by niubility »

Was completely dead in Australia. Down on both my local ISP and VPN to the National Research network. It was not a DNS issue as the IP Address is the same as it was during the outage.

"Host unreachable", maybe they took out the load-balancer?

- traceroute to star.c10r.facebook.com (2a03:2880:f00c:6:face:b00c:0:2)

1 redacted 2 ge-1-0-0.bb1.a.syd.aarnet.net.au (2001:388:1:5001::1) 107.649 ms 91.569 ms 91.814 ms 3 ae9.pe2.brwy.nsw.aarnet.net.au (2001:388:1:88::1) 91.981 ms 92.822 ms 103.957 ms 4 ae5.pe1.brwy.nsw.aarnet.net.au (2001:388:1:87::1) 92.447 ms 93.29 ms 101.182 ms 5 et-1-1-0.pe1.rsby.nsw.aarnet.net.au (2001:388:1:66::1) 94.606 ms 109.654 ms 91.987 ms 6 et-0-3-0.nsw-msct-bdr1.aarnet.net.au (2001:388:1:a3::2) 96.119 ms 92.032 ms 92.57 ms 7 6453.syd.equinix.com (2001:de8:6::6453:1) 99.204 ms 111.52 ms 190.499 ms 8 if-xe-0-3-1.3.thar1.1MH-Sydney.ipv6.as6453.net (2405:2000:ffd0::a) 90.392 ms 90.862 ms 92.174 ms 9 if-3-0-0.2.core1.PV4-Piti.ipv6.as6453.net (2405:2000:ffd0::1a) 232.07 ms 210.376 ms 163.293 ms 10 if-xe-3-1-1.10.tcore1.TV2-Tokyo.ipv6.as6453.net (2405:2000:ffb::22) 191.668 ms 200.129 ms 226.642 ms 11 if-ae2.2.tcore2.TV2-Tokyo.ipv6.as6453.net (2001:5a0:2200:300::2) 192.905 ms 191.953 ms 201.681 ms 12 if-ae6.2.tcore1.SVW-Singapore.ipv6.as6453.net (2405:2000:ffa0:100::49) 288.696 ms 279.671 ms 269.912 ms 13 if-ae11.2.thar1.SVQ-Singapore.ipv6.as6453.net (2405:2000:300:100::d) 264.938 ms 264.522 ms 266.912 ms 14 2405:2000:300:100::16 (2405:2000:300:100::16) 354.279 ms 349.7 ms 389.75 ms 15 ae2.bb02.sin1.tfbnw.net (2620:0:1cff:dead:beef::84c) 349.649 ms 348.205 ms 347.904 ms 16 ae0.bb01.hkg1.tfbnw.net (2620:0:1cff:dead:beef::1bdc) 349.552 ms 356.726 ms 348.74 ms 17 be6.bb01.pdx1.tfbnw.net (2620:0:1cff:dead:beef::5dd) 366.212 ms 368.99 ms 368.89 ms 18 be9.bb01.prn2.tfbnw.net (2620:0:1cff:dead:beef::f5) 365.81 ms 366.327 ms 366.598 ms 19 ae10.dr02.prn1.tfbnw.net (2620:0:1cff:dead:beef::1c27) 377.387 ms 365.613 ms 365.392 ms 23 * * * 24 ae10.dr02.prn1.tfbnw.net (2620:0:1cff:dead:beef::1c27) 387.156 ms !H 383.877 ms !H 374.672 ms !H

Re: Facebook was down

#244

Post by [deleted] »

kevan wrote: post #239
binoyxj wrote: post #231

Official update: "Facebook and Instagram experienced a major outage tonight from 22:10 until 23:10 PST. Our engineers identified the cause of the outage and recovered the site quickly. You should now see decreasing error rates while our systems stabilize. We don't expect any other break in service. I'll post another update within 30 mins. Thank you for your patience." https://developers.facebook.com/status/issues/393…

"The issue was resolved at 23:10 PST and the site stabilized shortly afterwards. Our internal and external monitoring shows that API requests are being served with normal latency and error rates, in all geographic regions. We are sorry for any inconvenience this may have caused you and the users of your apps." No hints there, guess we'll just have to wait for a full post-mortem to come out.

[deleted]

Re: Facebook was down

#245

Post by hrrsn »

eridius wrote: post #214
thrownaway2424 wrote: post #200

Earlier quoted context omitted.

Yeah, it doesn't seem like a DoS since facebook was reachable and serving error pages, and instagram was reachable and serving blank pages. It _does_ seem like an intrusion or other security incident though because I'd be surprised to learn that instagram shares lots of critical infrastructure with facebook. It seems more likely that someone hit the panic button for both sites.

Some sort of security incidence does seem more plausible than a DDoS, although I can't think of what would affect Facebook, Instagram, Tinder, Hipchat, and AIM simultaneously. I'm also having a hard time imagining what sort of security incident would result in Facebook deliberately shutting down their web presence, even for a few minutes. And all of the other potential attacks, such as DNS or CDN, seems like it a) wo…

Tinder uses Facebook's API heavily. It's not surprising it went down with Facebook

Re: Facebook was down

#247

Post by berkes »

munirusman wrote: post #65
gburt wrote: post #40

Earlier quoted context omitted.

$7.87 billion in 2013 / 365 days / 24 hours / 60 minutes / 60 seconds is about $250 a second. Edit: using more up to date data: $3,300,000,000 in the 3rd quarter of 2014 / (365/4) / 24 / 60 / 60 = $418.58

$1.5M an hour!!! But considering this is not the peak time in North America, it's should be little less.

A site like Facebook has a different profile though. More like email. If you cannot reach your mail, you'll read it at a later point.

When facebook comes up, people will catch up on "lost facebook time" most likely. Over the course of the week (or even day) it will most likely even out.

Re: Facebook was down

#248

Post by lmm »

MalcolmDiggs wrote: post #87

Quick, Google+ Engineers: take it down too! You don't want to fall behind.

Google+ was actually down as well, but fortunately neither of their users tried to log in during the outage.

Re: Facebook was down

#249

Post by yaeger »

jacko0 wrote: post #98

Yea, it could be Lizard Squad. https://twitter.com/LizardMafia . Facebook, Instagram, Tinder, AIM, Hipchat #offline #LizardSquad

Or it could be a power issue brought on by this little bigger than average blizzard that will hit the Boston area the hardest where, incidentally, Akamai is located.

But sure, couple of script kiddies might be responsible as well. It's usually one or the other.

Post reply on HN