3 ms·
Since this was my group's bug (search infrastructure), I can shine a little light. "Ongoing" is in the article title, but the actual glitch started Thursday ni
by kmavm 16y ago
Since this was my group's bug (search infrastructure), I can shine a little light.
"Ongoing" is in the article title, but the actual glitch started Thursday night and continued into Friday morning. The title also makes it sound as though the entire Facebook API was broken; to clarify, we were returning stale results from stream search for several hours due to a software issue. This impacted clients like, e.g., kurrently.com or http://likebutton.me/?q=Bieber http://likebutton.me/?q=Bieber ; you would see results from the start of the incident, rather than up-to-date ones.
We've resolved the software issue, and put alerting in place to ensure that we notice sooner. In the future, if you depend on Facebook stream search and notice a flagrant failure like this, feel free to tell me about it: kma at facebook.com
- aaronbrethorst 16y agoI don't suppose the platform team has a platform status RSS feed or twitter account anywhere? It'd be nice to know about any and every issue occurring in the platform.
- kmavm 16y agoThere's the Facebook platform page here and its matching twitter account, but they're not really what you're looking for, are they? Some of my colleagues in platform are probably reading this; I'll ask around at work tomorrow. http://www.facebook.com/platform http://www.facebook.com/platform http://www.twitter.com/fbplatform http://www.twitter.com/fbplatform
- aaronbrethorst 16y agoNot quite, yeah. I'm looking for something more along the lines of http://status.twitter.com/ http://status.twitter.com/, specifically for the FB platform. thanks! Btw, pity you folks aren't looking for PMs in Seattle right now. I'd love to apply :)
- kmavm 16y agoIs this more helpful? http://developers.facebook.com/live_status http://developers.facebook.com/live_status
- aaronbrethorst 16y agoYes! I'd love to see the Graph API stuff integrated in there, too, though, but I bet you guys are already doing that :)
- donaldc 16y agoThere are two issues here, and your post only addresses what Facebook is doing about one of them. The issues are: (1) The fact that the API went down for an extended period of time. The post addresses this issue. (2) The fact that, according to the article, there was no official communication from Facebook about the issue for quite some time, even once they presumably knew about the issue and were working on fixing it. If Facebook wants to power web logins, this is an organizational/process issue that they must fix. What, if anything, is Facebook doing to address issue (2)?