Quite the way to celebrate our 200 millionth check-in
So… yeah. An exhaustive explanation of last night’s downtime would be a bit redundant to yesterday’s post. In a nutshell, the same thing happened: an overloaded database, the solution to which again was manually redistributing check-in data to make sure no databases were overburdened and then rebooting the site, which we were finally able to do after nearly six hours of downtime. Unacceptably and frustratingly long, again.
We’re still working to implement the technical safeguards we outlined yesterday. We have some of those in place, and implementing the remainder is our top priority in the coming days. We’re hoping that these changes will help to stabilize things going forward.
Throughout the night, we tried to keep people updated through the @4sqsupport twitter feed and the new status.foursquare.com blog. Please let us know in the comments if that was helpful, and if there is anything we can do better.
Thanks for bearing with us.