News for hackers. Stuff that matters.

A comment on Fastly Outage. Parent comment

Re:Fastly Outage by lpmitchell on Tuesday June 08, 2021 @06:11AM (#27432663)
The m.media-amazon.com domain (and a few other CDN'd domains that they use) are running through Fastly:

    nslookup m.media-amazon.com
    
    Name:  media.amazon.map.fastly.net
It is very interesting that they are not using CloudFront!
[ Parent | on HN ]
Re:Fastly Outage by cowsandmilk on Tuesday June 08, 2021 @06:50AM (#27433286)
really, m.media-amazon.com seems to have a very short TTL (showing 37 seconds right now) and has been weighted to cloudfront now.

Amazon is also known to use Akamai. Sure, Amazon relies heavily on AWS, but why should it surprise anyone that a retail website obsessed with instant loading of pages decides to use non-AWS CDNs if the performance is better.

Even if CloudFront became the default, I'm certain amazon.com would keep contracts with fastly and akamai just so they can weight traffic away from CloudFront in an outage.

[ Parent | on HN ]
Re:Fastly Outage by jamespo on Tuesday June 08, 2021 @06:38AM (#27433065)
Good to have 3rd party redundancy, time to fail over to something else now I'd think though.
[ Parent | on HN ]
Re:Fastly Outage by longwave on Tuesday June 08, 2021 @06:47AM (#27433229)
They already have:

  $ host m.media-amazon.com
  m.media-amazon.com is an alias for c.media-amazon.com.
  c.media-amazon.com has address 99.86.119.84
(which is a Cloudfront IP)
[ Parent | on HN ]
Re:Fastly Outage by xmdx on Tuesday June 08, 2021 @06:53AM (#27433330)
Yep they did exactly this and are now running on cloudfront
[ Parent | on HN ]
Re:Fastly Outage by tester34 on Tuesday June 08, 2021 @06:34AM (#27433018)
Why?
[ Parent | on HN ]