Supabase incident

Log ingestion issues

Minor Resolved View vendor source →

Supabase experienced a minor incident on May 18, 2026 affecting Analytics, lasting 43m. The incident has been resolved; the full update timeline is below.

Started
May 18, 2026, 11:26 PM UTC
Resolved
May 19, 2026, 12:10 AM UTC
Duration
43m
Detected by Pingoru
May 18, 2026, 11:26 PM UTC

Affected components

Analytics

Update timeline

  1. investigating May 18, 2026, 11:26 PM UTC

    Customers may experience delayed log ingestion or periods where logs are unavailable. We will provide updates while we work to resolve the issue.

  2. monitoring May 18, 2026, 11:58 PM UTC

    Logging systems have returned to normal operation. During the incident, some logs may have been delayed or unavailable. While certain upstream log sources may retry delivery automatically, we cannot guarantee recovery of all missing logs generated during the affected time period. We will continue monitoring closely to ensure ongoing stability.

  3. resolved May 19, 2026, 12:10 AM UTC

    This incident has been resolved, and log delivery has returned to normal. During the incident, some logs may have been delayed or unavailable. While some upstream sources may retry delivery automatically, we cannot guarantee recovery of all missing logs from the affected period. Thank you for your patience while we worked to resolve this.