Supabase incident
Elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region
Supabase experienced a minor incident on March 18, 2026 affecting Storage, lasting 1h 54m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Mar 18, 2026, 04:27 PM UTC
We are currently investigating elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. Newly created projects may experience issues connecting to storage, while existing projects remain unaffected at this time. We are actively working to understand the full scope of the impact and will provide further updates as more information becomes available.
- investigating Mar 18, 2026, 04:58 PM UTC
We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. Newly created projects may still experience issues connecting to storage, while existing projects remain unaffected at this time. Our team is actively working to determine the root cause and assess the full impact. We will provide further updates as more information becomes available.
- investigating Mar 18, 2026, 05:30 PM UTC
We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. While we are still observing a higher-than-normal level of errors, initial findings indicate that the overall impact is lower than first expected. Many affected requests are succeeding upon retry. Our team is actively working to determine the root cause and will provide further updates as more information becomes available.
- identified Mar 18, 2026, 05:53 PM UTC
The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix.
- resolved Mar 18, 2026, 06:21 PM UTC
The fix was implemented. All impacted projects and newly created projects in the region are now successfully connecting to storage services.