CRITICAL: Compute Stuck in "Idle" State & "Failed to Fetch" Error - Manual Wake-up Fails
☁️ServerlessNeon🐘Postgres
Hi Neon Team & Community,
I am facing a critical blocking issue with my Neon Postgres project where the database refuses to accept connections and the Compute instance seems completely stuck in an "Idle" state, despite having ample quota remaining.
Here are the specific details of the failure:
1. The Symptoms:
Compute Status: Stuck on "Idle".
Wake-up Failure: I tried running SELECT 1; via the SQL Editor and external tools to trigger a wake-up, but the status does not change to "Active".
Quota: My compute usage is only 3.3 hours (out of 100 hours limit), so this is not a quota issue.
Client Error: When trying to connect via my application/browser client, I get a persistent Failed to fetch error.
2. The Error Log: I received an unexpected error with the following ID:
Verified Connection String (Using Pooled Connection with sslmode=require).
Attempted to force wake-up via Dashboard SQL Editor (Result: No response/Stuck).
Checked Network/Firewall (Issue persists on different networks).
Tried creating a new Branch (Issue persists).
4. Request: It seems like the compute endpoint for my project might be frozen or experiencing a "Cold Start" failure on the backend. Could you please check the logs associated with Error ID 5e512608436441729d6577b5888997c8 and help reset the state?