L
Outage recap · Langfuse

Langfuse outage — August 25, 2026

On August 25, 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.

Latency degradation on legacy ingestion queue

minor
Started
Aug 25, 6:16 AM EDT
Resolved
Aug 25, 9:42 AM EDT
Duration
3h 26m

Langfuse's updates (2)

  1. monitoring · Aug 25, 6:16 AM EDT

    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.

  2. resolved · Aug 25, 9:42 AM EDT

    Issue resolved since 12:30. Legacy ingestion pipeline is fully operational.

What our checks recorded

We checked Langfuse 41 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 203 ms, against 159 ms over the 24 hours before. Langfuse posted the incident at Aug 25, 6:16 AM EDT.

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

Performance degradation on ingestion path

minor
Started
Aug 25, 11:23 AM EDT
Resolved
Aug 25, 12:28 PM EDT
Duration
1h 5m

Langfuse's updates (2)

  1. monitoring · Aug 25, 11:23 AM EDT

    Ingestion delay of up to multiple minutes on the ingestion path. We have scaled up and are investigating the root cause.

  2. resolved · Aug 25, 12:28 PM EDT

    Issue resolved. Latency is back to normal levels.

What our checks recorded

We checked Langfuse 13 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 235 ms, against 160 ms over the 24 hours before. Langfuse posted the incident at Aug 25, 11:23 AM 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.