New Multi-region uptime checks and custom-domain status pages

Delayed Ingestion for non v4 SDKs

Minor Impact Resolved Notice published: September 14, 2026
View the provider incident record →

Current answer

Langfuse experienced a minor incident: Delayed Ingestion for non v4 SDKs. Resolved on Sep 14, 2026.

Official Langfuse status page Current Langfuse status Provider update:

The notice publication date does not establish the outage start. Provider resolved: .

Looking for an update now? Check the current status, or follow Langfuse for future changes.

Provider notice timeline

Investigating Investigating Monitoring
Affected Components
Ingestion API

Incident Timeline

Resolved
The incident has been resolved.
Sep 14, 2026 at 6:10 AM UTC
Monitoring
We're making consistent progress in our backlog and are currently seeing delays of about 60 minutes.
Sep 14, 2026 at 5:14 AM UTC
Investigating
We considerably increased throughput of the batch job to write data into v4 data model. We are currently catching up processing data.
Sep 14, 2026 at 3:52 AM UTC
Investigating
We currently experience an ingestion delay of old SDKs by 3 hours. This is due to performance issues in our batch job which moves data into the v4 data model (https://langfuse.com/changelog/2026-08-17-langfuse-v4).



We currently work on improving the batch job. All v4 compatible SDKs are not impacted by this. Upgrading SDKs is recommended.
Sep 14, 2026 at 2:51 AM UTC
Was your business affected by this Langfuse outage?
Follow Langfuse and route available status alerts to email or a team channel.