What Service Changes and Outages Has UncensoredDNS Experienced?

UncensoredDNS has documented several service changes and outages on its blog, most notably the shutdown of two anycast nodes (Kracon and Solido), a unicast server relocation, an IPv6 outage affecting the unicast server via Telia, a period of blog downtime, and the permanent disabling of cleartext DNS on port 53. These events are recorded in the project's blog posts and reflect the operational history of the service run by Thomas Steen Rasmussen.

Anycast node shutdowns

Two anycast nodes were permanently retired:

• Kracon anycast node — shut down permanently on October 24, 2024. The blog post notes that the company sponsoring the node was involved in the decision (the excerpt is truncated, but the shutdown is confirmed as permanent).
• Solido anycast node — also shut down, according to a blog post titled "Solido Anycast Node Shut Down."

What this means for users: The anycast service (anycast.uncensoreddns.org) continues to operate from multiple locations, but the removal of individual nodes can change which physical location answers your queries. If you relied on a specific node for latency or routing reasons, your traffic may now be served from a different location.

Unicast server relocation

A blog post from January 23, 2022 ("Moving Day Coming Up") announced that the unicast server was moving to a new hosting location within one to two weeks, with expected downtime during the transition.

What this means for users: If you use unicast.uncensoreddns.org (89.233.43.71 / 2a01:3a0:53:53::), the move may have caused temporary resolution failures. The unicast node is hosted at AS9167 in Copenhagen, Denmark, so a hosting change could also affect latency for users far from the new location.

IPv6 outage on the unicast server (Telia)

On February 15, 2021, a blog post reported that IPv6 had not been working for the unicast server since 01:57 CET that day, specifically via Telia. The post notes this affected DNS resolution over IPv6.

What this means for users: If your network reaches UncensoredDNS over IPv6 through Telia, queries to the unicast server would have failed or fallen back to IPv4 during that window. This is a useful reminder to check whether your resolver supports both address families if you depend on the unicast node.

Blog downtime

A post from February 10, 2022 ("Blog is Operational Again") states the blog had been offline for longer than the author would have liked before being restored.

What this means for users: The blog is the primary channel for service announcements. During blog outages, status updates may not have been available, so users should also check the project's Twitter account (@censurfridns) for updates.

Cleartext DNS turned off

Although not an outage, this is a major service change: cleartext DNS lookups on port 53 (both TCP and UDP) were permanently turned off on September 1, 2022, following an earlier announcement in February 2022. The blog cites the "unfriendly internet" as the reason.

What this means for users: If your device or router still points to UncensoredDNS over plain port 53, those lookups will no longer work. You must switch to an encrypted protocol:

How to check current status

Because these events span 2021–2025, the most reliable way to confirm what is currently running is to consult the project's own channels:

1. Blog (blog.uncensoreddns.org) — latest posts list service changes and outages.
2. Twitter/X (@censurfridns) — the project directs users here for updates and information.
3. Server info on the homepage — current anycast and unicast addresses and supported protocols are listed there.

If you are troubleshooting a resolution failure, first confirm which endpoint and protocol you are configured for, then check whether that endpoint has been affected by a node shutdown, relocation, or protocol change listed above.