L
Outage recap · Langfuse

Langfuse outage — October 20, 2026

On October 20, 2026, Langfuse had 2 reported incidents on Langfuse's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Degraded data serving in EU

minor
Started
Oct 20, 11:54 AM EDT
Resolved
Oct 20, 12:20 PM EDT
Duration
26 min

Langfuse's updates (3)

  1. identified · Oct 20, 11:54 AM EDT

    Degraded data serving in EU due to unhealthy clickhouse replica. Draining traffic.

  2. monitoring · Oct 20, 12:01 PM EDT

    We should have recovered

  3. resolved · Oct 20, 12:20 PM EDT

    Have been stable

What our checks recorded

We checked Langfuse 5 times from Langfuse's start time to its resolution, once every five minutes. Every one of them reached Langfuse's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 87 ms, against 149 ms over the 24 hours before. Langfuse posted the incident at Oct 20, 11:54 AM EDT.

Updates are Langfuse's own words from its status page (status: resolved); we never add an inferred cause.

Degraded performance in Halo (Langfuse Assistant)

none
Started
Oct 20, 1:03 PM EDT
Resolved
Oct 20, 1:50 PM EDT
Duration
48 min

Langfuse's updates (3)

  1. investigating · Oct 20, 1:03 PM EDT

    We are seeing increased error rates for requests in Halo (Langfuse assistant)

  2. identified · Oct 20, 1:11 PM EDT

    We identified the issue and a fix is currently being deployed.

  3. resolved · Oct 20, 1:50 PM EDT

    Issue with Langfuse Halo (assistant) is fixed.

What our checks recorded

We checked Langfuse 10 times from Langfuse's start time to its resolution, once every five minutes. Every one of them reached Langfuse's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 107 ms, against 149 ms over the 24 hours before. Langfuse posted the incident at Oct 20, 1:03 PM EDT.

Updates are Langfuse's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Langfuse. This recap summarizes incidents published on Langfuse's official status page.