Service update · 15 October 2026
We are completing our move away from Closte. A renewed domain hold, a substantial billing dispute and administrative tasks left pending have reinforced our decision to move every remaining customer service. We valued the platform for years. Our priority now is to complete the migrations, recover any remaining data and close the accounts carefully.
Need help completing a hosting migration? Contact our team · bali@birudaun.net · +62 361 4748157
The domain is on hold again
The current registry record for closte.com shows clientHold. Under ICANN’s explanation of domain status codes, this is a registrar-set hold that prevents a domain from being activated in DNS. Our public DNS checks on 15 October returned no such domain for both closte.com and app.closte.com.
The hold affects more than the homepage: it removes the normal public-DNS route to services addressed under closte.com. That includes the control panel and any backend, CDN or staging endpoint using a closte.com address. Without access to those interfaces, customers lose the normal means of managing their hosted services, retrieving backups or completing account changes. A website using its own domain may continue to run while its owner is unable to reach the hosting controls.
Our check on 24 September found the domain reachable and no clientHold in the registry record. The hold recorded on 15 October therefore marks a change since that check, following the earlier access interruptions described in our previous article.
The domain remains registered until January 2029. The registry record does not state why the hold was applied.
We reached the control panel using a local hosts-file workaround that mapped Closte’s domain names directly to their IP addresses, bypassing public DNS. Customers relying on normal DNS resolution could not reach closte.com or app.closte.com at the time of our checks.
A billing discrepancy that needs an explanation
We are also reviewing a customer’s report of a substantial apparent overcharge. Charges rose sharply above the account’s usual pattern during a period when we were moving workloads away and reducing traffic, with no corresponding expansion of the services we used.
The disputed charges need to be reconciled with the underlying usage and the services that were still active. The final amount due, and any correction, remain unresolved in the material reviewed for this article.
For the business receiving the bill, the immediate need is straightforward: a clear account of what was charged, why it was charged and how any error will be corrected. Access to someone who can resolve that question matters just as much as access to the billing screen.
The administration system is also reporting problems
During our 15 October check, Closte’s dashboard carried a notice acknowledging technical problems and warning that some features may not work as expected.
Administrative tasks remained pending during our review, with no completed result shown. That left the related cleanup steps unfinished.
This creates a practical complication for customers trying to leave. The account-termination screen requires websites, DNS zones, email domains, CloudSnaps and SSL certificates to be removed before an account can be closed. When a removal request remains pending, the customer cannot treat that part of the exit as complete.
Moving a website to another host and closing the old hosting account are separate jobs. Both need to be completed.
Every remaining customer is moving
Our previous assessment of Closte’s business risks allowed a small number of very low-traffic websites to remain at Closte while their owners used prepaid balances. We are now ending that exception and moving all remaining customer services away.
Closte suited our technical way of working for a long time. We were comfortable with self-service and did not expect routine assistance with every configuration change. We appreciated the platform and the work behind it.
Our responsibility to customers, however, includes dependable access, understandable billing and the ability to complete routine administration. We want customers to run their businesses without discovering unexpectedly that a website or an essential control panel is unavailable.
That responsibility determines the next step. Any remaining prepaid balance will be considered as part of closing an account; it is no longer a reason for us to leave customer workloads there.
Complete the move, then close the account
For anyone who still has data or services at Closte, our recommendation is to complete the departure in a deliberate order:
- Recover what you need. Export website files, databases and any remaining backups or configuration records. Keep copies outside Closte and confirm that they are usable.
- Verify the replacement service. Check the migrated website, forms, transactions and any connected services. Move any DNS or email dependencies before removing them from the old account.
- Keep the billing record. Save invoices, payment receipts, usage reports and correspondence. Ask for an explanation of disputed amounts and retain the records needed to resolve them.
- Remove the remaining resources. Once the migration is verified, remove the services and stored copies that are no longer required. Check that deletion tasks have actually finished and that the account’s closure requirements have been met.
- Remove saved payment methods and close the account. Use the controls available, retain confirmation and check subsequent statements. If the platform prevents payment-method removal or closure, record the problem and contact the provider and the payment issuer about the available next steps.
Removing a payment method does not itself close an account or settle an outstanding billing question. Treat the data migration, service cancellation, payment arrangements and final account closure as parts of the same handover.
Closing the chapter with appreciation
For our managed hosting work, the Closte case is closed as a provider decision. The remaining work is to finish the customer migrations and account administration carefully.
We are sorry to reach this point. We liked Closte and value the years in which it served us well.
We thank the Closte team and developers for that work. We wish them a good future and hope they can resolve the current difficulties successfully. Our own next chapter is to complete the move for every remaining customer and leave their websites, data and payment arrangements in a clear, settled position.
Earlier third-party reports
Earlier reports show that access and billing concerns have also been raised outside our own experience:
- 21 April 2025 — Reddit, r/webhosting: a customer discussion about Closte’s unavailable domain and related services, including reports that some websites on their own domains continued working.
- 18 July 2026, updated 19 August — Best Website: the web agency’s technical account of the Closte domain outage describes its DNS checks, a period of partial recovery and a renewed domain hold.
- 26 August 2026 update — LYVTech: another web agency’s report on Closte access problems records DNS failures and a domain hold, alongside guidance for affected site owners.
- 17 September 2026 — Trustpilot: a customer review on Closte’s profile reports a substantial increase over previous monthly charges.
These are dated technical accounts and customer reports, rather than official findings about Closte. They provide context for earlier concerns; they do not establish a common cause or resolve the billing question described here.
Make sure nothing important is left behind. We can help review your remaining hosting dependencies and plan the next steps. Contact our team · bali@birudaun.net · +62 361 4748157
