Supabase · incident

Edge Function Latency

Provider lifecycle: monitoring

Get one resolution alert

Enter an email and we’ll send a confirmation link. We use it only for this incident and delete it after the alert.

Degraded performance
Provider incident confirmed

Supabase Status has not marked this as resolved. The latest official update is shown first below.

Official timeline

Provider updates

2
  1. monitoring

    Error rates have returned to normal, and the service is operating as expected. The team continues to investigate the underlying cause of the latency and spike in 503 errors.

  2. investigating

    We are investigating reports of increased Edge Function latency and elevated rates of HTTP 503 responses, beginning at approximately 06:00 UTC. Our team is working to identify the cause and will provide further updates as they become available.