---
id: "INC-supabase-01M4RT1HA64EWGKK2NJJ00Z7M5"
kind: "incident"
aliases: []
title: "Supabase: Log ingestion impaired"
severity: "medium"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "Supabase", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["database", "incident", "ops", "postgres", "supabase", "vendor"]
not_affected_if: []
published_at: "2026-10-12T19:39:42+00:00"
first_seen_at: "2026-10-23T19:12:22+00:00"
updated_at: "2026-10-23T20:17:58+00:00"
sources: [{"source": "statuspage", "url": "https://status.supabase.com/incidents/01M4RT1HA64EWGKK2NJJ00Z7M5", "first_seen_at": "2026-10-23T19:12:22+00:00"}]
---

# Supabase: Log ingestion impaired

## Affected

- vendor:Supabase affected ? fixed ?

## Timeline

- 2026-10-23T19:12:22+00:00 statuspage https://status.supabase.com/incidents/01M4RT1HA64EWGKK2NJJ00Z7M5

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_