This morning, our database went down for 38 minutes. No read or write queries were being returned starting at 8:38am.
The cause seems to be a memory bug in a library we were using:
We've detected a memory leak within PostgREST, triggered by long-running connections, documented here:
https://github.com/PostgREST/postgrest/issues/2638
This bug affected PostgREST versions under v10.2, with it being addressed in v10.2 - your project was among the affected ones running v10.1.2.
— Supabase engineer
Supabase has since upgraded the version of that library to solve the memory leak, so hopefully that specific problem won't happen again.
Will we lose read access again this year for > 5 minutes, or write access for > 12 hours?
In total, we've had two outages this year:
1,000🏅 Top traders
| # | Name | Total profit |
|---|---|---|
| 1 | Ṁ50 | |
| 2 | Ṁ40 | |
| 3 | Ṁ5 | |
| 4 | Ṁ2 | |
| 5 | Ṁ1 |