Profile_bird

Hey there! backflip_status is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What are you doing? Join today to start receiving backflip_status's updates.

Already using Twitter
from your phone? Click here.

backflip_status

  1. Two problems: minor buffer issue in db : fixed / alerts system messed up (why it took a while for me to notice) : fixed.
  2. Your accounts are safe. We're getting false errors coming off the server which is why logins are failing. I am fixing now.
  3. Sorry about the internal errors this morning. Database got tied in a knot. All is fine now.
  4. Experiencing sporadic problems with our networking equipment which is effecting site uptime. We're working on a solution.
  5. We've rebooted the web server and everything seems to be working again.
  6. We're having issues with the web server. More later.
  7. Connectivity has been restored. But wow: http://tinyurl.com/7sbs24/0...
  8. http://tinyurl.com/dm5fke
  9. Our data center is down due to a fiber cut in SF. Thanks for the update @bifrosty2k
  10. @unitedlayer: all our servers off the net - unitedlayer.com as well - update please?
  11. The entire colo where backflip is housed is completely off the net. Please stand by for more info.
  12. Our support queue is all caught up. Thank you for your patience ;)
  13. We are a bit behind on the support queue. Please be patient; we will answer ALL the support questions.
  14. Reminder: please don't direct msg us on twitter for support. If you need help, email support@backflip.com.
  15. We're back. Sorry for the outage.
  16. We're heading over to the hosting facility to fix a misbehaving server.
  17. Something is pounding backflip like crazy the last few days. Probly another bot/script. Attempting recover and then block them.
  18. Oops, looks like we had a problem with our image server so the site looked weird overnight. Fixed now.
  19. We had a short outage this morning. It is corrected.
  20. Fixed internal errors that were occuring between 08:22 and 09:37 PST this morning. Sorry about that.