4 ms·

It's a 500 error right now. sigh edit: ok, it's back.

• drubio 19y ago
  Yep, got a 500 error to! I thought the post was a joke...reloaded and realized it wasn't, got a clean page. If you reload the page 3-5 times in a few seconds, you get the 500 error page. Now those are serious scaling issues!
  • michaelneale 19y ago
    Afraid so. Rails got them to market, if they have to port to whatever, they should do it and I don't see why that is a big deal for anyone. I still like rails even if it can't scale to twitter.
  • michaelneale 19y ago
    WOW - you are right. I am seeing that right now. Thats terrible. They could do a server too busy message and it would be more correct I think.
  • joshwa 19y ago
    They lost a DB server: http://twitter.com/twitter_status http://twitter.com/twitter_status