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.

Building verified history 5 of 24 verified daily observations collected. A percentage will appear after the minimum coverage threshold is met.

90-Day Trend

Sep 26Sep 30

Daily Status (Last 5 Days)

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

Incident History

September 2026
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.
Latency degradation on legacy ingestion queue
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 since 12:30. Legacy ingestion pipeline is fully operational.
monitoring
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
minor

View incident details and source

Notice published:

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

LLM-as-a-judge
resolved
All is back to normal
monitoring
After concurrency adjustments execution delay is back to normal. Monitoring.
investigating
Evaluations are taking longer to execute in EU
Longer v3 -> v4 propagation delay
minor

View incident details and source

Notice published:

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

Ingestion API
resolved
Back to normal propagation delay
monitoring
Latest major SDK versions are not impacted. Find upgrade docs here: https://langfuse.com/docs/observability/sdk/upgrade-path.
monitoring
We have scaled our database infrastructure to match the throughput demand
Degraded LLMaJ execution in EU
minor

View incident details and source

Notice published:

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

LLM-as-a-judge
resolved
Steady throughput for the last 30 minutes. Delay < 5min.
monitoring
our autoscaling responded slower than expected, but responded nonetheless. the backlog is draining
identified
evaluation throughput was overwhelmed by a slow tenant/model workload, with lock-expiry retries multiplying work; the concurrent worker rollout prolonged the incident.
investigating
Eval execution in EU region is taking longer than usual
Get alerts for Langfuse Subscribe to the provider incident feed Browse all services