Skip to main content
Langfuse

Slow trace data retirival across API and UI in EU

Degraded Lasted 59m · started · Langfuse's page

Level
confirmed
Worst impact
Degraded
Regions
eu
Down Index
21of 100

What to do

  • Check whether you use Langfuse in eu. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 59m it lasted.

    Anything that failed between 2026-10-21 07:46 UTC and 2026-10-21 08:45 UTC may need a replay.
  • Subscribe to Langfuse's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=langfuse works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Langfuse 5

  1. investigating

    Slow traces data serving across API and UI

    provider

  2. identified

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

    provider

  3. resolved

    All replicas look healthy again

    provider

  4. monitoring

    Looks like some timeout are still occurring. Monitoring.

    provider

  5. resolved

    should be finally resolved

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-da998e0dd5

Is Langfuse still down?

No, this incident was resolved 2026-10-21 08:45 UTC. For Langfuse's live state, see https://down.guide/langfuse.

How long did it last?

59m, from 2026-10-21 07:46 UTC to 2026-10-21 08:45 UTC, by the times Langfuse posted.

What was affected?

Langfuse named in eu.

What caused it?

Langfuse hasn't published a root cause. If it does, it shows here.

Where does this come from?

Langfuse's official status page, https://status.langfuse.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.