Sudden, consistent timeouts with Supabase python package
Starting around 8:38am ET this morning, my team and I started seeing an enormous surge of
ReadError, ConnectTimeout, and RemoteProtocolError when attempting to fetch from our Supabase project (regardless of table). We are using supabase-py.
We then noticed consistent PoolTimeout errors, so we adjusted our http config to remove the max connection limit. Now the PoolTimeout is gone, but the other errors remain.
This is our http configuration:
Our app is deployed on Railway. The last deployment before today was four days ago, a completely unrelated and tiny bugfix.
We checked our Supabase usage in the dashboard, and don't appear to be hitting any limits. We also don't see any failed API requests in the logs at all, which leads me to believe this might be an issue with the Python package.
There have been no significant changes to our app. No sudden increase in traffic or users, no code changes, no dependency changes.
Can anyone help us resolve this, or point us in the right direction?
Thanks!5 Replies
Check your Roles to see if you've used up all of your connections https://supabase.com/dashboard/project/_/database/roles
I have, we have barely used half of our connections
We just tried upgrading to the next tier, but the issue persists. Do you have any idea why this is suddenly happening?
No I have no ideas
Is there anyone else I can speak to who might be able to help?
Supabase support would be your best bet https://supabase.com/dashboard/support/new