As most regular users will be aware Twitter has had a number of issues over the last few days from incorrect Tweet counts, site availability, elevated errors to missing Tweets.
The missing Tweets from all pages are what’s concerning the gang at Fluid the most, but fear not Twitter have re-assured us on their status blog that they are not lost forever and will return soon:
“We’re currently experiencing site availability issues resulting from the failed enhancement of a new approach to timeline caching. Our infrastructure and operations engineers are currently working to resolve this. We’ll update you soon with an ETA.
10:17 PM PDT: Users may temporarily experience missing tweets from their timelines. They will be restored shortly.
11:51 PM PDT: We’re recovering from the site outage. Remember, users may temporarily experience missing or duplicate tweets from their timelines. Normal timelines will be restored shortly.”
We’re keeping our fingers crossed.
The problems over the last few days have caused a bit of concern. With a growing number of people not only using Twitter daily but relying on Twitter to be kept up to date with the latest news, industry developments or simply friends. The question on everyones lips today is ’should we depend on it’.
I am a huge Twitter fan, I not only encourage friends but businesses to use Twitter to engage with customers or clients, keep up to date with industry news and share their thoughts on hot topics. In some cases not having access to this information or to cusomers can be business critical.
The technical problems with Twitter can be more than a minor inconvenience for websites that have a Twitter feed installed. With Twitter being down this will disrupt these feeds and can potentially damage a website. Some businesses this morning will have to consider if having a live Twitter feed on their site is worth the potential disruption it can cause.
Here at Fluid we are hoping these issues get resolved as soon as possible but we would also like to know what procedures will be put in place to stop this happening again.
Link:
