Langfuse Outage History

Langfuse is up right now

Langfuse had 26 outages in the last 2 years totaling 33h 25m of downtime, averaging 1.1 incidents per month.

There were 26 Langfuse outages since June 2, 2026 totaling 33h 25m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.langfuse.com

Minor October 21, 2026

Slow trace data retirival across API and UI in EU

Detected by Pingoru
Oct 21, 2026, 07:46 AM UTC
Resolved
Oct 21, 2026, 08:45 AM UTC
Duration
58m
Timeline · 5 updates
  1. investigating Oct 21, 2026, 07:46 AM UTC

    Slow traces data serving across API and UI

  2. identified Oct 21, 2026, 08:31 AM UTC

    Slow clickhouse read replicas affecting performance across the service. Draining and replacing them.

  3. resolved Oct 21, 2026, 08:45 AM UTC

    All replicas look healthy again

  4. monitoring Oct 21, 2026, 08:56 AM UTC

    Looks like some timeout are still occurring. Monitoring.

  5. resolved Oct 21, 2026, 09:39 AM UTC

    should be finally resolved

Read the full incident report →

Notice October 20, 2026

Degraded performance in Halo (Langfuse Assistant)

Detected by Pingoru
Oct 20, 2026, 05:03 PM UTC
Resolved
Oct 20, 2026, 05:50 PM UTC
Duration
47m
Timeline · 3 updates
  1. investigating Oct 20, 2026, 05:03 PM UTC

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

  2. identified Oct 20, 2026, 05:11 PM UTC

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

  3. resolved Oct 20, 2026, 05:50 PM UTC

    Issue with Langfuse Halo (assistant) is fixed.

Read the full incident report →

Minor October 20, 2026

Degraded data serving in EU

Detected by Pingoru
Oct 20, 2026, 03:54 PM UTC
Resolved
Oct 20, 2026, 04:20 PM UTC
Duration
25m
Timeline · 3 updates
  1. identified Oct 20, 2026, 03:54 PM UTC

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

  2. monitoring Oct 20, 2026, 04:01 PM UTC

    We should have recovered

  3. resolved Oct 20, 2026, 06:56 PM UTC

    Have been stable

Read the full incident report →

Minor October 19, 2026

Degraded public API performance

Detected by Pingoru
Oct 19, 2026, 10:01 AM UTC
Resolved
Oct 19, 2026, 10:46 AM UTC
Duration
44m
Timeline · 2 updates
  1. investigating Oct 19, 2026, 10:01 AM UTC

    Degraded public API performance in US. Investigating.

  2. resolved Oct 19, 2026, 10:46 AM UTC

    Problematic workload was identified and isolated.

Read the full incident report →

Major September 30, 2026

Degraded ingestion for 20 projects

Detected by Pingoru
Sep 30, 2026, 09:10 AM UTC
Resolved
Sep 30, 2026, 03:30 PM UTC
Duration
6h 20m
Timeline · 3 updates
  1. identified Sep 30, 2026, 09:10 AM UTC

    S3 backpressure leads to S3 "please slow down" errors across projects with cm* prefix

  2. monitoring Sep 30, 2026, 09:43 AM UTC

    Offending workload was isolated, performance should be back to normal for other projects

  3. resolved Sep 30, 2026, 03:30 PM UTC

    All projects ingesting as normal

Read the full incident report →

Minor September 23, 2026

Elevated error rates in In App Agent

Detected by Pingoru
Sep 23, 2026, 01:36 PM UTC
Resolved
Sep 23, 2026, 01:43 PM UTC
Duration
6m
Timeline · 2 updates
  1. investigating Sep 23, 2026, 01:36 PM UTC

    We're observing elevated error rates across our In-App agent across multiple regions. Our team is investigating.

  2. resolved Sep 23, 2026, 01:43 PM UTC

    The issue has been resolved.

Read the full incident report →

Minor September 16, 2026

OTEL ingestion queue delay over 10 minutes in US

Detected by Pingoru
Sep 16, 2026, 08:20 PM UTC
Resolved
Sep 16, 2026, 09:31 PM UTC
Duration
1h 11m
Timeline · 2 updates
  1. investigating Sep 16, 2026, 08:20 PM UTC

    We're investigating degraded performance in the ingestion flow

  2. resolved Sep 16, 2026, 09:31 PM UTC

    Issue is resolved and OTEL ingestion pipeline is back to regular ingestion speed.

Read the full incident report →

Minor September 14, 2026

Delayed Ingestion for non v4 SDKs

Detected by Pingoru
Sep 14, 2026, 02:51 AM UTC
Resolved
Sep 14, 2026, 06:10 AM UTC
Duration
3h 18m
Timeline · 4 updates
  1. investigating Sep 14, 2026, 02:51 AM UTC

    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 (). We currently work on improving the batch job. All v4 compatible SDKs are not impacted by this. Upgrading SDKs is recommended.

  2. investigating Sep 14, 2026, 03:52 AM UTC

    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, 2026, 05:14 AM UTC

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

  4. resolved Sep 14, 2026, 06:10 AM UTC

    The incident has been resolved.

Read the full incident report →

Minor September 8, 2026

OTEL Ingestion Delay exceeds 10 minutes

Detected by Pingoru
Sep 08, 2026, 05:26 PM UTC
Resolved
Sep 08, 2026, 07:00 PM UTC
Duration
1h 34m
Timeline · 2 updates
  1. investigating Sep 08, 2026, 05:26 PM UTC

    We're investigating degraded performance in the ingestion flow

  2. resolved Sep 08, 2026, 07:00 PM UTC

    OTEL ingestion latency spike is resolved

Read the full incident report →

Minor September 2, 2026

Degraded OTEL ingestion in US region

Detected by Pingoru
Sep 02, 2026, 04:02 PM UTC
Resolved
Sep 02, 2026, 04:56 PM UTC
Duration
53m
Timeline · 4 updates
  1. investigating Sep 02, 2026, 04:02 PM UTC

    We are observing OTEL ingestion backlog in US region

  2. identified Sep 02, 2026, 04:24 PM UTC

    A deployment rollout coincided with a traffic spike, resulting in an unusually large backlog. Adjusting our autoscaling to absorb the backlog faster.

  3. monitoring Sep 02, 2026, 04:49 PM UTC

    Backlog is almost completely gone. Ingestion delay is < 1 min.

  4. resolved Sep 02, 2026, 04:56 PM UTC

    Completely back to normal

Read the full incident report →

Minor August 25, 2026

Performance degradation on ingestion path

Detected by Pingoru
Aug 25, 2026, 03:23 PM UTC
Resolved
Aug 25, 2026, 04:28 PM UTC
Duration
1h 4m
Timeline · 2 updates
  1. monitoring Aug 25, 2026, 03:23 PM UTC

    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, 2026, 04:28 PM UTC

    Issue resolved. Latency is back to normal levels.

Read the full incident report →

Minor August 25, 2026

Latency degradation on legacy ingestion queue

Detected by Pingoru
Aug 25, 2026, 10:16 AM UTC
Resolved
Aug 25, 2026, 01:42 PM UTC
Duration
3h 26m
Timeline · 2 updates
  1. monitoring Aug 25, 2026, 10:16 AM UTC

    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, 2026, 01:42 PM UTC

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

Read the full incident report →

Minor August 20, 2026

Evaluations are delayed in EU

Detected by Pingoru
Aug 20, 2026, 08:06 AM UTC
Resolved
Aug 20, 2026, 09:55 AM UTC
Duration
1h 49m
Timeline · 3 updates
  1. investigating Aug 20, 2026, 08:06 AM UTC

    Evaluations are taking longer to execute in EU

  2. monitoring Aug 20, 2026, 09:40 AM UTC

    After concurrency adjustments execution delay is back to normal. Monitoring.

  3. resolved Aug 20, 2026, 09:55 AM UTC

    All is back to normal

Read the full incident report →

Minor August 19, 2026

Longer v3 -> v4 propagation delay

Detected by Pingoru
Aug 19, 2026, 12:36 PM UTC
Resolved
Aug 19, 2026, 03:10 PM UTC
Duration
2h 33m
Timeline · 3 updates
  1. monitoring Aug 19, 2026, 12:36 PM UTC

    We have scaled our database infrastructure to match the throughput demand

  2. monitoring Aug 19, 2026, 01:19 PM UTC

    Latest major SDK versions are not impacted. Find upgrade docs [here](https://langfuse.com/docs/observability/sdk/upgrade-path).

  3. resolved Aug 19, 2026, 03:10 PM UTC

    Back to normal propagation delay

Read the full incident report →

Minor August 18, 2026

Degraded LLMaJ execution in EU

Detected by Pingoru
Aug 18, 2026, 12:06 PM UTC
Resolved
Aug 18, 2026, 01:25 PM UTC
Duration
1h 18m
Timeline · 4 updates
  1. investigating Aug 18, 2026, 12:06 PM UTC

    Eval execution in EU region is taking longer than usual

  2. identified Aug 18, 2026, 12:27 PM UTC

    evaluation throughput was overwhelmed by a slow tenant/model workload, with lock-expiry retries multiplying work; the concurrent worker rollout prolonged the incident.

  3. monitoring Aug 18, 2026, 12:47 PM UTC

    our autoscaling responded slower than expected, but responded nonetheless. the backlog is draining

  4. resolved Aug 18, 2026, 01:25 PM UTC

    Steady throughput for the last 30 minutes. Delay < 5min.

Read the full incident report →

Minor August 15, 2026

prod-us: Delayed ingestion for prod-us

Detected by Pingoru
Aug 15, 2026, 05:28 PM UTC
Resolved
Aug 15, 2026, 06:05 PM UTC
Duration
36m
Timeline · 2 updates
  1. investigating Aug 15, 2026, 05:28 PM UTC

    Currently the ingestion for the events table is delayed in the US environment. This happens only for data from non-latest major SDK versions. We are investigating this and have started a mitigation. The data should be up to date soon.

  2. resolved Aug 15, 2026, 06:05 PM UTC

    We incurred a temporary delay on the legacy ingestion path for v4. This delay has been resolved. OTEL ingestion has not been impacted.

Read the full incident report →

Minor August 12, 2026

Latency increase eval execution up to 40 minutes is resolved

Detected by Pingoru
Aug 12, 2026, 11:56 AM UTC
Resolved
Aug 12, 2026, 01:37 PM UTC
Duration
1h 40m
Timeline · 3 updates
  1. monitoring Aug 12, 2026, 11:56 AM UTC

    We are seeing an increase in the eval execution. We have scaled up our infrastructure and are monitoring.

  2. monitoring Aug 12, 2026, 12:39 PM UTC

    Previous latency increase of the eval execution is resolved. Slight delays may still occur.

  3. resolved Aug 12, 2026, 01:37 PM UTC

    The issue is resolved now

Read the full incident report →

Minor August 3, 2026

[US] Ingestion Delays

Detected by Pingoru
Aug 03, 2026, 06:25 PM UTC
Resolved
Aug 03, 2026, 07:03 PM UTC
Duration
38m
Timeline · 3 updates
  1. investigating Aug 03, 2026, 06:25 PM UTC

    We're currently observing about 10min ingestion delays. Our team is investigating.

  2. investigating Aug 03, 2026, 06:56 PM UTC

    We see an improvement and the current delay is below 5min. We continue to investigate and scale.

  3. resolved Aug 03, 2026, 07:03 PM UTC

    This issue is resolved and we're back to regular processing times.

Read the full incident report →

Minor July 14, 2026

502 BAD Gateway errors on UI

Detected by Pingoru
Jul 14, 2026, 07:12 PM UTC
Resolved
Jul 14, 2026, 08:19 PM UTC
Duration
1h 6m
Timeline · 2 updates
  1. investigating Jul 14, 2026, 07:12 PM UTC

    We experience occasional API errors with 502 Bad Gateway. The team is investigating the root cause currently.

  2. resolved Jul 14, 2026, 08:19 PM UTC

    We resolved the performance bottleneck. All APIs are responding as expected as of now.

Read the full incident report →

Minor July 2, 2026

[EU] Elevated latencies and error rates

Detected by Pingoru
Jul 02, 2026, 07:43 AM UTC
Resolved
Jul 02, 2026, 08:03 AM UTC
Duration
20m
Timeline · 2 updates
  1. investigating Jul 02, 2026, 07:43 AM UTC

    We're observing elevated latencies and error rates across read APIs and some frontend routes. Ingestion is not affected.

  2. resolved Jul 02, 2026, 08:03 AM UTC

    The issue has been resolved.

Read the full incident report →

Minor June 26, 2026

[EU] Elevated ingestion times

Detected by Pingoru
Jun 26, 2026, 09:32 AM UTC
Resolved
Jun 26, 2026, 09:51 AM UTC
Duration
18m
Timeline · 3 updates
  1. investigating Jun 26, 2026, 09:32 AM UTC

    We're currently experiencing elevated ingestion times in the EU environment. Some events are processed with a delay of about 15 minutes. Our team is investigating.

  2. monitoring Jun 26, 2026, 09:43 AM UTC

    We found a patch and currently work through the backlog. Things should recover within the next 10min.

  3. resolved Jun 26, 2026, 09:51 AM UTC

    The incident has been resolved.

Read the full incident report →

Minor June 16, 2026

Elevated API and tracing latency in the US region

Detected by Pingoru
Jun 16, 2026, 05:36 PM UTC
Resolved
Jun 16, 2026, 06:12 PM UTC
Duration
36m
Timeline · 2 updates
  1. monitoring Jun 16, 2026, 05:36 PM UTC

    A hiccup during a planned database maintenance. Identified and resolved. Presently monitoring.

  2. resolved Jun 16, 2026, 06:12 PM UTC

    All latencies are back to normal

Read the full incident report →

Minor June 10, 2026

Ingestion delay

Detected by Pingoru
Jun 10, 2026, 02:47 PM UTC
Resolved
Jun 10, 2026, 03:16 PM UTC
Duration
28m
Timeline · 2 updates
  1. investigating Jun 10, 2026, 02:47 PM UTC

    We currently have a bottleneck in our ingestion pipeline which causes a delay of ingested data of 12 minutes. We currently work to scale the pipeline.

  2. resolved Jun 10, 2026, 03:16 PM UTC

    We scaled our ingestion and are processing data in time.

Read the full incident report →

Minor June 8, 2026

Database upgrdae

Detected by Pingoru
Jun 08, 2026, 08:55 PM UTC
Resolved
Jun 08, 2026, 09:00 PM UTC
Duration
5m
Timeline · 2 updates
  1. investigating Jun 08, 2026, 08:55 PM UTC

    We just executed a database upgrade which caused a downtime of 5 minutes.

  2. resolved Jun 08, 2026, 08:55 PM UTC

    Upgrade successfully resolved.

Read the full incident report →

Major June 8, 2026

Our media API returns 500 errors

Detected by Pingoru
Jun 08, 2026, 06:57 PM UTC
Resolved
Jun 08, 2026, 07:55 PM UTC
Duration
57m
Timeline · 3 updates
  1. investigating Jun 08, 2026, 06:57 PM UTC

    We observe that our api/public/media endpoint currently returns 500 status errors as our underlying database has performance issues.

  2. investigating Jun 08, 2026, 07:54 PM UTC

    We scaled our underlying infrastructure and are processing media uploads without errors.

  3. resolved Jun 10, 2026, 02:45 PM UTC

    We scaled our infrastructure and are processing media uploads without errors.

Read the full incident report →