A downtime occur from 2021-07-28T17:56 to 2021-07-28 18:16:08, everything should return to normal now.
NodeRSSBot Status
@noderss_bot will be down for maintenance now. Will recover soon
Service are being gradually restored
The demo uses Supabase. Since Supabase has closed IPv4 connections, the demo has switched to an IPv6 network and testing shows that it can connect normally. However, recently there have been frequent errors of "relation 'xxx' not found," but restarting the bot restores to normal. The detailed reasons are still under investigation.
NodeRSSBot Status
The demo uses Supabase. Since Supabase has closed IPv4 connections, the demo has switched to an IPv6 network and testing shows that it can connect normally. However, recently there have been frequent errors of "relation 'xxx' not found," but restarting the…
Recoved after switching the pooling config to session mode in supabase dashboard.
NodeRSSBot Status
The demo uses Supabase. Since Supabase has closed IPv4 connections, the demo has switched to an IPv6 network and testing shows that it can connect normally. However, recently there have been frequent errors of "relation 'xxx' not found," but restarting the…
Supabase charge for Egress bandwith. Recently Demo comsure over 8G per month which exceeded their free plan. So I just increase the fetch gap for the demo. I may consider some alternatives for supbase when I have some free time from my job. The database is a PostgreSQL which a pg_cron extension to fixes some dead feed. It is around 50MB but read bandwidth is around 8G per month. Any suggestion?