On 17 March 2026, Radix transitioned to Tucows Registry Services. For many service providers, a change like this typically means technical work, coordination, and potential risk.
For Registry Gateway customers, it didn’t.
This transition is a clear example of what Registry Gateway is designed to do: absorb registry complexity in the background, so your operations stay stable and predictable.
When a registry changes its backend provider, integrations and operational processes are usually affected. Without an abstraction layer, this often leads to development work, workflow adjustments, and migration planning.
With Registry Gateway, this is handled as part of the platform.
We manage registry integrations, updates, and changes centrally, so you don’t have to. That means no need to rebuild integrations, no need to adapt your workflows, and no need to run a separate migration project.
The only visible impact was the downtime window defined by the registry.
For the affected Radix TLDs (.fun, .host, .in.net, .online, .press, .pw, .site, .space, .store, .tech, .uno and .website), the transition took place on 17 March 2026 from 00:00 UTC until approximately 10:00 UTC.
During this window:
Transformational commands (create, renew, transfer, update, delete) were temporarily unavailable
DNS and RDDS remained operational
Informational queries stayed available
Outside of this planned window, operations continued as usual.
The key takeaway is simple: you don’t need to manage registry backend migrations yourself.
Registry Gateway gives you one stable integration for all your registry connections. Whether a registry updates its systems, changes processes, or migrates to a new backend, your setup remains unchanged.
This is possible because Registry Gateway combines your own accreditations with Realtime Register’s integrations into one unified platform and API.
Registry changes are not one-off events. They happen regularly across the domain ecosystem.
With Registry Gateway, you are protected from that ongoing complexity:
One API connection for all registry integrations
No need to manage registry or ICANN requirements yourself
No development work when registries change systems
Reduced operational overhead and fewer migration risks
Platform-managed updates, maintenance, and compliance
In practice, this means your team can focus on customers and growth, instead of technical maintenance and registry-specific processes.
At Realtime Register, we believe domain operations should be efficient, predictable, and easy to manage.
Registry Gateway is built to give you exactly that: one platform, one API, and full control over your domain business, without the complexity behind the scenes.
Do you have questions about this migration, or want to learn more about how Registry Gateway supports your accreditations and registry connections?
Our team is ready to help.