- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 100
What to do
Check whether your product depends on Langfuse. 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 3h 26m it lasted.
Anything that failed between 2026-08-25 10:16 UTC and 2026-08-25 13:42 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 2
- monitoring
The legacy ingestion queue is experiencing latency degradation up to 5 minutes. We have scaled up our infrastructure in response and are monitoring the situation. We recommend to switch to the new OTEL ingestion queue.
provider
- resolved
Issue resolved since 12:30. Legacy ingestion pipeline is fully operational.
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-06e0d61d4d
Is Langfuse still down?
No, this incident was resolved 2026-08-25 13:42 UTC. For Langfuse's live state, see https://down.guide/langfuse.
How long did it last?
3h 26m, from 2026-08-25 10:16 UTC to 2026-08-25 13:42 UTC, by the times Langfuse posted.
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.