Langfuse reported "Slow trace data retirival across API and UI in EU" on its status page at 2026-10-21 07:46 UTC.

Langfuse did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-21 07:46 UTC and ended at 2026-10-21 08:45 UTC. It lasted 59 min.

How do I get alerts for Langfuse?

Subscribe to the Langfuse live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Langfuse. outages.live reads it every few minutes and keeps every update.

LangfuseIncident · 2026-10-21 07:46 UTC

Slow trace data retirival across API and UI in EU

ResolvedOfficial update

should be finally resolved

The latest update from Langfuse.

State

Resolved

Started

12 d ago

2026-10-21 07:46 UTC

Lasted

59 min

until 2026-10-21 08:45 UTC

Worst impact

Degraded

Timeline

5 updates

07:4608:0108:1608:3008:45

DegradedUpdate postedTimes in UTC

Investigating

45 min 77%

Identified

14 min 23%

Updates

Times in UTC

As posted by Langfuse

Resolved2026-10-21 09:39 UTC

should be finally resolved

Monitoring2026-10-21 08:56 UTC

Looks like some timeout are still occurring. Monitoring.

Resolved2026-10-21 08:45 UTC

All replicas look healthy again

Identified2026-10-21 08:31 UTC

Slow clickhouse read replicas affecting performance across the service. Draining and replacing them.

Investigating2026-10-21 07:46 UTC

Slow traces data serving across API and UI

Langfuse in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 12 min

This incident

18% 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·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

Langfuse·Elevated error rates in In App Agent

The issue has been resolved.

Resolvedresolved 39 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