Langfuse outage history
We hold 27 Langfuse incidents from Langfuse's status page, the newest from Oct 21, 2026. 25 of the 27 listed carry Langfuse's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.
Uptime & history
Tracking since Jun 22, 2026% of our checks that found Langfuse fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.
- Slow trace data retirival across API and UI in EUOct 21, 2026 → Oct 21, 2026 · resolved
- Degraded performance in Halo (Langfuse Assistant)Oct 20, 2026 → Oct 20, 2026 · resolved
- Degraded data serving in EUOct 20, 2026 → Oct 20, 2026 · resolved
- Degraded public API performanceOct 19, 2026 → Oct 19, 2026 · resolved
- Degraded ingestion for 20 projectsSep 30, 2026 → Sep 30, 2026 · resolved
- Elevated error rates in In App AgentSep 23, 2026 → Sep 23, 2026 · resolved
- OTEL ingestion queue delay over 10 minutes in USSep 16, 2026 → Sep 16, 2026 · resolved
- Delayed Ingestion for non v4 SDKsSep 13, 2026 → Sep 14, 2026 · resolved
- OTEL Ingestion Delay exceeds 10 minutesSep 8, 2026 → Sep 8, 2026 · resolved
- Degraded OTEL ingestion in US regionSep 2, 2026 → Sep 2, 2026 · resolved
- Performance degradation on ingestion pathAug 25, 2026 → Aug 25, 2026 · resolved
- Latency degradation on legacy ingestion queueAug 25, 2026 → Aug 25, 2026 · resolved
How Langfuse fails
Since Jul 2, 2026, Langfuse's status page has marked 4 Langfuse components as impaired, across 331 of our five-minute readings. Ingestion API accounts for the most: 187 readings (about 16 hours) on 12 days, most recently on Sep 30, 2026. Next is LLM-as-a-judge, with 76 readings on 5 days. We hold 27 Langfuse incidents from Langfuse's status page, the earliest from Jun 8, 2026. Of the 25 that Langfuse closed with an end time, the median lasted 57 minutes.
| Component | Outage | Degraded | Maint. | Days | Last |
|---|---|---|---|---|---|
| Ingestion API | — | 187 | — | 12 | Sep 30, 2026 |
| LLM-as-a-judge | — | 76 | — | 5 | Oct 21, 2026 |
| UI | — | 35 | 3 | 5 | Oct 22, 2026 |
| Public API | — | 33 | 3 | 4 | Oct 22, 2026 |
Incidents by month: Jun 2026: 5 · Jul 2026: 2 · Aug 2026: 10 · Sep 2026: 6 · Oct 2026: 4
Counts are five-minute readings of Langfuse's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.
Every recorded incident
October 2026 · 4
- Oct 21, 2026Slow trace data retirival across API and UI in EUminor59 min5 updates
- Oct 20, 2026Degraded performance in Halo (Langfuse Assistant)none48 min3 updates
- Oct 20, 2026Degraded data serving in EUminor26 min3 updates
- Oct 19, 2026Degraded public API performanceminor45 min2 updates
September 2026 · 6
- Sep 30, 2026Degraded ingestion for 20 projectsmajor6 h 20 min3 updates
- Sep 23, 2026Elevated error rates in In App Agentminor7 min2 updates
- Sep 16, 2026OTEL ingestion queue delay over 10 minutes in USminor1 h 12 min2 updates
- Sep 13, 2026Delayed Ingestion for non v4 SDKsminor3 h 19 min4 updates
- Sep 8, 2026OTEL Ingestion Delay exceeds 10 minutesminor1 h 35 min2 updates
- Sep 2, 2026Degraded OTEL ingestion in US regionminor54 min4 updates
August 2026 · 10
- Aug 25, 2026Performance degradation on ingestion pathminor1 h 5 min2 updates
- Aug 25, 2026Latency degradation on legacy ingestion queueminor3 h 26 min2 updates
- Aug 21, 2026[Triggered] [TEST] [HIPAA] OTEL Ingestion Delay exceeds 10 minutesminorend not published
- Aug 20, 2026[Triggered] [TEST] [PROD-EU] OTEL Ingestion Queue Delay Status Page (10 minutes)minorend not published
- Aug 20, 2026Evaluations are delayed in EUminor1 h 49 min3 updates
- Aug 19, 2026Longer v3 -> v4 propagation delayminor2 h 34 min3 updates
- Aug 18, 2026Degraded LLMaJ execution in EUminor1 h 19 min4 updates
- Aug 15, 2026prod-us: Delayed ingestion for prod-usminor36 min2 updates
- Aug 12, 2026Latency increase eval execution up to 40 minutes is resolvedminor1 h 41 min3 updates
- Aug 3, 2026[US] Ingestion Delaysminor38 min3 updates
July 2026 · 2
- Jul 14, 2026502 BAD Gateway errors on UIminor1 h 7 min2 updates
- Jul 2, 2026[EU] Elevated latencies and error ratesminor21 min2 updates
June 2026 · 5
- Jun 26, 2026[EU] Elevated ingestion timesminor19 min3 updates
- Jun 16, 2026Elevated API and tracing latency in the US regionminor37 min2 updates
- Jun 10, 2026Ingestion delayminor29 min2 updates
- Jun 8, 2026Database upgrdaeminor—2 updates
- Jun 8, 2026Our media API returns 500 errorsmajor57 min3 updates
Incidents and their updates are Langfuse's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Langfuse.