outages.live
Live
LangfuseIncident · 2026-09-14 02:51 UTC

Delayed Ingestion for non v4 SDKs

ResolvedOfficial update

The incident has been resolved.

The latest update from Langfuse.

State

Resolved

Started

49 d ago

2026-09-14 02:51 UTC

Lasted

3 h 19 min

until 2026-09-14 06:10 UTC

Worst impact

Degraded

Timeline

4 updates
02:5103:4104:3005:2006:10
DegradedUpdate postedTimes in UTC

Investigating

2 h 23 min 72%

Monitoring

56 min 28%

Updates

Times in UTC

As posted by Langfuse

Resolved2026-09-14 06:10 UTC

The incident has been resolved.

Monitoring2026-09-14 05:14 UTC

We're making consistent progress in our backlog and are currently seeing delays of about 60 minutes.

Investigating2026-09-14 03:52 UTC

We considerably increased throughput of the batch job to write data into v4 data model. We are currently catching up processing data.

Investigating2026-09-14 02:51 UTC

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 ( ). We currently work on improving the batch job. All v4 compatible SDKs are not impacted by this. Upgrading SDKs is recommended.

Langfuse in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

17

Days with an incident

15

Median duration

1 h 12 min

This incident

2.8× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 h 20 min
median 1 h 12 min
90 days agoToday

Other Langfuse incidents

All incidents

Langfuse·Slow trace data retirival across API and UI in EU

should be finally resolved

Resolvedresolved 12 d ago

Langfuse·Degraded performance in Halo (Langfuse Assistant)

Issue with Langfuse Halo (assistant) is fixed.

Resolvedresolved 12 d ago

Langfuse·Degraded data serving in EU

Have been stable

Resolvedresolved 12 d ago

Langfuse·Degraded public API performance

Problematic workload was identified and isolated.

Resolvedresolved 14 d ago

Langfuse·Degraded ingestion for 20 projects

All projects ingesting as normal

Resolvedresolved 32 d ago

Follow Langfuse

Your coding agent knows when Langfuse is down, and tells you when a failure is theirs, not yours. You can also get Langfuse incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "langfuse" and tell me if Langfuse has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=langfuse
Slack
/feed subscribe https://outages.live/feed.xml?providers=langfuse

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane