L
Outage recap · Langfuse

Langfuse outage — September 13, 2026

On September 13, 2026, Langfuse had a reported incident on Langfuse's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Delayed Ingestion for non v4 SDKs

minor
Started
Sep 13, 10:51 PM EDT
Resolved
Sep 14, 2:10 AM EDT
Duration
3h 19m

Langfuse's updates (4)

  1. investigating · Sep 13, 10:51 PM EDT

    We currently experience an ingestion delay of old SDKs by 3 hours. This is due to performance issues in our batch job which moves data into the v4 data model (<https://langfuse.com/changelog/2026-08-17-langfuse-v4>). We currently work on improving the batch job. All v4 compatible SDKs are not impacted by this. Upgrading SDKs is recommended.

  2. investigating · Sep 13, 11:52 PM EDT

    We considerably increased throughput of the batch job to write data into v4 data model. We are currently catching up processing data.

  3. monitoring · Sep 14, 1:14 AM EDT

    We're making consistent progress in our backlog and are currently seeing delays of about 60 minutes.

  4. resolved · Sep 14, 2:10 AM EDT

    The incident has been resolved.

What our checks recorded

We checked Langfuse 39 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 230 ms, against 204 ms over the 24 hours before. Langfuse posted the incident at Sep 13, 10:51 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.