I’m sharing this as both a warning and a public record of what happened with Sav.com’s V2 system.
What happened
EEA.net expired on December 24, 2025 at Sav. The name entered the standard 30-day registrar grace period.
On January 20, 2026, while the domain was still in grace, I attempted to renew it through Sav’s official V2 dashboard.
At the time:
Later, Sav said no backend order existed for EEA.net on January 20 and sent the name to auction, where it was awarded to another bidder.
Why I contacted Sav when I did
EEA.net has an unusual two-month gap between its creation and expiration dates. That mismatch made the timeline look longer than it actually was, which is why I reached out after noticing the problem. Importantly, my renewal attempt still occurred within the official grace period.
Why I had screenshots
Since Sav rolled out V2, I’ve experienced:
What Sav said
On February 2, before the auction ended, I contacted support and provided my screenshots. Sav acknowledged in writing that the V2 dashboard showing “Grace Renewal Period” may have been misleading. They still refused to intervene, saying only backend logs matter.
Their position: my “first recorded attempt” was February 2, after grace had ended.
Why this matters to other domainers
I manage over 2,000 domains and paid thousands for EEA.net. I’ve renewed thousands of names over the years at other registrars without issues.
The core problem here is not that I forgot to renew. The issue is that Sav’s own interface allowed a full renewal flow during grace, entered a processing state, continued to show “Grace Renewal Period,” and then later relied solely on backend logs to justify sending the name to auction.
Because of repeated V2 issues, I previously moved most of my highest-value domains out of Sav. I kept a smaller set and documented renewals precisely so I would have evidence if something went wrong. In this case, even that was not enough.
Over the past few days I’ve seen multiple similar reports on Trustpilot, Reddit, and NamePros involving stalled renewals, missing domains, confusing status labels, and post-hoc reliance on logs. This appears to be a pattern rather than a one-off. This makes me deeply concerned that many domains at Sav could be at risk whenever a V2 renewal glitches, because Sav ultimately defers only to its internal logs.
What I’ve done
I filed a formal ICANN Contractual Compliance Complaint regarding Sav’s handling of this renewal and auction.
Screenshots I’m sharing here
If anyone has had similar V2 renewal issues at Sav, especially stalled “processing” states, please share your experience.
I’ll update this thread as things progress.
What happened
EEA.net expired on December 24, 2025 at Sav. The name entered the standard 30-day registrar grace period.
On January 20, 2026, while the domain was still in grace, I attempted to renew it through Sav’s official V2 dashboard.
At the time:
- The cart showed EEA.net – Domain Renewal – $12.12
- I proceeded to payment
- The system moved to a “We’re processing your order(s)” screen
Later, Sav said no backend order existed for EEA.net on January 20 and sent the name to auction, where it was awarded to another bidder.
Why I contacted Sav when I did
EEA.net has an unusual two-month gap between its creation and expiration dates. That mismatch made the timeline look longer than it actually was, which is why I reached out after noticing the problem. Importantly, my renewal attempt still occurred within the official grace period.
Why I had screenshots
Since Sav rolled out V2, I’ve experienced:
- Domains disappearing from my dashboard
- Failed or inconsistent renewals
- Confusing status labels
What Sav said
On February 2, before the auction ended, I contacted support and provided my screenshots. Sav acknowledged in writing that the V2 dashboard showing “Grace Renewal Period” may have been misleading. They still refused to intervene, saying only backend logs matter.
Their position: my “first recorded attempt” was February 2, after grace had ended.
Why this matters to other domainers
I manage over 2,000 domains and paid thousands for EEA.net. I’ve renewed thousands of names over the years at other registrars without issues.
The core problem here is not that I forgot to renew. The issue is that Sav’s own interface allowed a full renewal flow during grace, entered a processing state, continued to show “Grace Renewal Period,” and then later relied solely on backend logs to justify sending the name to auction.
Because of repeated V2 issues, I previously moved most of my highest-value domains out of Sav. I kept a smaller set and documented renewals precisely so I would have evidence if something went wrong. In this case, even that was not enough.
Over the past few days I’ve seen multiple similar reports on Trustpilot, Reddit, and NamePros involving stalled renewals, missing domains, confusing status labels, and post-hoc reliance on logs. This appears to be a pattern rather than a one-off. This makes me deeply concerned that many domains at Sav could be at risk whenever a V2 renewal glitches, because Sav ultimately defers only to its internal logs.
What I’ve done
I filed a formal ICANN Contractual Compliance Complaint regarding Sav’s handling of this renewal and auction.
Screenshots I’m sharing here
- Jan 20 cart showing EEA.net – $12.12
- Jan 20 “Processing your order(s)” screen
- Dashboard showing Renewal Grace Period
- Feb 2 support chat where Sav admits the UI may have been misleading
If anyone has had similar V2 renewal issues at Sav, especially stalled “processing” states, please share your experience.
I’ll update this thread as things progress.
Last edited:















