Avani-Media
Hi Supabase team, Our free-tier project, Avani Reporting Platform (qrkghrvlcjonkayxzhwg, Seoul / ap-northeast-2), remains unavailable. SQL Editor and database clients fail with: FATAL: 57P03: the database system is not accepting connections DETAIL: Hot standby mode is disabled. Support has already restarted the project onto a fresh instance, but the issue persists. The Postgres logs on October 3, 2026, at 05:28 UTC** show: redo done at 35/13FFFDD8 could not write to file "pg_wal/xlogtemp.40495": No space left on device startup process (PID 40495) exited with exit code 1 shutting down due to startup process failure Recovery repeatedly reaches the end of WAL replay, then fails when writing a new WAL file. The dashboard shows a provisioned 2 GB disk; an earlier reading showed approximately 1.93 GB used. This appears similar to [[#48507](https://github.com/orgs/supabase/discussions/48507)](https://github.com/orgs/supabase/discussions/48507) and [[#45958](https://github.com/orgs/supabase/discussions/45958)](https://github.com/orgs/supabase/discussions/45958). We had accumulated temporary Convertr ingestion data, and a large cleanup operation may have added further WAL pressure. Could someone escalate this to the infrastructure team to check whether the disk can be temporarily expanded or space safely reclaimed **without removing WAL required for recovery or losing existing data**? Once connections are restored, we plan to disable the ingestion and cleanup jobs temporarily, back up important data, and clean up staging data in small batches. We would like to remain on Free if possible. This supports reporting we need by Monday, October 5. We’d really appreciate help recovering the project safely. Happy to provide additional details privately through our existing support ticket. Thank you!