Two things we’d like to share with you:

1.) We’ve been experiencing difficulties fetching data the past Mondays and Tuesdays.
Unfortunately this led to missing data for some of you. Having thought to have fixed the issue it reoccurred this week. We are sorry for the inconvenience and wanted you to know that we will continue to finding a solution.

2.) Facebook made changes to their API leaving a gap in data for Facebook pages.
We just came to know this fact and are going to investigate asap. We will keep you updated.

With our development-team still being busy developing for one of our clients, we are anxious to find a quick solution. Thanks for hanging in there!

Regards,

Your TwentyFeet Support Team

we are happy to announce that we’ve took some actions that led to a significant boost in performance for TwentyFeet. One of these activities was the migration of our databases to Amazon RDS. Unfortunately we weren’t able to do so without a short downtime for approx. 15% of our users. If you were effected by this downtime we would like to thank you for your patience and understanding!

Furthermore we’ve upgraded the server capacity of our frontend-servers and made improvements to the load-balancing. This step was pretty important to make sure that we are able to fast react on increasing loads and assure fast response times.

Thanks,

TwentyFeet-Team

Dear TwentyFeet users and friends,

As you might have recognized we had a data generation issue that lasted for two days. The problem originated from an overflow of the queue that is holding all kinds of tasks (e.g. processing of data that has been gathered from Twitter or other services). Although there were adding additional servers-power to crank up the performance, the number of tasks didn’t go down. After we’ve assured the messages to be dequeued, all users were able to access their data around 10am CET.

Parallel to this event we recognized that some data wasn’t aggregated correctly. This behavior can be seen in peaks that are shown on the chart (as seen on the screenshot) or in the effected users activity stream. We could observe this behavior with some Twitter- and Bit.ly-accounts. Unfortunately we couldn’t identify any regularities yet. If your account is effected by this behavior, we would like to apologize for the discrepancy and therein resulting inconvenience!

At this point we don’t have a feature to delete incorrect data. If you are interested in this feature, we’d ask you to vote in the TwentyFeet-Uservoice and leave your comments and ideas:

http://bit.ly/ywYuFX

Once again, thank you very much for your understanding. We are open for questions any time. You can reach us via Twitter, Facebook or the built in Help-button.

Thanks,

Your TwentyFeet-Team