Zeabur is shutting down: move workloads before December 1, not December 31

Zeabur will pause shared-cluster services and begin shutting down dedicated servers on December 1. Here is the migration checklist customers need before the platform closes.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

Zeabur customers should plan around December 1—not the December 31 final shutdown date. Shared-cluster services are scheduled to pause on December 1, while dedicated servers can stop on their individual expiration dates any time from December 1 through December 31.[1]

What is changing

NowNew dedicated-server and domain purchases have stopped. Self-service domain transfers, refund requests, and migration support are available.[1]
Dec. 1Dedicated-server renewals stop, servers begin expiring, and running services on shared clusters are paused.[1]
Dec. 31All dedicated servers and shared clusters are scheduled to stop operating.[1]

Reporting cutoff: October 22, 2026, 1:26 p.m. EDT (17:26 UTC). Zeabur’s shutdown announcement and preliminary incident report were rechecked at this cutoff.

Why this is a separate story from the breach

Zeabur’s October security incident is the backdrop, but the shutdown creates a different reader decision: when and how to move hosted applications, databases, domains, and secrets. Zeabur says it chose to wind down after reassessing the work and responsibility required to continue operating following two security incidents; it also cites increasing platform complexity and questions about its long-term value.[1]

BleepingComputer reported the shutdown on October 20 as a consequence of the second security breach in two months and repeated the December schedule.[3] That report is useful public corroboration that the closure was announced, but its breach figures and shutdown chronology substantially trace back to Zeabur’s own disclosures rather than a separate forensic investigation.

The deadline is workload-specific

Service First operational deadline What Zeabur says will happen
Dedicated servers Individual expiration date, December 1–31 Renewals are disabled starting December 1; each server shuts down when its current term expires.[1]
Shared clusters December 1 Running services are paused. Zeabur says users can restart them manually to back up data.[1]
All dedicated servers and shared clusters December 31 Operation stops.[1]
Data export, deletion, and support Not announced Zeabur says the final export deadline, deletion date, and support-closing date are not yet finalized.[1]

That last row is not extra time. Zeabur explicitly tells users to follow the service shutdown schedule instead of waiting for a later deletion deadline.[1] Its migration guide is available now and is expected to be updated for more services and scenarios.[1]

Security work must travel with the migration

Moving the application is not enough. Zeabur’s preliminary report says an attacker read 3,218,965 environment-variable records and account, project, environment, and service data associated with 321,810 accounts. It also reports confirmed root sign-ins to 101 GCP dedicated servers and attacker-added SSH keys on 50 of them.[2]

Zeabur directs every user to replace passwords and keys stored on the platform—even credentials replaced after the August incident—and says old credentials should be revoked before new ones are created and deployed.[2] For the affected GCP dedicated servers, Zeabur’s recommendation is to back up data and rebuild the server; it calls rebuilding the most reliable way to remove possible backdoors.[2]

Practical migration checklist

The steps below are practical guidance derived from the vendor deadlines and incident instructions, not a guarantee that every Zeabur workload can be moved the same way.

  1. Inventory the whole dependency chain. Record every Zeabur service, database, persistent volume, domain, build/deploy integration, external API, and dedicated-server expiration date.
  2. Prioritize anything that can stop December 1. Treat shared-cluster workloads and dedicated servers expiring early in the month as the first wave.
  3. Create and test recoverable backups. Confirm that application data, database exports, file uploads, configuration, and deployment instructions can be restored outside Zeabur. Do not treat “download completed” as proof of a working restore.
  4. Build the replacement before cutting over. Restore into the new environment, test application behavior, health checks, scheduled jobs, outbound email, storage, and third-party integrations, then schedule DNS and traffic changes with a rollback path.
  5. Rotate secrets into the destination. Revoke exposed-capable passwords, API keys, cloud keys, database credentials, signing keys, and encryption keys at their providers; create replacements and deploy only the new values.[2]
  6. Move domains deliberately. Zeabur says self-service transfers are available for domains bought through the platform. Verify registrar ownership, DNS records, nameservers, transfer locks, and renewal settings after the move.[1]
  7. Preserve evidence before systems disappear. Keep authorized copies of relevant access, deployment, billing, and incident records needed for troubleshooting, security review, or a compensation request.

What remains unknown

  • The final data-export deadline, data-deletion date, and Zeabur Support closing date were still unannounced at the reporting cutoff.[1]
  • Zeabur’s incident investigation remains ongoing. Its report says the initial access path cannot yet be confirmed. It also says whether some backups and source-code uploads were downloaded cannot be confirmed.[2]
  • No public promise guarantees that every service will remain available through December 31; Zeabur says the opposite for services with earlier dates.[1]

Bottom line

For Zeabur users, December 31 is the end of the platform—not the safe date to begin planning. Use each workload’s December 1 status and dedicated-server expiration date as the real deadline, test the move before cutover, and complete the credential and compromised-host work alongside the migration.

Sources

  1. Zeabur is shutting down: what happens next — Zeabur, October 17, 2026; live recheck October 22, 2026.
  2. Zeabur October 2026 security incident (preliminary report) — Zeabur, October 19, 2026; live recheck October 22, 2026.
  3. Zeabur shutting down after second security breach in two months — BleepingComputer, October 20, 2026.