Some of you may notice that your Twitter account has not backed up in a few days. This is the result of two issues. One is that the database system we use on Amazon Web Services is not ideal for the Twitter PDF generation process, so we are moving all of your tweets to a new database system. This is taking some time and causing some delays. It should be completed in a few more days.
The second issue is that we are getting a lot of “Over Capacity” responses from the Twitter API. Just as the Twitter website shows a fail whale sometimes, so does the API. When that happens, we can’t do a backup, and there is nothing on our side we can do to fix that. We have been in contact with Twitter’s platform team to find a better solution now that we so many users backing up Twitter. We will keep you posted on the results.
{ 3 comments }
Thank’s for the updates. I love your service and understand that these things happen. I appreciate you keeping everyone up-to-date though. Very open of you
Thanks for the update guys. Just to let you know that my last back up was the 27/28 of December for all services, not just Twitter. What’s the normal back-up frequency?
Thanks
Fred
Incentivize the upgrade path: current free users get weekly backups and if you want daily backups, upgrade to the paid service.
This will lower your API burden considerably.
Rich
BlogRodent
Comments on this entry are closed.