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.
-
Spinn3r News- Spinn3r Hiring Five new Engineers (and growing rapidly)
- Spinn3r Hiring Support Engineer
- NYTimes, on Memetracker, and Spinn3r
- Spinn3r at Real Time Stream Crunchup, RSS Speedups, and Startup Discounts
- Spinn3r Hiring Crawl Engineer
- Spinn3r 3.1 - Now with Twitter Support and Social Media Ranking
- Blogfa.com (Iranian Blog Network) Down Due to Iranian Protests and Civil Unrest?
- Papers using Spinn3r Data from ICWSM 2009
- Spinn3r talk from ICWSM 2009
- Spinn3r 3.0: New Features, New Architecture, New APIs - More Goodness
Subscribe
-
Flickr
More Photos
July 20, 2008 at 7:33 pm
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.
July 28, 2008 at 2:45 pm
One wonders why they don’t use a CDN for users with high follower counts at least.