If your BandwagonHost instance is hosted in a facility that has introduced hardware updates, there is no need to immediately purchase a new virtual server. The provider offers a free upgrade option via KiwiVM for eligible existing instances, while newly created instances are automatically provisioned on the upgraded nodes. This guide is compiled and verified as of 2026-10-28 based on historical official announcements. You can log into KiwiVM to check for an upgrade prompt; if none appears or your workload has high requirements for service continuity, follow the structured guidance below.
Eligible Datacenters and Official Hardware Announcement Scope#
BandwagonHost has announced hardware node updates for specific datacenters at different times. Note that the confirmed hardware scope varies across facilities, and upgrade availability should not be assumed for facilities not covered by announcements.
| Announcement Date | Official Announcement Link | Datacenter Code | Verified Hardware Scope | Upgrade Access Details |
|---|---|---|---|---|
| 2026-05-12 | News #244 | New York USNY_6 / USNY_8 | AMD EPYC and NVMe RAID-10 | Existing VMs can log in to KiwiVM to see a free upgrade option; new VMs are automatically deployed on new nodes |
| 2025-09-20 | News #242 | Hong Kong HK3 / HK8 | AMD EPYC and NVMe RAID-10 | Free upgrade option provided via KiwiVM for existing VMs; new VMs are automatically deployed on new nodes |
| 2025-07-11 | News #240 | Los Angeles DC9 / USCA_9 | AMD EPYC and NVMe RAID-10 | Existing VMs can log in to KiwiVM to check for a free upgrade option; new VMs are automatically deployed on new nodes |
| 2025-06-23 | News #239 | Vancouver CABC_1 / CABC_6 | AMD high-frequency CPU and NVMe | Existing VMs can check KiwiVM for a free upgrade option; new VMs are automatically deployed on new nodes |
It is essential to note that the Vancouver announcement specifies only "AMD high-frequency CPU and NVMe" without stating EPYC or RAID-10. This entry should not be documented as verified EPYC or RAID-10.
Distinguishing Hardware Upgrades, Plan Adjustments, and Datacenter Migrations#
Users often confuse host hardware upgrades, plan upgrades, and cross-datacenter migrations. These three operations serve different purposes and require distinct checks:
| Action | Problem You Want to Solve | What to Verify First |
|---|---|---|
| Hardware Node Upgrade | Use newer hardware nodes mentioned in announcements | Check whether your instance displays a free upgrade option in KiwiVM and read current panel notices |
| Plan Adjustment | Need more CPU, RAM, or disk resources | Check whether plan resizing is supported in the client area, along with exact resource quotas and billing adjustments |
| Datacenter Migration | Change geographic location or network routing | Check available destination datacenters, migration rules, and notices within the migration interface |
Keep the following operational boundaries in mind:
- The official "free" upgrade description refers specifically to providing a hardware node upgrade option for eligible existing instances. For questions about specific impacts on your IP address, routing, monthly bandwidth tally, or billing, review the actual prompt displayed in KiwiVM before proceeding or confirm directly with official support.
- Cross-datacenter migration is an entirely separate operation. According to the official announcement on 2024-05-15 (News #231), KiwiVM migration transfers only occupied disk sectors, and all transfers are counted. This describes the mechanism of datacenter transfers and cannot be used to infer bandwidth usage, IP behavior, or duration for hardware node upgrades.
Pre-Upgrade Backup and General Maintenance Preparation#
Before initiating any system upgrade or administrative change within KiwiVM, complete standard maintenance safeguards to ensure reliable rollback options:
- Perform independent backups: Store critical databases, files, and configurations on an offsite server or local machine, and verify that backups can be restored. Review our Backup and Restore Guide for general backup workflows.
- Record existing network configurations: Keep a written record of your current public IP address, SSH port, service statuses, and firewall rules to simplify post-upgrade verification.
- Select a business-acceptable maintenance window: If your workload cannot tolerate potential service interruptions, perform the operation during low-traffic hours and notify relevant stakeholders in advance.
- Review current KiwiVM interface notices thoroughly: Operational details and notices can vary by batch and facility. Always rely on the text currently displayed in your control panel; if any stated impact is unacceptable for your setup, pause and consult support first.
What to Do If No Option Appears or Your Service Is Interruption-Sensitive#
If you log into KiwiVM and find no upgrade option, or if your service cannot accommodate potential interruptions, apply the following measures:
- Do not guess or tamper: Avoid modifying dashboard URLs or calling unlisted API endpoints. Do not attempt to apply procedures from one datacenter to another.
- Check the official system status page: Visit the Official Status Page before executing any maintenance. The status page displays timestamps in Vancouver time; use it to verify whether nodes are under active maintenance in real time, rather than treating it as a permanent uptime guarantee.
- Submit an inquiry via official support: If your instance is in an announced location but lacks an upgrade option in KiwiVM, contact support through the Official Ticket Portal to verify eligibility. Include the following details in your ticket:
- VPS identifier (VEID)
- Current datacenter code (e.g., USCA_9, HK3, USNY_6)
- The exact text currently displayed in KiwiVM or an explanation of the missing upgrade option
- Specific questions to confirm (such as whether the node batch qualifies for upgrade, or expected impact on the existing IP or connectivity)
Post-Upgrade Service Verification and Related Guides#
After the upgrade process finishes, verify your deployment against actual application workflows rather than relying solely on the control panel indicator:
- Network connectivity verification: Test SSH remote access, verify that public IP routing responds correctly, and check gateway and DNS resolution.
- Application and daemon checks: Confirm that web servers, database services, and containerized workloads restart normally and listen on expected ports.
- Data integrity and cron validation: Spot-check application data and files, and verify that scheduled cron tasks resume without issues.
- Baseline performance testing: If desired, evaluate system performance under identical network conditions and real workload profiles. There is no need to rely on external benchmark figures; practical stability for your application should remain the primary metric.
If you find that hardware improvements alone do not resolve latency or routing constraints, consult our BandwagonHost Datacenter Migration Guide or review our BandwagonHost Comprehensive Overview for broader datacenter comparisons.
If you determine that your current plan's resource limits can no longer accommodate growth and genuinely need to evaluate higher-tier plans, you can review current offerings through the Official BandwagonHost Purchase Portal (orders completed through referral links may generate a small commission for us, supporting our ongoing editorial work).
Information verified on 2026-10-28 based on official announcements.