NS1

NS1 was founded on the idea that DNS could be more than a simple name-to-address lookup — that the DNS layer could be an active component of traffic management, routing decisions, and application delivery. The platform's Filter Chain architecture allows operators to compose traffic management logic from modular filters: geolocation, latency measurement, load balancing, A/B testing, and health check data can all influence which DNS answer is returned to a given resolver. This data-driven DNS approach attracted enterprise and media customers who needed more sophisticated traffic steering than traditional round-robin or simple geographic routing could provide. IBM acquired NS1 in 2022, integrating it into IBM's networking and edge product portfolio.

The authoritative DNS infrastructure that NS1 operates handles query resolution for its customer base using a globally distributed anycast network. The data-driven routing decisions that differentiate NS1 from simpler DNS providers require the filter chain logic to execute at query time using real-time data — health check results, latency measurements, and traffic load signals must be available to the resolver at the moment each query is answered. This real-time data dependency means that health check infrastructure failures can cause routing decisions to be made with stale or absent signal data, potentially directing traffic to degraded endpoints.

DNS infrastructure degradation at NS1 produces the downstream failures characteristic of any authoritative DNS problem, amplified by the traffic management dependency. Domains hosted on NS1's name servers become unresolvable when the authoritative resolver network is degraded, making them unreachable regardless of origin health. Filter chain logic that depends on real-time health check data falls back to configured default behaviour when health check data is unavailable, which may direct traffic differently than intended. The NS1 management portal and API, used for zone and record management, can be unavailable independently of the resolver network during control plane incidents.

Outage.gg tracks NS1 service status through community reports from network engineers and platform operators. If DNS resolution is failing, traffic management routing is behaving unexpectedly, or the portal is inaccessible, the live status page shows current incident data.