- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 21of 100
What to do
Check whether you use Langfuse in us. 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 54m it lasted.
Anything that failed between 2026-09-02 16:02 UTC and 2026-09-02 16:56 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 4
- investigating
We are observing OTEL ingestion backlog in US region
provider
- identified
A deployment rollout coincided with a traffic spike, resulting in an unusually large backlog. Adjusting our autoscaling to absorb the backlog faster.
provider
- monitoring
Backlog is almost completely gone. Ingestion delay is < 1 min.
provider
- resolved
Completely back to normal
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-75414c57cb
Is Langfuse still down?
No, this incident was resolved 2026-09-02 16:56 UTC. For Langfuse's live state, see https://down.guide/langfuse.
How long did it last?
54m, from 2026-09-02 16:02 UTC to 2026-09-02 16:56 UTC, by the times Langfuse posted.
What was affected?
Langfuse named in us.
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.