Supabase incident
Edge Functions experiencing high response times in ap-northeast-1 and ap-northeast-2
Affected components
Update timeline
- investigating Mar 06, 2026, 02:26 PM UTC
We are currently investigating the cause for increased response times.
- investigating Mar 06, 2026, 02:47 PM UTC
We are continuing to investigate reports of Edge Functions experiencing high response times in Asia Pacific regions Our team is still working to determine the underlying cause. We understand the disruption this may be causing and are treating this with high priority.
- investigating Mar 06, 2026, 03:17 PM UTC
We are continuing to investigate reports of Edge Functions experiencing high response times in Asia Pacific regions Our team is still working to determine the underlying cause. We understand the disruption this may be causing and are treating this with high priority.
- identified Mar 06, 2026, 03:46 PM UTC
Response times in the ap-northeast-1 (Tokyo) region have improved following mitigation efforts. We are currently rolling out the fix to the ap-northeast-2 (Seoul) region. Further updates will be provided as the rollout continues.
- monitoring Mar 06, 2026, 03:56 PM UTC
Response times in both the ap-northeast-1 (Tokyo) and ap-northeast-2 (Seoul) regions have now stabilised. We will continue to monitor the systems closely to ensure stability.
- resolved Mar 06, 2026, 07:36 PM UTC
Both regions are now working as usual.
Looking to track Supabase downtime and outages?
Pingoru polls Supabase's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Supabase reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Supabase alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required