outages.live
Live
LangfuseIncident · 2026-08-15 17:28 UTC

prod-us: Delayed ingestion for prod-us

ResolvedOfficial update

We incurred a temporary delay on the legacy ingestion path for v4. This delay has been resolved. OTEL ingestion has not been impacted.

The latest update from Langfuse.

State

Resolved

Started

78 d ago

2026-08-15 17:28 UTC

Lasted

36 min

until 2026-08-15 18:05 UTC

Worst impact

Degraded

Timeline

2 updates
17:2817:3717:4717:5618:05
DegradedUpdate postedTimes in UTC

Investigating

36 min 100%

Updates

Times in UTC

As posted by Langfuse

Resolved2026-08-15 18:05 UTC

We incurred a temporary delay on the legacy ingestion path for v4. This delay has been resolved. OTEL ingestion has not been impacted.

Investigating2026-08-15 17:28 UTC

Currently the ingestion for the events table is delayed in the US environment. This happens only for data from non-latest major SDK versions. We are investigating this and have started a mitigation. The data should be up to date soon.

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

49% shorter than 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.cc/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.cc/feed.xml?providers=langfuse
Slack
/feed subscribe https://outages.cc/feed.xml?providers=langfuse

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane