...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.

You 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

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

Just 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>

My 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

Woah, downforeveryoneorjustme says: Huh? http://www.facebook.com doesn't look like a site on the interwho.

Yep, I checked there too. Also getting:

Ping request could not find host www.facebook.com. Please check the name and try again.

DNS issue? I can ping some of their IP addresses but not others.

The facebook.com ping in Brazil don't work.

A little investigation:

Anon_Online notices of the event, OP probably high/drunk 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

Hmm

Those 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

1) 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

This looks like a DNS Problem, can't be anon.

If 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

Querying 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
  $

Yup, that worked. However it's pretty useless as nobody else is online :)

Works when adding these to hosts in the Netherlands. Pretty funny, almost everyone offline :O

It's back up for me in the Netherlands after doing ipconfig /flushdns in console, fwiw.

facebook.com redirects to www.facebook.com which in turn does not resolve.

You can add those IPs as "www.facebook.com" in your hosts file and then the site becomes accessible.

Doesn't work for me. Facebook still not loading in Germany.

Guys, just go to https://beta.facebook.com/ and it works.

Until you try to log in...

You are right!

Both gmail and facebook down within an hour or so? Something going on?

Cyberattack! Don't panic! Everyone make your way to your nearest cyber-shelter! ;-)

Prepping for the end of the world next Friday ;)

Down here in France. Geo dns issue?

I just tried using: 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)

It 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.

So www.facebook.com is not resolving but facebook.com does. Someone pushed a bad dns update?

Strange, yes downforeveryoneorjustme says it is not a site, but I can refresh FB just fine.

facebook.com might still be in your DNS cache,

something seems wrong with their domain registry. they use Markmonitor, any other Markmonitor domains affected?

Just 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 :)

Down from Amsterdam ( IX5 ) And France ( OVH ), Track live tweets here http://facebook.twitterconsole.com

Don't know if it's yours, but well done on twitterconsole.com - very nice!

It is up for me in Austin, Texas. Maybe a localized DNS issue?

Huh. As of 15 minutes ago, I was (successfully) pulling data from http://graph.facebook.com.

At 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)

Down here in Rochester, New York. However I'm still able to have a conversation through the mobile Facebook Messenger app.

Latest WHOIS, could be my cache.

http://pastebin.com/sEHtBTwp

The beta site (http://beta.facebook.com) hasn't been affected.

Down for me here (UK, broadband provider is Eclipse) - looks like a DNS problem. isup.me also fails to resolve it.

I'm in Sacramento, CA - It's down at my house, but not at my neighbor's house (we're both on Comcast).

Up in Minneapolis, Minnesota.

Down for me in Chicago . . . its been a hell of a day for big web companies!

"ping: cannot resolve www.facebook.com: Unknown host" from Seattle.

wont 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!

Works fine in San Diego, California, but images aren't showing up.

you 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

Down here (Rome, Italy)

Up in Auburn, AL - VPN'd through Montvale, NJ though

Now it resolves 31.13.64.23 ... was it planned?

I just checked and Facebook is dead here in NY.

OpenDNS still resolves the correct ip:s..

Facebook is still down here in Germany.

The HN effect;) Down for me in germany.

webmon.com (click on demo) shows it's been up from 4 locations with couple glitches in the past hour.

Now webmon shows erros for Facebook, see here:

https://webmon.com/#monitors/f/7

yep - just got an alert.

Webmon says: "19 errors in the past 14 minutes"

it seems it's a dns issue.

Down for me too in Romania/Bucharest.

Down for me too. Philadelphia.

Down here in Vietnam, Asia

Down for me in Sacramento.

Down in Portugal as well

Down in Kraków, Poland.

Down for me: Amsterdam

Always down in China.

Down here (Israel).

Down in Argentina.

Not in Argentina.

wth, how does the site go down EVERYWHERE???

Down in Kent, UK

Down in Chicago

Down in UK

Down in Belgium :(

Down in Malaysia :)

Down in London

69.171.229.16

Down in Spain

down in (Jogjakarta) Indonesia

Down in DC!

down for me in new jersey

down in Nashville

down in Portugal.

down in Mumbai

it's back up

still down for me in Berkeley CA

Not 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?

Try flushing your DNS. Windows: CMD -> ipconfig /flushdns

Still down in New Zealand, mind you.