Not workin

[T6rabek]

Hello everyone,

My project had stopped for 2 hours and i upgraded to pro but 1 hour passed it is not still live. I have restard but did not work

[Samielakkad]

If this project is in EU-CENTRAL-1 (Frankfurt), it matches today's active Supabase incident rather than a billing or plan-upgrade delay:

https://status.supabase.com/

Supabase reports that an infrastructure-provider connectivity issue left some Frankfurt projects in a stuck state. Their latest update says the impacted projects have been restarted and functionality restored, and the incident is now being monitored. They specifically ask customers whose Frankfurt project is still affected to open a support ticket for individual investigation.

What to do now:

1. Check the project's region. If it is Frankfurt, include the project ref and this incident in a private support ticket: “Projects in stuck state in EU-CENTRAL-1 (Frankfurt)”.
2. Do not keep issuing restart requests; a plan upgrade or another restart will not fix an infrastructure-level stuck state and can make the timeline harder to diagnose.
3. Record the UTC time when it stopped, the upgrade time, and the last restart attempt for support.
4. If the project is in another region, open a ticket anyway because the status page currently shows the other regions as operational; that would need project-specific investigation.

Do not post the project ref or credentials publicly. The Pro upgrade changes the plan, but it does not itself recover a project that the platform has to repair.

[T6rabek]

Thanks for the update. It worked

…

On Thu, Jul 16, 2026, 15:54 Sami El Akkad ***@***.***> wrote: If this project is in *EU-CENTRAL-1 (Frankfurt)*, it matches today's active Supabase incident rather than a billing or plan-upgrade delay: https://status.supabase.com/ Supabase reports that an infrastructure-provider connectivity issue left some Frankfurt projects in a stuck state. Their latest update says the impacted projects have been restarted and functionality restored, and the incident is now being monitored. They specifically ask customers whose Frankfurt project is still affected to open a support ticket for individual investigation. What to do now: 1. Check the project's region. If it is Frankfurt, include the project ref and this incident in a private support ticket: *“Projects in stuck state in EU-CENTRAL-1 (Frankfurt)”*. 2. Do not keep issuing restart requests; a plan upgrade or another restart will not fix an infrastructure-level stuck state and can make the timeline harder to diagnose. 3. Record the UTC time when it stopped, the upgrade time, and the last restart attempt for support. 4. If the project is in another region, open a ticket anyway because the status page currently shows the other regions as operational; that would need project-specific investigation. Do not post the project ref or credentials publicly. The Pro upgrade changes the plan, but it does not itself recover a project that the platform has to repair. — Reply to this email directly, view it on GitHub <#47986?email_source=notifications&email_token=BFSVUA4GSJ4NRP74GUDRZSD5FCX7BA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGYYDMNJTUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17660653>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFSVUA4UXSLTCF4IFTBAZJT5FCX7BAVCNFSNUABIKJSXA33TNF2G64TZHMZDCNBVHA3TCOJTHNCGS43DOVZXG2LPNY5TCMBUGM3TENZVUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BFSVUA2QIHEQ5WF7H4QPFN35FCX7BA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGYYDMNJTUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/BFSVUA6WVJYZZQUYMYW6IRL5FCX7BA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGYYDMNJTUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>