Logs degraded in multiple regions
Oct 30, 11:38 UTCOct 30, 12:29 UTC
Duration
51m
Impact
Informational
Root cause
Not disclosed
Supabase, 90 days
50 incidents
Affected
Not listed by the vendor.
Final update
We have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC. Service is now operating normally. We apologise for the disruption
Timeline
- Resolved · Oct 30, 12:29 UTC
We have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC. Service is now operating normally. We apologise for the disruption
- Monitoring · Oct 30, 12:11 UTC
A fix has been deployed and we are now monitoring the log service. We'll post another update as soon as we have one.
- Identified · Oct 30, 11:56 UTC
We have identified the cause of the Logs degradation and a fix is being prepared. Other services remain unaffected. We'll post another update as soon as we have one.
- Investigating · Oct 30, 11:38 UTC
We are currently investigating degraded Logs functionality in multiple regions. Some users may experience delayed, missing, or unavailable logs in the Dashboard and Logs API. Other services, including your database and APIs, are not affected at this time. Our team is actively investigating. We'll post another update as soon as we have one.
More from Supabase
Full historyDelayed Log Delivery from 14:10 - 15:30 UTClasted 53mLog Drain Issueslasted 47mElevated Mgmt API Error Rates in Multiple Regionslasted 3d 17hElevated Mgmt API Error Rates in Multiple Regionslasted 2h 13mProject lifecycle operation errors in the EU regionlasted 12h 3mProject lifecycle operations such as project creation, pausing, and restoration, in all regionslasted 1h 16m