Today, once again “Something is Technically Wrong” with Twitter. From my memory this, just happens to be the second time that Twitter has had to restart the caching system. According to the Twitter blog.

Part of our caching service required an unscheduled restart. That means a slow rebuilding of data. You may notice some of the normal browsing related features (such as pagination) are missing while we repopulate the caching service. This is so we can get it done quicker.

This seams to spell trouble for Twitter, while Mashable blames the Democrats, (Deep down so do I) I think this is something deeper in the works of Twitter. According to an uptime tracker Twitter is online 98% of the time, but it seams to go down at the worst times. This year Twitter crashed during the Macworld Keynote and whenever something significant happens Twitter starts to get slow.

Twitter likes to blame Ruby on Rails, their web framework, for all their downtime. Something Twitter likes to refer to as “scaling problems,” and there have even been rumors Twitter might rebuild the system completely with either Java or PHP.

But for now it looks like were stuck, Twitter is “stressing out” so it looks like this bug is temporarily prevalent for everyone.

* Matt is a guest blogger for JoeTech. He blogs for fun and profit at Duhh and SocialFeed.