Appears to be in Oregon, Southern Oregon. Mobile too.
This is awesome. Though I think this will be more of a time sink with employees F5ing until Facebook is back online.
Down from Los Angeles.
Down out of the VA/DC area also.
W. PA. too. Looks pretty widespread.
Works here (large .edu in Western PA). I would expect there to be rioting in the streets if FB was down.
Back up now (from Toronto) with the following IPs (184.108.40.206,2a03:2880:10:cf07:face:b00c:0:1)
Was down when I first checked.
% telnet www.facebook.com 443
telnet: connect to address 220.127.116.11: Connection refused
telnet: connect to address 2a03:2880:10:cf07:face:b00c:0:1: Connection refused
telnet: Unable to connect to remote host
Up here on Comcast in Tennessee.
It wasn't loading here in the UK either, although it's back now.
Down from intersellar orbit.
It's up in NYC from Cogent
traceroute to facebook.com (18.104.22.168), 30 hops max, 60 byte packets
1 pfsense.alloy.local (172.16.20.1) 0.308 ms 0.395 ms 0.259 ms
2 10.0.2.2 (10.0.2.2) 0.719 ms 0.602 ms 0.480 ms
3 * * *
4 * * *
5 * * *
6 gi0-0-0-18.209.nr11.b001578-0.jfk01.atlas.cogentco.com (22.214.171.124)
8.511 ms 4.990 ms 6.357 ms
7 gi2-12.mag01.jfk01.atlas.cogentco.com (126.96.36.199) 3.595 ms
gi2-12.mag02.jfk01.atlas.cogentco.com (188.8.131.52) 3.753 ms
gi2-12.mag01.jfk01.atlas.cogentco.com (184.108.40.206) 4.069 ms
8 te0-2-0-0.rcr22.jfk01.atlas.cogentco.com (220.127.116.11) 6.441 ms
te0-6-0-0.rcr22.jfk01.atlas.cogentco.com (18.104.22.168) 6.227 ms
te0-2-0-0.rcr22.jfk01.atlas.cogentco.com (22.214.171.124) 3.649 ms
9 be2355.ccr21.jfk02.atlas.cogentco.com (126.96.36.199) 4.787 ms
be2356.ccr22.jfk02.atlas.cogentco.com (188.8.131.52) 4.290 ms
be2358.mpd22.jfk02.atlas.cogentco.com (184.108.40.206) 4.108 ms
10 be2150.mpd21.dca01.atlas.cogentco.com (220.127.116.11) 9.557 ms 9.228
ms be2151.mpd22.dca01.atlas.cogentco.com (18.104.22.168) 8.767 ms
11 be2112.ccr41.iad02.atlas.cogentco.com (22.214.171.124) 11.265 ms 12.065
ms be2113.ccr41.iad02.atlas.cogentco.com (126.96.36.199) 13.096 ms
12 xe-11-2-1.edge3.Washington4.Level3.net (188.8.131.52) 10.781 ms 11.072
ms 13.606 ms
13 184.108.40.206 (220.127.116.11) 10.876 ms 9.413 ms 9.890 ms
14 be2.bb02.iad3.tfbnw.net (18.104.22.168) 27.637 ms be3.bb01.iad3.tfbnw.net
(22.214.171.124) 24.573 ms 23.740 ms
15 ae12.bb04.frc3.tfbnw.net (126.96.36.199) 23.398 ms
ae17.bb04.frc3.tfbnw.net (188.8.131.52) 23.474 ms ae12.bb03.frc3.tfbnw.net
(184.108.40.206) 23.161 ms
16 ae87.dr04.frc1.tfbnw.net (220.127.116.11) 24.017 ms
ae90.dr02.frc1.tfbnw.net (18.104.22.168) 25.780 ms
ae89.dr04.frc1.tfbnw.net (22.214.171.124) 37.919 ms
17 * * *
18 * * *
19 edge-star-shv-13-frc1.facebook.com (126.96.36.199) 26.808 ms 25.720
ms 25.618 ms
www.facebook.com is an alias for star.c10r.facebook.com.
star.c10r.facebook.com has address 188.8.131.52
star.c10r.facebook.com has IPv6 address 2a03:2880:f011:301:face:b00c:0:1
star.c10r.facebook.com mail is handled by 10 msgin.t.facebook.com.
facebook.com. 453 IN A 184.108.40.206
So perhaps different dns entries are just cached depending on geographical
[image: Inline image 1]
And Darius wins the Internet for today.
PS: What do you pay for a loop up there?
it totally was not down from interstellar orbit. You didn't have time to
tell because rtt from interstellar space is 11 hours minimum, which is even
worse than some cellular data operators. Pants on fire.
Can anyone confirm if it was down in the MD/DC, Northern Oregon, Eastern PA
and Palo Alto areas? I'm dying to know.
What would I be doing with a load balancer as an alternative time-waste for Facebook?
Or are you suggesting that I would amuse myself by lowering the brightness of my keyboard backlight?
I am confused by your comment.
Really? I'm in the UK too (London) and it was fine for me the whole time. I do have an IPv6 tunnel to HE though, so maybe it was fine on v6 and only down via v4??
Yep, completely out for me here. Couldn't even get as much as an error page most of the time, although I did briefly get a generic message saying "Sorry, something went wrong. We're working on getting this fixed as soon as we can".
I'm on Virgin Media cable for IPv4 and a SIXXS tunnel hosted by Goscomb in London for IPv6.
Multiple people in a UK techy IRC channel that I frequent were also reporting it as down at the time.