Oracle Dyn

Dyn started in 2001 as a dynamic DNS service — a clever solution for home users and small businesses that wanted to host services behind residential internet connections with constantly changing IP addresses. Over the following decade Dyn evolved into a serious enterprise DNS provider, offering managed DNS, email delivery, and internet performance monitoring to large organisations worldwide. Oracle acquired Dyn in 2016 for a reported $600 million, folding it into the Oracle Cloud Infrastructure portfolio. The Dyn brand has since been largely retired in favour of the Oracle DNS and Oracle Cloud infrastructure branding.

Dyn entered public consciousness in October 2016 when it was struck by one of the largest distributed denial-of-service attacks in recorded history. The Mirai botnet — composed of hundreds of thousands of compromised IoT devices — flooded Dyn's infrastructure with DNS query traffic at a scale that overwhelmed its mitigation systems. The result was that major websites and services including Twitter, Reddit, Netflix, Spotify, and Amazon were unreachable for hours across large parts of North America and Europe. The incident demonstrated how much of the internet's visible diversity actually depends on a small number of DNS infrastructure providers operating underneath.

Managed DNS providers like Oracle Dyn serve as authoritative nameservers for their customers' domains, meaning that when the DNS provider has problems, every domain hosted on that infrastructure becomes unresolvable. Enterprise customers depend on Dyn for latency-based routing, geographic load balancing, and failover automation — services that actively shape where traffic lands across distributed infrastructure. A provider-level outage breaks all of those mechanisms simultaneously, sending traffic to wrong endpoints or returning SERVFAIL responses to every query.

Outage.gg tracks Oracle Dyn DNS infrastructure status through reports from network engineers, DevOps teams, and infrastructure managers. If DNS resolution for Dyn-hosted domains is failing, the management console is unreachable, or anycast routing is behaving abnormally, the live status page reflects current community reports.