The free-tier peak hours restriction is gated on your plan tier, not strictly on your target region's local clock. The warning can surface a different region's peak window than the one your service deploys to, so deploys may remain blocked even after 20:00 SGT if another region is still in its peak window. This is expected behavior for the Free plan, not a stuck gate. Your two options are deploying outside peak hours (waiting until all regions' windows have passed) or upgrading to the Hobby plan, which removes the restriction entirely. Once you can deploy, you also have one staged change (build watch patterns on @go/api) that will need to be applied.

I still need a human review. The project UI explicitly names asia-southeast1-eqsg3a and states the blocked window is 8 AM–8 PM Asia/Singapore. If the actual gate is based on all regions rather than that named region and timezone, please confirm the authoritative global window and update or clarify the UI/documentation. I am not requesting an upgrade or region change; I need the expected next deploy time and confirmation that this account/service is not stuck.

To correct our earlier reply: the peak-hours restriction checks only your service's own deploy region, not every region. For asia-southeast1-eqsg3a the documented window is 8 AM - 8 PM Asia/Singapore, and deploys should be accepted from 20:00 SGT onward.

Your account is not stuck. Your deployment history shows multiple successful deploys after 20:00 SGT today, so the gate has cleared. The brief block you saw at 20:00:24 and 20:01:30 may have been a narrow server-side timing edge, but it resolved within minutes.

You still have one unapplied staged change (build watch patterns on @go/api) that will need to be deployed separately.