Latency degradation on legacy ingestion queue
minor- Started
- Aug 25, 6:16 AM EDT
- Resolved
- Aug 25, 9:42 AM EDT
- Duration
- 3h 26m
Langfuse's updates (2)
- monitoring · Aug 25, 6:16 AM EDT
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.
- resolved · Aug 25, 9:42 AM EDT
Issue resolved since 12:30. Legacy ingestion pipeline is fully operational.
What our checks recorded
We checked Langfuse 41 times from Langfuse's start time to its resolution, once every five minutes. Every one of them reached Langfuse's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 203 ms, against 159 ms over the 24 hours before. Langfuse posted the incident at Aug 25, 6:16 AM EDT.
Updates are Langfuse's own words from its status page (status: resolved); we never add an inferred cause.