KubeServers is Closing — What UK Magento Store Owners Must Do Next

KubeServers has confirmed it is closing down. The company has served a number of UK Magento merchants over the years, and its closure leaves those customers in a difficult position: find a new host that understands Magento, or risk losing their store entirely when the servers go dark.

This is not the first time a Magento-adjacent hosting company has closed. What makes KubeServers different is the specific customer base — merchants who chose them precisely because they claimed Magento expertise. Finding a direct replacement means finding a host that actually delivers what KubeServers promised.

When a hosting company shuts down, the timeline typically goes like this:

1. Support degrades first. Tickets go unanswered. Response times stretch from hours to days.
2. Control panel access ends. You can no longer create backups, change settings, or access logs.
3. Servers are shut down. Your Magento store goes offline. Visitors see an error or blank page.
4. Data becomes inaccessible. Without an advance backup, your database, media files, and code may be unrecoverable.
5. DNS expires. Your domain may begin resolving to nothing, further damaging search rankings.

For a Magento store, even 24 hours of downtime has measurable consequences: lost orders, lost organic ranking signals, and lost customer trust. Extended downtime during a shutdown scenario can take months to recover from in Google Search.

Not every host that claims to support Magento actually does. Here is what separates a real Magento host from a generic host with a Magento landing page:

• UK data centres. Latency matters for Magento stores selling to UK customers. A server in Frankfurt or Virginia adds measurable milliseconds to every page load.
• Full Magento stack included. Varnish for full-page caching, Redis for sessions and object cache, OpenSearch for catalogue search, NVMe storage for fast database reads. These should be included, not sold as extras.
• Magento-specific support. When your checkout breaks at 11pm, you need someone who understands Magento — not a generic helpdesk that will log a ticket and escalate in the morning.
• Free migration included. Any reputable Magento host targeting KubeServers customers should include migration at no extra cost. If they charge for it, keep looking.
• A real SLA. What is the uptime guarantee? What is the compensation policy if they miss it? Generic "99.9% uptime" claims are not enough — you need clarity on what happens when they fail.

EveryHost has been hosting Magento stores exclusively for over 14 years. We do not host WordPress, WooCommerce, or generic PHP applications. Every server we build, every configuration we apply, and every support engineer we employ is focused on one thing: Magento.

For KubeServers customers specifically, here is what you get when you move to EveryHost:

• Full migration included at no extra cost. We handle the database transfer, media files, code, DNS cutover, and post-migration testing.
• UK data centres. Your store stays in the UK, serving UK customers with low latency.
• The complete Magento performance stack. Varnish full-page cache, Redis, OpenSearch, and NVMe SSD storage — all configured correctly from day one.
• Sentinel WAF. Our in-house Magento-aware security layer blocks attack patterns specific to Magento: admin probing, search abuse, cron-driven spikes, and session attacks.
• 24/7 UK-based support. Engineers who know Magento, available around the clock.

We have done this many times. Here is the process from start to go-live:

Zero-downtime migration: your store moves off KubeServers before shutdown, live throughout.

1. We provision your new server. Based on your store size — product count, order volume, expected traffic — we configure the right dedicated or managed plan. This takes a few hours.
2. We migrate your files and database. Our engineers pull everything from your KubeServers environment: codebase, media library, database, and configuration. Your live store stays untouched throughout.
3. We test everything on the new server. We run the store on the new environment under a temporary domain. We check checkout, catalogue, search, admin, and cron — before we touch your live DNS.
4. DNS cutover — your store goes live on EveryHost. When you are satisfied with testing, we update DNS. Propagation typically takes 15–60 minutes. Your store is live on EveryHost with zero downtime.
5. Post-migration monitoring for 48 hours. We watch performance, error logs, and cache behaviour for 48 hours after go-live. If anything needs tuning, we fix it as part of the migration.