New Multi-region uptime checks and custom-domain status pages

Langfuse Outage History

Daily provider-status observations and published incident history for Langfuse.

Operational

Langfuse is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Langfuse for future changes.

92% of 50 verified observed days had no reported provider issue

90-Day Trend

Sep 26Nov 15

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
October 2026 90% 30 3

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Daily Status (Last 51 Days)

Sep 26 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

October 2026
Slow trace data retirival across API and UI in EU
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Public API LLM-as-a-judge UI
resolved
should be finally resolved
monitoring
Looks like some timeout are still occurring. Monitoring.
resolved
All replicas look healthy again
identified
Slow clickhouse read replicas affecting performance across the service. Draining and replacing them.
investigating
Slow traces data serving across API and UI
Degraded data serving in EU
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Public API LLM-as-a-judge UI
resolved
Have been stable
monitoring
We should have recovered
identified
Degraded data serving in EU due to unhealthy clickhouse replica. Draining traffic.
Degraded public API performance
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Public API
resolved
Problematic workload was identified and isolated.
investigating
Degraded public API performance in US. Investigating.
September 2026
Degraded ingestion for 20 projects
partial

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Ingestion API
resolved
All projects ingesting as normal
monitoring
Offending workload was isolated, performance should be back to normal for other projects
identified
S3 backpressure leads to S3 "please slow down" errors across projects with cm* prefix
Elevated error rates in In App Agent
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

UI UI UI UI
resolved
The issue has been resolved.
investigating
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
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Ingestion API
resolved
Issue is resolved and OTEL ingestion pipeline is back to regular ingestion speed.
investigating
We're investigating degraded performance in the ingestion flow
Delayed Ingestion for non v4 SDKs
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Ingestion API
resolved
The incident has been resolved.
monitoring
We're making consistent progress in our backlog and are currently seeing delays of about 60 minutes.
investigating
We considerably increased throughput of the batch job to write data into v4 data model. We are currently catching up processing data.
investigating
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
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Ingestion API
resolved
OTEL ingestion latency spike is resolved
investigating
We're investigating degraded performance in the ingestion flow
Degraded OTEL ingestion in US region
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Ingestion API
resolved
Completely back to normal
monitoring
Backlog is almost completely gone. Ingestion delay is < 1 min.
identified
A deployment rollout coincided with a traffic spike, resulting in an unusually large backlog. Adjusting our autoscaling to absorb the backlog faster.
investigating
We are observing OTEL ingestion backlog in US region
August 2026
Performance degradation on ingestion path
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

Ingestion API
resolved
Issue resolved. Latency is back to normal levels.
monitoring
Ingestion delay of up to multiple minutes on the ingestion path. We have scaled up and are investigating the root cause.
Get alerts for Langfuse Subscribe to the provider incident feed Browse all services