Supabase pooler issue @us-east-2
🔢DB Connections
Hi everyone!
I have an application hosted on Render that was running perfectly until last week. Starting on the 12th, I received reports that the app was returning the following error:
status: 500
message: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
I looked into it and read that Supabase was having issues in the us-east-2 region, which is exactly where my application is located. I decided to wait for an official fix.
However, as of right now, my application is still hitting the same problem. Actually, it has become intermittent: it starts working, and everything flows as expected, then suddenly, after 1 or 2 minutes, it stops responding and starts returning the error above. Then the cycle repeats.
I have an older version of this app kept for backup purposes (to be deleted soon) that also runs on Render, but the database is in the us-east-1 region. Over there, everything is working normally, with no pooler-related messages.
Does anyone know what might be going on? The Supabase Status page says the service is operational with no recent incidents... but I can't find the reason why my application stopped working in the us-east-2 region.
Thanks in advance for any insights!
I have an application hosted on Render that was running perfectly until last week. Starting on the 12th, I received reports that the app was returning the following error:
status: 500
message: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
I looked into it and read that Supabase was having issues in the us-east-2 region, which is exactly where my application is located. I decided to wait for an official fix.
However, as of right now, my application is still hitting the same problem. Actually, it has become intermittent: it starts working, and everything flows as expected, then suddenly, after 1 or 2 minutes, it stops responding and starts returning the error above. Then the cycle repeats.
I have an older version of this app kept for backup purposes (to be deleted soon) that also runs on Render, but the database is in the us-east-1 region. Over there, everything is working normally, with no pooler-related messages.
Does anyone know what might be going on? The Supabase Status page says the service is operational with no recent incidents... but I can't find the reason why my application stopped working in the us-east-2 region.
Thanks in advance for any insights!
