Your business changes, and your server should follow. When traffic grows you upgrade; when a project winds down you can downgrade to save money. Here's how upgrades/downgrades typically work and what to watch for.
1. When to upgrade
- CPU or RAM is consistently near capacity and the app slows down.
- Disk space keeps running low.
- Traffic grows and you need more bandwidth or a more stable route.
2. When to downgrade
After a promo/campaign ends, when a project enters a quiet phase, or if you over-provisioned at the start — consider downgrading to cut costs.
3. The upgrade process
At 00Shark, upgrading is usually contact support to confirm the target spec → schedule the upgrade → verify your app. CPU/RAM upgrades are typically fast; when a node or route change is involved, support will coordinate any data migration and maintenance window.
4. Key things to note
- Disk usually only grows: upgrades can enlarge disk, but downgrades often can't shrink it directly — account for your data size.
- Back up first: take a full backup or snapshot before any change.
- Maintenance window: some changes need a brief reboot — schedule off-peak.
5. Cross-spec migration
For large changes (different region or architecture), it's safer to migrate to a new server: deploy on the new plan, sync data, switch DNS, verify, then retire the old one.
For specific upgrade/downgrade options, pricing and migration scheduling, contact sales on Telegram @aliyun370. Final billing and policy are confirmed by support.