Sorry, that was a database change I made. I make it use transactions in a more conservative way which ended up being a good bit slower so it was having trouble keeping up with people's bets. It should be much better now. I really need to track some metrics of bet to result time so that this sort of issue is more obvious to us.
Have you seen graphite?
http://graphite.wikidot.com/This page has a REALLY good example of how to see if your deploys messed anything up:
http://codeascraft.etsy.com/2010/12/08/track-every-release/