Incidents reported on status page for Privilist https://status.privilist.com/ en https://status.privilist.com/ Wed, 20 May 2026 03:40:58 +0000 https://status.privilist.com/#9eb019c38137f5bd72302c147f1246dcb2a9d487dc42995e14e03bee2059f064 Database recovered https://status.privilist.com/ Wed, 20 May 2026 03:29:16 +0000 https://status.privilist.com/#9eb019c38137f5bd72302c147f1246dcb2a9d487dc42995e14e03bee2059f064 Database went down https://status.privilist.com/ Wed, 20 May 2026 03:16:55 +0000 https://status.privilist.com/#2054aabaed1535b30d35b110d2358e6710a05ea86a6eabe63055ada78c069412 Database recovered https://status.privilist.com/ Wed, 20 May 2026 03:16:17 +0000 https://status.privilist.com/#1af9746ceb5e27165aeb044e88063c2acfce05167529e4176ba74cb83a1f2015 Auth recovered https://status.privilist.com/ Wed, 20 May 2026 03:10:30 +0000 https://status.privilist.com/#1af9746ceb5e27165aeb044e88063c2acfce05167529e4176ba74cb83a1f2015 Auth went down https://status.privilist.com/ Wed, 20 May 2026 02:56:49 +0000 https://status.privilist.com/#2054aabaed1535b30d35b110d2358e6710a05ea86a6eabe63055ada78c069412 Database went down https://status.privilist.com/ Wed, 20 May 2026 02:17:16 +0000 https://status.privilist.com/#699975fabc1a2606e3a5c4fa1f83ae9c3a6b3f36c6911fae4baa4a3745de3546 Database recovered https://status.privilist.com/ Wed, 20 May 2026 02:13:16 +0000 https://status.privilist.com/#8676c13549bb0c706db508dadd692d137319c982d493d4c05052d51ad53b2526 Auth recovered https://status.privilist.com/ Tue, 19 May 2026 15:40:57 +0000 https://status.privilist.com/#699975fabc1a2606e3a5c4fa1f83ae9c3a6b3f36c6911fae4baa4a3745de3546 Database went down https://status.privilist.com/ Tue, 19 May 2026 15:40:14 +0000 https://status.privilist.com/#8676c13549bb0c706db508dadd692d137319c982d493d4c05052d51ad53b2526 Auth went down https://status.privilist.com/incident/867064 Wed, 08 Apr 2026 11:19:00 -0000 https://status.privilist.com/incident/867064#8b8dbb61de65999909d5c1db7b028c99bf17eb8845443804ae86edf6ee5ecb9e ## Incident: 2026-04-08 Supabase Instance Freeze **Timeline**: - Last working: April 7, ~07:37 UTC - Detected: April 8, ~05:30 UTC - Resolution: Manual reboot via Supabase dashboard - Duration: ~22 hours downtime **Impact**: All apps (admin, teams, barbaard, menu, mobile) unable to authenticate **Root Cause**: Supabase instance became unresponsive (not auto-pause) **Prevention**: - [ ] Deploy health-check edge function - [ ] Set up external monitoring (Uptime Robot) - [ ] File support ticket for RCA - [ ] Fix recurring database errors