3 ms·
Amazon being down surely points to something other than Fastly being the cause?
by unfunco 5y ago
Amazon being down surely points to something other than Fastly being the cause?
- austinjp 5y agoI just had a look at amazon.co.uk and most assets fail to load, the browser debug console is full of 503 errors. Picking one at random, it's fastly: $ nslookup images-eu.ssl-images-amazon.com Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: images-eu.ssl-images-amazon.com canonical name = m.media-amazon.com. m.media-amazon.com canonical name = media.amazon.map.fastly.net. Name: media.amazon.map.fastly.net Address: 199.232.177.16 Name: media.amazon.map.fastly.net Address: 2a04:4e42:1d::272
- mpitt 5y agoAmazon.com uses Fastly https://www.streamingmediablog.com/2020/05/fastly-amazon-homepage.html https://www.streamingmediablog.com/2020/05/fastly-amazon-hom...
- jfny 5y ago[deleted]
- richardwhiuk 5y agoThey will use S3, but they need a CDN in front. Surprised they don't use CloudFront - maybe that's what they've failed over to.
- macintux 5y agoApparently they switched from CloudFront after determining Fastly was faster for this use case. CloudFront is focused on large streaming services, not small HTTP resources.