Project stuck in "Coming up" for 5 days after unpause (ca-central-1) — Auth returning 400s for existing users #48050
Answered
by
Davidobadun
Davidobadun
asked this question in
Questions
Replies: 2 comments
|
When did you file your support ticket? |
0 replies
|
i filed it on Monday.
The issue just got resolved.
Thank you ,
David Obadun
…________________________________
From: GaryAustin1 ***@***.***>
Sent: Friday, 17 July 2026 18:15:09
To: supabase/supabase ***@***.***>
Cc: David Obadun ***@***.***>; Author ***@***.***>
Subject: Re: [supabase/supabase] Project stuck in "Coming up" for 5 days after unpause (ca-central-1) — Auth returning 400s for existing users (Discussion #48050)
When did you file your support ticket?
—
Reply to this email directly, view it on GitHub<#48050?email_source=notifications&email_token=AI5RX5MXIMX7IRHFC7SNGXD5FKQO3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWG43TANJXUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17677057>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AI5RX5L6OS5AXKC4F6W27F35FKQO3AVCNFSNUABIKJSXA33TNF2G64TZHMZDCNBVHA3TCOJTHNCGS43DOVZXG2LPNY5TCMBUGQ4TINZWUF3AE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
0 replies
Answer selected by
GaryAustin1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Project details
while the project is in this state
What happened
My free-tier project was paused due to inactivity. I unpaused it on Monday, July 13,
and it has been stuck in "Coming up..." on the dashboard for 5 days now.
Current dashboard state:
Impact
Users that existed before the pause cannot log in — Auth requests return 400
(visible in Unified Logs). Nothing was changed on my end; same project URL and anon key.
What I've tried
while the project is in this transitional state
Suspected cause
Timeline lines up with the June 30 "Project status change failures in multiple regions"
capacity incident — ca-central-1 is on the affected region list. The restore job appears
stuck/orphaned and likely needs to be manually re-queued.
Could someone from the team take a look and kick the restore for this project?
Happy to provide any additional info. Thanks!
All reactions