Akamai Edge DNS was down

Post by brentm » Thu, Jul 22, 2021, 4:42 PM UTC

knaik94 wrote: post #55

I am surprised financial institutions don't have any regulation for redundancy. The one that stuck out to me is the Navy Federal Credit Union website being down. I have not had any issues logging into mobile though for some of the reported sites.

Post by lowbloodsugar » Thu, Jul 22, 2021, 4:42 PM UTC

tyingq wrote: post #7

You can see this on a lot of sites right now. You get the Akamai style error with something like: Reference: #11.453a2f17.1393u44848484.3aee33433 At the bottom of a very bland looking error page.

Post by simonswords82 » Thu, Jul 22, 2021, 4:42 PM UTC

tootie wrote: post #64

simonswords82 wrote: post #14

I'm sick and tired of these types of services (I'm looking at you too Cloudflare) going down and taking otherwise healthy websites down with them.

It was fastly last time.

Post by davidjgraph » Thu, Jul 22, 2021, 4:43 PM UTC

sakisv wrote: post #49

davidjgraph wrote: post #15

Serious question, has anyone properly solved the issue of DNS as a single point of failure?

Depending on what point you draw the line of "single point of failure" you could use multiple providers for your dns. GOV.UK for example uses both aws and gcp for DNS

Post by brentm » Thu, Jul 22, 2021, 4:44 PM UTC

sathackr wrote: post #59

cbono1 wrote: post #38

Why would Google and Amazon be on the downdetector list or experiencing issues? Don't they have their own DNS / nameservers separate from Akamai?

because the way downdetector works is it just basically counts how many people are searching/visiting for down and if it's much higher than typical it flags the site as down. So if everyone searched "is google down" and visited the link on downdetector that was returned in the search, that would add to the downdetector count for that site. Downdetector doesn't actually know if the site is up or down.