The Radix migration to Tucows is now underway.
Affected TLDs:
.fun / .host / .in.net / .online / .press / .pw / .site / .space / .store / .tech / .uno / .website
ETA from registry side: March 17, 10:00 UTC
During the window, we're seeing the usual pattern:
create / renew / transfer / update / delete not going through
check / info still responding
DNS resolving normally
So domains are fine, just no lifecycle ops for now.
From our side, main impact so far:
renewals and transfers stacking
some API flows returning errors without much context
a few edge cases around domains close to expiry
Nothing unexpected, but still a bit messy operationally.
Curious how others are handling it:
retry later vs queue internally?
doing anything special for expiry edge cases?
or just letting support deal with it?
These backend switches (Team Internet to Tucows in this case) are getting more common lately, interested to hear if others are seeing similar patterns.
Affected TLDs:
.fun / .host / .in.net / .online / .press / .pw / .site / .space / .store / .tech / .uno / .website
ETA from registry side: March 17, 10:00 UTC
During the window, we're seeing the usual pattern:
create / renew / transfer / update / delete not going through
check / info still responding
DNS resolving normally
So domains are fine, just no lifecycle ops for now.
From our side, main impact so far:
renewals and transfers stacking
some API flows returning errors without much context
a few edge cases around domains close to expiry
Nothing unexpected, but still a bit messy operationally.
Curious how others are handling it:
retry later vs queue internally?
doing anything special for expiry edge cases?
or just letting support deal with it?
These backend switches (Team Internet to Tucows in this case) are getting more common lately, interested to hear if others are seeing similar patterns.
