Is Langfuse down right now?
No, it is up
Operational · All systems operational
Components
- EU (cloud.langfuse.com) · Ingestion APIOperational
- EU (cloud.langfuse.com) · Prompts APIOperational
- EU (cloud.langfuse.com) · UIOperational
- EU (cloud.langfuse.com) · Public APIOperational
- EU (cloud.langfuse.com) · LLM-as-a-judgeOperational
- US (us.cloud.langfuse.com) · Ingestion APIOperational
- US (us.cloud.langfuse.com) · Prompts APIOperational
- US (us.cloud.langfuse.com) · UIOperational
- US (us.cloud.langfuse.com) · Public APIOperational
- US (us.cloud.langfuse.com) · LLM-as-a-judgeOperational
- HIPAA (hipaa.cloud.langfuse.com) · Ingestion APIOperational
- HIPAA (hipaa.cloud.langfuse.com) · Prompts APIOperational
- HIPAA (hipaa.cloud.langfuse.com) · UIOperational
- HIPAA (hipaa.cloud.langfuse.com) · Public APIOperational
- HIPAA (hipaa.cloud.langfuse.com) · LLM-as-a-judgeOperational
- JP (jp.cloud.langfuse.com · Ingestion APIOperational
- JP (jp.cloud.langfuse.com · Prompts APIOperational
- JP (jp.cloud.langfuse.com · UIOperational
- JP (jp.cloud.langfuse.com · Public APIOperational
- JP (jp.cloud.langfuse.com · LLM-as-a-judgeOperational
User reports
Having trouble with Langfuse? Reports are anonymous and only counted, no cookies.
Langfuse uptime, last 90 days
Each bar is one UTC day, coloured by the worst state we saw on the official status page.
Recent Langfuse incidents
Slow trace data retirival across API and UI in EU · 21 Oct 2026, 07:46 UTC · 59 min · minor
resolved · 21 Oct 2026, 09:39 UTC
should be finally resolved
monitoring · 21 Oct 2026, 08:56 UTC
Looks like some timeout are still occurring. Monitoring.
resolved · 21 Oct 2026, 08:45 UTC
All replicas look healthy again
identified · 21 Oct 2026, 08:31 UTC
Slow clickhouse read replicas affecting performance across the service. Draining and replacing them.
investigating · 21 Oct 2026, 07:46 UTC
Slow traces data serving across API and UI
Degraded performance in Halo (Langfuse Assistant) · 20 Oct 2026, 17:03 UTC · 48 min
resolved · 20 Oct 2026, 17:50 UTC
Issue with Langfuse Halo (assistant) is fixed.
identified · 20 Oct 2026, 17:11 UTC
We identified the issue and a fix is currently being deployed.
investigating · 20 Oct 2026, 17:03 UTC
We are seeing increased error rates for requests in Halo (Langfuse assistant)
Degraded data serving in EU · 20 Oct 2026, 15:54 UTC · 26 min · minor
resolved · 20 Oct 2026, 16:20 UTC
Have been stable
monitoring · 20 Oct 2026, 16:01 UTC
We should have recovered
identified · 20 Oct 2026, 15:54 UTC
Degraded data serving in EU due to unhealthy clickhouse replica. Draining traffic.
Degraded public API performance · 19 Oct 2026, 10:01 UTC · 45 min · minor
resolved · 19 Oct 2026, 10:46 UTC
Problematic workload was identified and isolated.
investigating · 19 Oct 2026, 10:01 UTC
Degraded public API performance in US. Investigating.
Degraded ingestion for 20 projects · 30 Sept 2026, 09:10 UTC · 6 h 20 min · major
resolved · 30 Sept 2026, 15:30 UTC
All projects ingesting as normal
monitoring · 30 Sept 2026, 09:43 UTC
Offending workload was isolated, performance should be back to normal for other projects
identified · 30 Sept 2026, 09:10 UTC
S3 backpressure leads to S3 "please slow down" errors across projects with cm* prefix
Elevated error rates in In App Agent · 23 Sept 2026, 13:36 UTC · 7 min · minor
resolved · 23 Sept 2026, 13:43 UTC
The issue has been resolved.
investigating · 23 Sept 2026, 13:36 UTC
We're observing elevated error rates across our In-App agent across multiple regions. Our team is investigating.
OTEL ingestion queue delay over 10 minutes in US · 16 Sept 2026, 20:20 UTC · 1 h 12 min · minor
resolved · 16 Sept 2026, 21:31 UTC
Issue is resolved and OTEL ingestion pipeline is back to regular ingestion speed.
investigating · 16 Sept 2026, 20:20 UTC
We're investigating degraded performance in the ingestion flow
Delayed Ingestion for non v4 SDKs · 14 Sept 2026, 02:51 UTC · 3 h 19 min · minor
resolved · 14 Sept 2026, 06:10 UTC
The incident has been resolved.
monitoring · 14 Sept 2026, 05:14 UTC
We're making consistent progress in our backlog and are currently seeing delays of about 60 minutes.
investigating · 14 Sept 2026, 03:52 UTC
We considerably increased throughput of the batch job to write data into v4 data model. We are currently catching up processing data.
investigating · 14 Sept 2026, 02:51 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 (<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.
OTEL Ingestion Delay exceeds 10 minutes · 8 Sept 2026, 17:26 UTC · 1 h 35 min · minor
resolved · 8 Sept 2026, 19:00 UTC
OTEL ingestion latency spike is resolved
investigating · 8 Sept 2026, 17:26 UTC
We're investigating degraded performance in the ingestion flow
Degraded OTEL ingestion in US region · 2 Sept 2026, 16:02 UTC · 54 min · minor
resolved · 2 Sept 2026, 16:56 UTC
Completely back to normal
monitoring · 2 Sept 2026, 16:49 UTC
Backlog is almost completely gone. Ingestion delay is < 1 min.
identified · 2 Sept 2026, 16:24 UTC
A deployment rollout coincided with a traffic spike, resulting in an unusually large backlog. Adjusting our autoscaling to absorb the backlog faster.
investigating · 2 Sept 2026, 16:02 UTC
We are observing OTEL ingestion backlog in US region
Performance degradation on ingestion path · 25 Aug 2026, 15:23 UTC · 1 h 5 min · minor
resolved · 25 Aug 2026, 16:28 UTC
Issue resolved. Latency is back to normal levels.
monitoring · 25 Aug 2026, 15:23 UTC
Ingestion delay of up to multiple minutes on the ingestion path. We have scaled up and are investigating the root cause.
Latency degradation on legacy ingestion queue · 25 Aug 2026, 10:16 UTC · 3 h 26 min · minor
resolved · 25 Aug 2026, 13:42 UTC
Issue resolved since 12:30. Legacy ingestion pipeline is fully operational.
monitoring · 25 Aug 2026, 10:16 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.
Evaluations are delayed in EU · 20 Aug 2026, 08:06 UTC · 1 h 49 min · minor
resolved · 20 Aug 2026, 09:55 UTC
All is back to normal
monitoring · 20 Aug 2026, 09:40 UTC
After concurrency adjustments execution delay is back to normal. Monitoring.
investigating · 20 Aug 2026, 08:06 UTC
Evaluations are taking longer to execute in EU
Longer v3 -> v4 propagation delay · 19 Aug 2026, 12:36 UTC · 2 h 34 min · minor
resolved · 19 Aug 2026, 15:10 UTC
Back to normal propagation delay
monitoring · 19 Aug 2026, 13:19 UTC
Latest major SDK versions are not impacted. Find upgrade docs [here](https://langfuse.com/docs/observability/sdk/upgrade-path).
monitoring · 19 Aug 2026, 10:30 UTC
We have scaled our database infrastructure to match the throughput demand
Degraded LLMaJ execution in EU · 18 Aug 2026, 12:06 UTC · 1 h 19 min · minor
resolved · 18 Aug 2026, 13:25 UTC
Steady throughput for the last 30 minutes. Delay < 5min.
monitoring · 18 Aug 2026, 12:47 UTC
our autoscaling responded slower than expected, but responded nonetheless. the backlog is draining
identified · 18 Aug 2026, 12:27 UTC
evaluation throughput was overwhelmed by a slow tenant/model workload, with lock-expiry retries multiplying work; the concurrent worker rollout prolonged the incident.
investigating · 18 Aug 2026, 12:06 UTC
Eval execution in EU region is taking longer than usual
Langfuse is listed under Dev tools. Status data comes from the official status page and is checked every 5 minutes.All AI service statuses