5 ms·
Is Facebook down?
- elemenohpee 14y agoWoah, downforeveryoneorjustme says: Huh? http://www.facebook.com http://www.facebook.com doesn't look like a site on the interwho.
- acron0 14y agoYep, I checked there too. Also getting: Ping request could not find host www.facebook.com. Please check the name and try again.
- elemenohpee 14y agoDNS issue? I can ping some of their IP addresses but not others.
- aferrari_ 14y agoThe facebook.com ping in Brazil don't work.
- selectnull 14y agoBoth gmail and facebook down within an hour or so? Something going on?
- NathanKP 14y agoIt is up for me in Austin, Texas. Maybe a localized DNS issue?
- eric59 14y ago"ping: cannot resolve www.facebook.com: Unknown host" from Seattle.
- wronskian 14y agoDown for me here (UK, broadband provider is Eclipse) - looks like a DNS problem. isup.me also fails to resolve it.
- izietto 14y agoDown here (Rome, Italy)
- halayli 14y agowebmon.com (click on demo) shows it's been up from 4 locations with couple glitches in the past hour.
- trendspotter 14y agoNow webmon shows erros for Facebook, see here: https://webmon.com/#monitors/f/7 https://webmon.com/#monitors/f/7
- halayli 14y agoyep - just got an alert.
- trendspotter 14y agoWebmon says: "19 errors in the past 14 minutes"
- halayli 14y agoit seems it's a dns issue.
- jrajav 14y agoUp in Minneapolis, Minnesota.
- Yoni1 14y agoDown here (Israel).
- factorialboy 14y agoDown for me: Amsterdam
- extraio 14y agoI'm in Sacramento, CA - It's down at my house, but not at my neighbor's house (we're both on Comcast).
- wolfcat 14y agoStrange, yes downforeveryoneorjustme says it is not a site, but I can refresh FB just fine.
- BreadPaPa 14y agoDown in Chicago
- deleted 14y ago[deleted]
- dawolf- 14y agofacebook.com might still be in your DNS cache, something seems wrong with their domain registry. they use Markmonitor, any other Markmonitor domains affected?
- corford 14y agoJust tried dumping the cache, same result (I'm using Google's public dns servers as forwarders). I can however ping www.facebook.com from my servers in Germany (hetzner.net). Edit: sorry - thought you were replying to my post :)
- chrisu_de 14y agoThe HN effect;) Down for me in germany.
- kelleolsen 14y agoDown in Spain
- legosteentje 14y agoDown from Amsterdam ( IX5 ) And France ( OVH ), Track live tweets here http://facebook.twitterconsole.com http://facebook.twitterconsole.com
- corford 14y agoDon't know if it's yours, but well done on twitterconsole.com - very nice!
- snomad 14y agoDown for me in Sacramento.
- jamesjporter 14y agoDown for me in Chicago . . . its been a hell of a day for big web companies!
- phatbyte 14y agoDown in Portugal as well
- corford 14y agoDown here in France. Geo dns issue? I just tried using: http://www.analogx.com/cgi-bin/cgidig.exe?DNS=208.67.222.222&Query=www.facebook.com&Type=1&submit=Lookup http://www.analogx.com/cgi-bin/cgidig.exe?DNS=208.67.222.222... and that's claiming everything is fine (i.e. www.facebook.com exists and is a CNAME for star.facebook.com)
- chuhnk 14y agoSo www.facebook.com is not resolving but facebook.com does. Someone pushed a bad dns update?
- crypteasy 14y agoDown here in Rochester, New York. However I'm still able to have a conversation through the mobile Facebook Messenger app.
- conradfr 14y agoAt home I got nothing. On my server I get the layout but no content. It works fine for a friend on the same ISP as me. (France)
- zorkin 14y agoDown in London
- trendspotter 14y agoFacebook is still down here in Germany.
- pdknsk 14y agoIf it's down for you, try these IPs, to check whether is a DNS problem. ;; ANSWER SECTION: facebook.com. 1690 IN A 69.171.229.16 facebook.com. 1690 IN A 173.252.100.16 facebook.com. 1690 IN A 173.252.101.16 facebook.com. 1690 IN A 66.220.152.16 facebook.com. 1690 IN A 66.220.158.16 facebook.com. 1690 IN A 69.171.224.32
- chuhnk 14y agofacebook.com redirects to www.facebook.com which in turn does not resolve.
- Yoni1 14y agoYou can add those IPs as "www.facebook.com" in your hosts file and then the site becomes accessible.
- Yoni1 14y agoYup, that worked. However it's pretty useless as nobody else is online :)
- iddqd 14y agoQuerying Facebook's DNS servers directly shows something is definitely wrong: $ dig +short @b.ns.facebook.com www.facebook.com star.facebook.com. $ dig +short @b.ns.facebook.com star.facebook.com $
- trendspotter 14y agoDoesn't work for me. Facebook still not loading in Germany.
- dieds 14y agoWorks when adding these to hosts in the Netherlands. Pretty funny, almost everyone offline :O
- thomasbk 14y agoIt's back up for me in the Netherlands after doing ipconfig /flushdns in console, fwiw.
- revskill 14y agoDown here in Vietnam, Asia
- joecurry 14y agoUp in Auburn, AL - VPN'd through Montvale, NJ though
- TeMPOraL 14y agoDown in Kraków, Poland.
- niico 14y agoNot in Argentina.
- jayare0125 14y agodown for me in new jersey
- deleted 14y ago[deleted]
- inconditus 14y agoWorks fine in San Diego, California, but images aren't showing up.
- replayzero 14y agoDown in Kent, UK
- diedsj 14y agowth, how does the site go down EVERYWHERE???
- deleted 14y ago[deleted]
- ylem 14y agodown in Mumbai
- gzanitti 14y agoDown in Argentina.
- antoniopratas 14y agodown in Portugal.
- laander 14y agoA little investigation: Anon_Online notices of the event, OP probably high/drunk https://twitter.com/Anon_Online/status/278269562422697987 https://twitter.com/Anon_Online/status/278269562422697987 Odd-looking whois of facebook.com (notice the xxx domains and last update timestamp) http://pastebin.com/K4gAK3gi http://pastebin.com/K4gAK3gi Hmm
- legosteentje 14y agoThis looks like a DNS Problem, can't be anon.
- aes256 14y ago1) Anonymous are very unlikely to have anything to do with this; 2) There's nothing untoward about that whois report; you need to put the domain in speech marks to query the exact domain
- zackkitzmiller 14y agoThose DNS records are legit. the domains aren't facebook.com, facebook.com is at the beginning. Do a whois for anyone, and you'll get similar results. Edit, this is the google.com whois http://scrp.at/de0b2ad78907145d389c19b5cd61dc7b4d06e4e7 http://scrp.at/de0b2ad78907145d389c19b5cd61dc7b4d06e4e7
- lor11 14y agowont work for me ireland, so i tried americanproxy.org home page and log in option came up but no homepage after i put my password in, still worked tho after hiding my ip address!
- paganel 14y agoDown for me too in Romania/Bucharest.
- legosteentje 14y agoLatest WHOIS, could be my cache. http://pastebin.com/sEHtBTwp http://pastebin.com/sEHtBTwp
- tlwaddington 14y agoThe beta site (http://beta.facebook.com http://beta.facebook.com) hasn't been affected.
- mhielscher 14y agoHuh. As of 15 minutes ago, I was (successfully) pulling data from http://graph.facebook.com http://graph.facebook.com.
- robbie7 14y agoGuys, just go to https://beta.facebook.com/ https://beta.facebook.com/ and it works.
- FearMeForIAmDan 14y agoUntil you try to log in...
- jcmoscon 14y agoYou are right!
- yudhi 14y agodown in (Jogjakarta) Indonesia
- dag11 14y agoDown for me too. Philadelphia.
- harrychenca 14y agoit's back up
- geverett 14y agostill down for me in Berkeley CA
- Acen 14y agoTry flushing your DNS. Windows: CMD -> ipconfig /flushdns Still down in New Zealand, mind you.
- joey_muller 14y agoNot only was the site down for me in San Francisco but the Likes count buttons on several blogs were not loading. Can't the like button at least be cached?
- grumps 14y agoDown in DC!
- jcmoscon 14y agoI just checked and Facebook is dead here in NY.
- FearMeForIAmDan 14y agoIt seems like a SERVER has been taken down. Due to the large differences in location, it seems like a server(s) that service(s) multiple locations has/have been taken out. People are screaming Anon, but it could be a power outage and have the same effect. Either way, get ready to change some passwords.
- dawolf- 14y ago...and that's why you don't use Facebook Like buttons and Boxes all over your site. because it looks broken and full of errors now. Also, I don't want to know what this outage is doing to all the "Log in with Facebook" buttons right now. On a serious note: DNS issue. The authoritative nameservers a.ns.facebook.com and b.ns.facebook.com seem to be "set up" like this a the moment: *.facebook.com ->(cname) star.facebook.com -> no answer facebook.com still resolves the correct (?) IPs, but www.facebook.com, developers.facebook.com, graph.facebook.com all starting to die as your DNS cache expires. That's why it still might work for some at the moment while it really is broken.
- ssttoo 14y agoYou can load FB buttons and stuff without affecting your site at all, even if FB has DNS issues or is blocked by a firewall https://www.facebook.com/note.php?note_id=10151176218703920 https://www.facebook.com/note.php?note_id=10151176218703920 You load the JS SDK using the "fif" pattern. If it fails to load, none of the tags like <fb:like> etc get replaced by iframes, so no errors on the page. `DOMContentLoaded` and `onload` on your page fire as usual. It's as if the site doesn't even use FB widgets
- beagle3 14y agoJust be aware that doing that gives FB a chance to sniff cookies, referrer and other stuff on your own page. <sarcasm>Of course, FB is completely trustworthy with any data you give them access to, so nothing wrong will ever happen.</sarcasm>
- rb12345 14y agoMy cached results seem to have a cname of "star.c10r.facebook.com", which works: Non-authoritative answer: Name: star.c10r.facebook.com Addresses: 2a03:2880:10:8f01:face:b00c:0:1 31.13.72.23 Aliases: www.facebook.com
- craaash80 14y agoNow it resolves 31.13.64.23 ... was it planned?
- bluedevil 14y agoyou have to change your DNS nameservers. this works for me. primary: z.nic.de 194.246.96.1 Anycast (Berlin, Frankfurt/Main, Miami, Moscow, Sao Paulo) . secondary: google 8.8.4.4
- frookichalors 14y agodown in Nashville
- CarlHoerberg 14y agoOpenDNS still resolves the correct ip:s..
- zackmore 14y agoAlways down in China.
- spoko1001 14y ago69.171.229.16