Twitter Screws Up Again.

Twitter is down again… this time a partial outage due to S3.

However, this time it’s their own fault for not using a caching proxy in front of S3.

This is just getting to the point where it’s embarrassing.

  1. Seems like a caching proxy would eliminate much of the benefit of using S3. You’d pay for (expensive) bandwidth out of Amazon and again out of your proxy.

  2. One wonders why they don’t use a CDN for users with high follower counts at least.

%d bloggers like this: