# Is Langfuse down?

> Langfuse is operational. Checked 2026-11-01 23:42 UTC.

- Official status page: https://status.langfuse.com
- Web page: https://outages.cc/langfuse
- JSON: https://outages.cc/api/v1/providers/langfuse
- RSS: https://outages.cc/feed.xml?providers=langfuse

## Active incidents

Langfuse reports no active incident. Status pages can lag the start of a problem by a few minutes.

## Last 90 days

17 incidents on 15 of the last 90 days.

- [Langfuse: Slow trace data retirival across API and UI in EU](https://outages.cc/outages/langfuse-7veimzkw7c.md): Resolved, started 2026-10-21 07:46 UTC, lasted 59 min. should be finally resolved
- [Langfuse: Degraded performance in Halo (Langfuse Assistant)](https://outages.cc/outages/langfuse-2ahbxwbn7we.md): Resolved, started 2026-10-20 17:03 UTC, lasted 48 min. Issue with Langfuse Halo (assistant) is fixed.
- [Langfuse: Degraded data serving in EU](https://outages.cc/outages/langfuse-1jo6dpiuskt.md): Resolved, started 2026-10-20 15:54 UTC, lasted 26 min. Have been stable
- [Langfuse: Degraded public API performance](https://outages.cc/outages/langfuse-1vjrc2mqzdu.md): Resolved, started 2026-10-19 10:01 UTC, lasted 45 min. Problematic workload was identified and isolated.
- [Langfuse: Degraded ingestion for 20 projects](https://outages.cc/outages/langfuse-109ensjvkd2.md): Resolved, started 2026-09-30 09:10 UTC, lasted 6 h 20 min. All projects ingesting as normal
- [Langfuse: Elevated error rates in In App Agent](https://outages.cc/outages/langfuse-9113b7853y.md): Resolved, started 2026-09-23 13:36 UTC, lasted 7 min. The issue has been resolved.
- [Langfuse: OTEL ingestion queue delay over 10 minutes in US](https://outages.cc/outages/langfuse-1uqv2c2vx81.md): Resolved, started 2026-09-16 20:20 UTC, lasted 1 h 12 min. Issue is resolved and OTEL ingestion pipeline is back to regular ingestion speed.
- [Langfuse: Delayed Ingestion for non v4 SDKs](https://outages.cc/outages/langfuse-taacbcm63o.md): Resolved, started 2026-09-14 02:51 UTC, lasted 3 h 19 min. The incident has been resolved.
- [Langfuse: OTEL Ingestion Delay exceeds 10 minutes](https://outages.cc/outages/langfuse-p8385h9fw5.md): Resolved, started 2026-09-08 17:26 UTC, lasted 1 h 35 min. OTEL ingestion latency spike is resolved
- [Langfuse: Degraded OTEL ingestion in US region](https://outages.cc/outages/langfuse-10baipewwn5.md): Resolved, started 2026-09-02 16:02 UTC, lasted 54 min. Completely back to normal
- [Langfuse: Performance degradation on ingestion path](https://outages.cc/outages/langfuse-oriik1058y.md): Resolved, started 2026-08-25 15:23 UTC, lasted 1 h 5 min. Issue resolved. Latency is back to normal levels.
- [Langfuse: Latency degradation on legacy ingestion queue](https://outages.cc/outages/langfuse-2gc0cap65fl.md): Resolved, started 2026-08-25 10:16 UTC, lasted 3 h 26 min. Issue resolved since 12:30. Legacy ingestion pipeline is fully operational.
- [Langfuse: Evaluations are delayed in EU](https://outages.cc/outages/langfuse-1hgo5tl27g7.md): Resolved, started 2026-08-20 08:06 UTC, lasted 1 h 49 min. All is back to normal
- [Langfuse: Longer v3 -> v4 propagation delay](https://outages.cc/outages/langfuse-29ysqow6jhk.md): Resolved, started 2026-08-19 12:36 UTC, lasted 2 h 34 min. Back to normal propagation delay
- [Langfuse: Degraded LLMaJ execution in EU](https://outages.cc/outages/langfuse-14adduxzl1b.md): Resolved, started 2026-08-18 12:06 UTC, lasted 1 h 19 min. Steady throughput for the last 30 minutes. Delay < 5min.
- [Langfuse: prod-us: Delayed ingestion for prod-us](https://outages.cc/outages/langfuse-15p3dbz7yzt.md): Resolved, started 2026-08-15 17:28 UTC, lasted 36 min. We incurred a temporary delay on the legacy ingestion path for v4. This delay has been resolved. OTEL ingestion has not been impacted.
- [Langfuse: Latency increase eval execution up to 40 minutes is resolved](https://outages.cc/outages/langfuse-kh4iz61uyj.md): Resolved, started 2026-08-12 11:56 UTC, lasted 1 h 41 min. The issue is resolved now