We want to address the recent issues affecting .SI domains and provide some context on what happened, why Dynadot was impacted, and what we're doing to improve the experience.
Over the past week, we've seen an unusually high level of demand for .SI domains. This surge created significant challenges with registry connectivity, resulting in delays and errors across several services, including domain registrations, availability checks, nameserver updates, transfers, and other domain management functions.
We understand how frustrating this has been, particularly for customers who experienced failed registration attempts, delayed updates, or difficulty managing their domains. We sincerely apologize for the disruption.
Why was Dynadot impacted so heavily?
Dynadot manages the largest portfolio of .SI domains among registrars, which meant we were handling a particularly high volume of requests during this surge.
The .SI registry has limitations on the number of connections and requests it can process. With demand increasing dramatically, these limitations created bottlenecks that affected our ability to communicate with the registry and process customer requests in a timely manner.
We've seen some customers question why they were able to perform certain actions at other registrars while experiencing difficulties at Dynadot. While other registrars also experienced connectivity challenges, the impact was not necessarily the same across all providers. Our significantly larger .SI volume meant we were placing more requests through the available registry connections, resulting in greater disruption for our customers.
For perspective, Dynadot supports over 700 TLDs and routinely processes much higher registration volumes across our platform without these types of issues. This was an unusual combination of extraordinary demand, registry infrastructure limitations, and our existing .SI market share.
What have we done to improve the situation?
Our engineering team has been actively monitoring the issues and has implemented process improvements to better manage requests, reduce unnecessary connection attempts, and improve how our systems handle registry connectivity disruptions.
While some of the underlying limitations are outside our direct control, we recognize that it's our responsibility to provide the best possible experience for our customers. We're continuing to evaluate additional improvements to our order processing, retry mechanisms, and communication around pending requests.
Moving forward
We know that many customers rely on Dynadot for time-sensitive registrations and domain management, and we understand the importance of having reliable access to these services.
This situation has highlighted areas where we can improve, particularly in how we manage unusually high demand when registry connectivity is constrained. We'll continue working to strengthen these processes and minimize the impact of similar situations in the future.
We appreciate your patience and understanding throughout this unusual period, and we apologize again for the inconvenience it has caused.