flickr has a great API. I am using the flickr API to manage my photography portfolio website. I can organize everything (uploading, naming, ordering, etc.) using the flickr album tools and then just pull it into my site.

I have seen HTTP 500 return codes on webservers where outputting errors was suppressed, but some error occured anyway while processing the page.

Looked fine in a browser, but not an ideal case for SEO...

It's not just the main website.

beta.facebook.com graph.facebook.com developers.facebook.com

Mostly dead on port 80/443 or returning error codes.

Not really pointing to a faulty code push. Must be something more sinister going on.

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

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