GitHub pretty slow in Brazil
Massive Dyn DNS outage
71–80 of 302 posts
Re: Massive Dyn DNS outage
#72GitHub pretty slow in Brazil
Re: Massive Dyn DNS outage
#73GitHub employee here. We're monitoring an incident with our upstream DNS provider: https://twitter.com/githubstatus/status/789433336083001344
> our upstream DNS provider
Maybe you should have more than one. Then I could actually carry out my work...
Re: Massive Dyn DNS outage
#74GitHub pretty slow in Brazil
A lot of the bigger sites are very slow from Brazil today :(
And SP is also suffering from a lack of power in some areas. Happy Friday!
Re: Massive Dyn DNS outage
#75GitHub pretty slow in Brazil
same here. getting the "page taking way too long to load" page every time.
Re: Massive Dyn DNS outage
#76Earlier quoted context omitted.
The TTL for the glue records of a .com domain is 48 hours, so even if you have Route53 set up and ready to go, it takes a long time to switch the zone away from Dyn. We switched from Dyn to Rout53 a few weeks ago. It took about 12 hours before half of the traffic had shifted over.
That's the reason to have your DNS at at least two different companies, working in tandem. In a case where one is down, your Unicorn Corp doesn't go down with it.
How does that work in practice? Even if I set NS records pointing to two different DNS providers, I don't think a DNS client would automatically switch and retry if one is too slow to respond/times out.
Re: Massive Dyn DNS outage
#77Earlier quoted context omitted.
The TTL for the glue records of a .com domain is 48 hours, so even if you have Route53 set up and ready to go, it takes a long time to switch the zone away from Dyn. We switched from Dyn to Rout53 a few weeks ago. It took about 12 hours before half of the traffic had shifted over.
That's the reason to have your DNS at at least two different companies, working in tandem. In a case where one is down, your Unicorn Corp doesn't go down with it.
Exactly: there's nothing wrong with only using one provider if you're not willing to pay for two services but if you can't afford downtime you really need active diversity all the way down.
Route53 uses a bunch of different top-level domains for the same reason – if someone does manage to take the .com servers offline you'll be glad .co.uk is run by a separate organization.
Re: Massive Dyn DNS outage
#78DYN is experiencing a DDoS https://www.dynstatus.com/incidents/nlr4yrr162t8
Yep. Seems to be the root of the problem.
Re: Massive Dyn DNS outage
#79All this talk about redundancy, real-time apps, scalable architecture and and a "simple" DDOS against DNS architecture brings half of the internet down. Honestly did nobody think about having a spare dns at some other company? or even backup dns server exactly for a situation like that?
From where I'm looking at the internet (central Europe), I don't notice anything. Maybe your internet on the other side of the Atlantic is broken, ours seems to be working fine. ;-) Edit: Looks like the eastern part of the USA is affected: https://cloudharmony.com/status-for-dyn
Not really, I can't access our production servers which are in US east. Can't access Intercom with which we provide customer support. Our clients are mailing us that payment provider doesn't work either. So we're losing money while being in central EU.
Re: Massive Dyn DNS outage
#80Earlier quoted context omitted.
That's the reason to have your DNS at at least two different companies, working in tandem. In a case where one is down, your Unicorn Corp doesn't go down with it.
How does that work in practice? Even if I set NS records pointing to two different DNS providers, I don't think a DNS client would automatically switch and retry if one is too slow to respond/times out.
Why not? That's the whole idea behind having more than one NS server isn't it?