Akamai believes they have it fixed. We've seen our traffic return to normal. https://twitter.com/Akamai/status/1418251400660889603
hmmm does not appear fixed here in the Midwest
Akamai Edge DNS was down
111–120 of 229 posts
Re: Akamai Edge DNS was down
#112Earlier quoted context omitted.
I switched to BitWarden and haven't looked back. You can use it on the phone and pc (browser). As well as a desktop client.
And with vaultwarden you can go self hosted with a very lightweight server written in rust.
Switched to vaultwarden at work for password management, only have minor gripes so can recommend.
Re: Akamai Edge DNS was down
#113I 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.
this is prime shit Hacker News says right here. Wait until you learn banks close on Sunday. Or have maintenance windows for their website, ATM, etc.
Re: Akamai Edge DNS was down
#114Absolutely amazing how many billion $+ companies are single homed for DNS.
I wonder how much they spend on multi-AZ redundant architectures...
Re: Akamai Edge DNS was down
#115Serious question, has anyone properly solved the issue of DNS as a single point of failure?
The problem isn't DNS though, is it? The problem is that people don't necessarily use the redundancies on DNS? The whole reason it takes a domain 24h to fully work with DNS is because it propagates the information other DNS servers, thus making not be a centralized service.
DNS doesn't 'propagate' except in the very limited case of zone-transfer publication, which... nobody really relies on these days. Registrars tell you it takes 24 hours to propagate to stop you from complaining to them about your ISP's DNS caching policy. The reality is: recursing DNS servers have caches, they respect TTLs, and for the most part that means that DNS changes should fully wash through within an hour for most changes (less if you keep your TTLs shorter).
Re: Akamai Edge DNS was down
#116Just got booted out of Netflix on the PS4 because the console could no longer connect to Sony's license server. Netflix was working just fine by the way.
Yup, I learned Hulu on Xbox One relies heavily on some Microsoft authentication during a recent Office 365 or Azure outage (not sure which).
Re: Akamai Edge DNS was down
#117https://downdetector.com/archive So many sites down... and unfortunately not one of them is Twitter
You got your wish, looks like Twitter's on the list now too.
Re: Akamai Edge DNS was down
#118People don't believe me when I say how much DNS matters. So I wrote a song about it.
https://soundcloud.com/ryan-flowers-916961339/dns-to-the-tun...
Re: Akamai Edge DNS was down
#119Earlier quoted context omitted.
What's frustrating is that DNS is returning an address, instead of just failing, and so macos is caching that value (though it might be cloudflare doing that).
Wildcard DNS should be a prosecutable crime, punishable by no less than 20 years of hard labor. (Edit: Probably should have made it clear that this was a joke)
Wildcard DNS helps me to handle multitenancy easily. What's wrong with it?
Re: Akamai Edge DNS was down
#120Earlier quoted context omitted.
I switched to BitWarden and haven't looked back. You can use it on the phone and pc (browser). As well as a desktop client.
Yeah, my path was LastPass -> Bitwarden -> 1Password. Both Bitwarden and 1Password are great.
Same path. It'll be very hard to move away from 1Password. App experience, sync, security features like key in addition to master password, family organizer-based recovery of an account, these are a few things that stand out.