Langfuse experienced a ~3-hour ingestion delay affecting users on older (non-v4) SDKs, caused by performance issues in the batch job responsible for migrating data into the v4 data model. The team increased batch job throughput to recover the backlog, reducing delays to approximately 60 minutes before full resolution. Users on v4-compatible SDKs were unaffected throughout the incident.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
We're making consistent progress in our backlog and are currently seeing delays of about 60 minutes.
We considerably increased throughput of the batch job to write data into v4 data model. We are currently catching up processing data.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with