At Levamo, we build managed WordPress hosting for businesses that depend on their websites. Our infrastructure is designed to keep your site fast, stable, and ready to grow, from everyday browsing to busy checkouts and logged-in experiences.

Behind the scenes, our team is constantly working to improve that platform. Infrastructure upgrades allow us to adopt better technology, improve performance, and provide a dependable foundation for your business.

Our next major upgrade introduces a new generation of hardware, including AMD Zen 5 processors, alongside improvements to memory and storage performance. In our testing, these changes have delivered significant improvements in WordPress processing performance.

To make this possible, we're moving our underlying hosting infrastructure from Amazon Web Services (AWS) to Oracle Cloud Infrastructure (OCI).

Every customer will receive this upgrade at no additional cost. Your existing plan, features, and pricing will remain unchanged.

We're planning to begin migrating customer hosting environments in November 2026. Each migration will involve a scheduled maintenance window and some downtime.

This guide explains what's changing, what to expect, and how to prepare.

We're upgrading from AMD Zen 4 to Zen 5 processors, alongside improvements to the memory and storage supporting your website.

Together, these changes should help database queries run faster and reduce the time WordPress spends processing requests. This can improve time to first byte (TTFB), meaning your website starts responding sooner.

You may notice the biggest benefits on dynamic pages that aren't served from cache, such as checkouts, account areas, and your WordPress dashboard.

In our testing with WPPerformanceTester, the new infrastructure processed close to twice as many WordPress queries per second, increasing from approximately 2,400–2,500 to nearly 5,000.

This synthetic WordPress benchmark measures the combined processing performance of the upgraded infrastructure. The improvements you experience on your own website will depend on how it's built, configured, and used.

No. Your existing plan and pricing will remain exactly the same. This infrastructure upgrade comes at no additional cost.

Your existing plan features, PHP workers, storage allowance, and add-ons will remain unchanged. You'll continue using the same Levamo dashboard and managing your websites as you do today.

We're transferring your entire hosting environment, including website files, databases, configurations, and staging sites, to the new infrastructure.

Your custom domain names will remain the same. However, your hosting environment's IP address and the region code in certain Levamo temporary URLs will change.

We've chosen Oracle Cloud as a partner that can support where we want to take Levamo.

Its flexibility gives us greater control over how we configure processing power, memory, and storage for WordPress hosting.

This allows us to introduce newer infrastructure across our platform while maintaining our customers' existing plans and pricing, and continue improving the service as their needs grow.

Over the past six months, we've worked closely with Oracle and our infrastructure partners to test and fine-tune the new platform.

Our testing has focused on processor performance, memory, storage, and how these components work together to deliver better WordPress performance. We've also been developing and testing the process used to transfer hosting environments between infrastructure providers.

Our objective is to complete each migration reliably, preserve customer data, and minimize disruption.

Yes. As part of the infrastructure upgrade, we're consolidating our hosting locations.

Your backups will remain in their existing locations, on separate infrastructure outside AWS.

After the transition, Chicago and Frankfurt will also be the available hosting locations for new websites.

We're investigating additional locations, but none have been confirmed at this stage.

Hosting location can affect network latency, particularly when visitors are geographically distant from the server. For example, a website currently hosted in US West will move to US Central, which changes the distance between the hosting environment and some visitors.

At the same time, the new infrastructure offers improved processing capabilities that can help websites respond more quickly.

The overall effect will depend on your website's workload, visitor locations, caching, and other factors. We can't guarantee that every website or visitor will experience the exact same performance improvement.

No. The upgrade will include all customers.

Once the migration to Oracle Cloud is complete, we'll retire our AWS hosting infrastructure, so remaining on the current platform won't be an option.

We're planning to begin migrating customer hosting environments in November 2026.

We'll schedule migrations by hosting environment, which includes all websites and staging sites associated with an individual plan. We'll analyze recent traffic patterns across those websites to help identify a quieter period for the migration.

Before your scheduled migration, you'll receive an email with your maintenance date and time. You'll also be able to view the schedule in your Levamo dashboard, with the time zone clearly identified.

We'll send a reminder before maintenance begins and confirm completion once the migration and our checks are finished.

Yes. Your websites will experience planned downtime while we move your hosting environment to the new infrastructure.

During this time, visitors will see a Levamo maintenance message, and your websites won't be accessible normally.

We're allowing approximately two hours for each maintenance window, although your websites may return online sooner.

The time required depends primarily on the size of your hosting environment's disk. Larger environments may require additional time. The maintenance window includes both the transfer and our verification checks. It is an estimate, not a guaranteed maximum downtime.

We'll include your expected maintenance window in your migration notification and keep you informed if the work takes longer than planned.

Yes. We'll initially select a maintenance window based on recent traffic patterns and our available migration capacity.

If the selected time doesn't work for you, you'll be able to choose an alternative from the available dates and times in your Levamo dashboard.

You can make this change once, at least 48 hours before your scheduled migration.

If none of the available options work for you, please contact our support team so we can review your circumstances.

If you have an important business event, promotion, launch, or other time-sensitive activity planned, please contact us as early as possible.

Before migration begins, we'll stop your hosting environment from accepting new requests and allow requests already being processed to finish. We'll then pause the database and take your hosting environment offline while we transfer it to the new infrastructure.

During this period, your websites won't accept new orders, form submissions, registrations, or other changes.

This protects the consistency of your existing data during the transfer.

For ecommerce websites: Payment notifications delivered through webhooks may be delayed while your website is offline. Most payment providers automatically retry failed webhook deliveries, although retry behavior, including timing and maximum attempts, depends on the provider.

If your business relies on external systems that communicate with your website, we recommend reviewing those integrations before your scheduled migration.

Scheduled tasks and background processes won't run while your hosting environment is offline for maintenance.

Your existing scheduled tasks and queued actions will be preserved as part of the migration. Once your environment is back online, background processing can resume, including pending tasks that are eligible to run.

Some time-sensitive tasks may execute later than originally scheduled, depending on how they're configured.

Your Levamo dashboard will remain accessible during the migration, allowing you to view your maintenance schedule and migration status.

However, your websites and hosting environment will be temporarily unavailable. This includes access to WordPress administration, SFTP, SSH, and other tools that require a running hosting environment.

Our team will verify that your hosting environment has been successfully transferred before confirming the migration is complete.

If we encounter an issue, we'll investigate and work to resolve it. We'll keep you informed of significant delays or changes to your maintenance schedule.

If the migration cannot be completed as planned, our team will determine the appropriate next steps and notify you of any additional maintenance required.

We're cloning your hosting environment onto the new infrastructure, including your website files, databases, and configurations.

Before the transfer, we'll prevent new changes to the environment and allow requests already in progress to finish.

Our migration automation verifies that the copied files and data match your original hosting environment. Our team will then carry out additional checks to confirm that the migration has been completed successfully.

If our checks identify any problems, we'll investigate and resolve them before confirming completion.

Yes. Your backups are already stored in a separate data center outside AWS.

We'll retain your existing backup data, and you'll continue to have access to your backups after the move.

Your staging sites will move to the new infrastructure alongside your production websites.

Any staging sites using Levamo temporary URLs will receive updated hostnames reflecting the new hosting region.

If your deployment tools connect using temporary URLs or IP addresses, you'll need to update their connection settings after migration. The required hostname changes are explained in the SFTP and SSH section below.

All websites within the same hosting plan, or hosting environment, will be migrated together. This includes any staging sites associated with those websites.

If you have multiple hosting plans, each environment will have its own scheduled maintenance window.

Our migration automation will verify the transferred files and data, and our team will carry out additional checks before confirming completion.

Once verification is complete, we'll notify you by email and update the migration status in your Levamo dashboard.

We recommend checking your websites after migration, particularly any business-critical functionality such as checkout, registrations, forms, and external integrations.

Yes. Each hosting environment has one static public IP address, and that address will change during migration.

To give customers time to update their DNS records, we'll temporarily forward incoming website traffic sent to the old IP to the new hosting environment through a fallback reverse proxy for 60 days after migration.

After that period, traffic sent to the old IP address will no longer be forwarded.

This temporary forwarding only covers incoming website traffic. Other connections, including SFTP and SSH connections that use the old IP address, will need to be updated when your environment moves.

External services that allowlist your hosting environment's IP address will also need to be updated. The temporary forwarding system doesn't cover outgoing connections.

Your new IP address will be available in your Levamo dashboard once migration is complete.

This depends on how your domains are connected to Levamo.

We'll automatically update the necessary DNS records as part of the migration. You won't need to make these changes yourself.

You'll need to update the relevant DNS records manually after migration, unless you first update your domain connections to use our newer system.

We recommend making this change before your scheduled migration so we can manage the DNS updates automatically.

You can find instructions in our domain management how-to guides.

You'll need to update the relevant DNS records to point to your new hosting environment's IP address.

Your new IP address will be available in your Levamo dashboard after migration.

Our temporary IP forwarding system provides additional time to make these changes, but all DNS updates should be completed as soon as possible after the migration.

If your domains are connected through Levamo's Cloudflare domain management system, you won't need to make changes to your CDN or SSL setup.

We'll continue managing your CDN and automatically issuing and managing SSL certificates as we do today.

If you manage your CDN or SSL configuration elsewhere, we don't expect changes beyond updating the necessary IP addresses.

However, some setups may require additional attention. If you're using an external CDN, custom reverse proxy, or specialized SSL configuration, please contact our support team before your migration.

This depends on how you connect.

If you connect using a custom domain name:

Your hostname can remain the same, provided the domain's DNS records are updated correctly.

If you connect using a Levamo temporary hostname:

You'll need to update the hostname in your SFTP or SSH client after migration.

The region code changes as follows:

Only the region code changes. The rest of the temporary hostname stays the same.

If you connect directly to an IP address:

You'll need to replace the old IP address with your environment's new IP address after migration.

You'll find your exact SFTP and SSH connection details in your Levamo dashboard.

Some integrations may require changes, depending on how they connect to your hosting environment.

Tools and integrations using your custom domain can continue using the same address, provided its DNS records are updated correctly.

If an integration connects using a Levamo temporary URL or directly to your hosting environment's IP address, you'll need to update its connection settings after migration.

If an external service only accepts connections from approved IP addresses, you'll need to update its allowlist with your hosting environment's new static IP address.

This is necessary even if Levamo automatically manages your DNS records.

Connections from your website may fail if the external service continues to allow only the old IP address.

Incoming webhooks may be interrupted while your environment is offline. Whether failed requests are retried depends on the sending service.

Scheduled tasks running within your environment won't execute during maintenance.

If you use a custom reverse proxy, IP-based integrations, or specialized connection settings, please contact our team before your scheduled upgrade.

Once you've received confirmation that your migration is complete, we recommend checking your websites and any important external connections.

Depending on your setup, this may include:

If your domains are connected through Levamo's Cloudflare domain management system and you don't use any external connections that require updating, you may not need to make any changes.

If you have questions about the infrastructure upgrade, need assistance preparing for your migration, or notice anything that isn't working as expected afterward, please contact the Levamo support team through live chat in your dashboard.

Our team can help you review your domain connections, migration schedule, and any issues affecting your hosting environment.