Hello,

Your analysis is correct. The issue lies within the Zeabur CLI tool itself: it has a fixed 30-second total timeout for upload requests, and the entire zip package must be uploaded within those 30 seconds. Currently, there is no parameter to increase this. For a compressed file of about 50MB, this means the upload speed to the S3 Hong Kong node must be stably maintained at around 14 Mbps or higher to succeed. This explains why it fluctuates during peak evening hours—which perfectly matches the timeline you recorded (mostly failing in the evening, occasionally succeeding).

We have logged this issue and will adjust the CLI tool to allow the timeout to scale based on file size.

Before the fix is released, here are a few suggestions:

1. We see that you have switched to GitHub deployment (naraka-git) and it is working properly—this is currently the most stable method as it bypasses local uploads entirely.
2. Drag-and-drop uploading of zip files directly from the Dashboard does not have this 30-second limit and can serve as a backup.
3. If you still prefer to use the CLI for deployment, you can reduce the size of the upload package by excluding large static assets like images.

Please let us know if you have any other questions.