Supabase incident

Log ingestion impaired

Resolved after 5 hours 50 minutes, on October 12, 2026.

resolved Oct 13, 2026, 01:30 AM UTC

We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation.

Started
Oct 12, 2026, 07:39 PM UTC
Resolved
Oct 13, 2026, 01:30 AM UTC
Duration
5h 50m
Detected by Pingoru
Oct 12, 2026, 07:39 PM UTC

Update timeline

  1. investigating Oct 12, 2026, 07:39 PM UTC

    Log ingestion is currently impaired. Logs may be delayed or unavailable. We are investigating the issue and working to restore normal functionality. We will provide further updates as more information becomes available.

  2. investigating Oct 12, 2026, 07:39 PM UTC

    Log ingestion is currently impaired. Logs may be delayed or unavailable. We are investigating the issue and working to restore normal functionality. We will provide further updates as more information becomes available.

  3. identified Oct 12, 2026, 08:09 PM UTC

    We have identified the issue impacting log ingestion. Logs may be delayed or unavailable. We are working to restore normal functionality.

  4. identified Oct 12, 2026, 08:09 PM UTC

    We have identified the issue impacting log ingestion. Logs may be delayed or unavailable. We are working to restore normal functionality.

  5. identified Oct 12, 2026, 08:56 PM UTC

    We are implementing a fix for the log ingestion issue, and traffic is beginning to recover. We are continuing to work toward full recovery.

  6. identified Oct 12, 2026, 08:56 PM UTC

    We are implementing a fix for the log ingestion issue, and traffic is beginning to recover. We are continuing to work toward full recovery.

  7. identified Oct 12, 2026, 10:17 PM UTC

    We continue to work on a fix as traffic continues to recover. We will provide further updates as more information becomes available.

  8. identified Oct 12, 2026, 10:17 PM UTC

    We continue to work on a fix as traffic continues to recover. We will provide further updates as more information becomes available.

  9. identified Oct 13, 2026, 12:05 AM UTC

    We are continuing to implement the fix as traffic recovers. We will provide further updates as progress continues.

  10. identified Oct 13, 2026, 12:05 AM UTC

    We are continuing to implement the fix as traffic recovers. We will provide further updates as progress continues.

  11. monitoring Oct 13, 2026, 12:35 AM UTC

    The fix has been implemented, and the system has returned to normal operation. Log ingestion is back to normal, and we are monitoring for stability.

  12. monitoring Oct 13, 2026, 12:35 AM UTC

    The fix has been implemented, and the system has returned to normal operation. Log ingestion is back to normal, and we are monitoring for stability.

  13. resolved Oct 13, 2026, 01:30 AM UTC

    We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation.

  14. resolved Oct 13, 2026, 01:30 AM UTC

    We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation.

  15. resolved Oct 13, 2026, 01:30 AM UTC

    We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation.

Your product runs on more than Supabase

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →