502 BAD Gateway errors on UI
minor- Started
- Jul 14, 3:12 PM EDT
- Resolved
- Jul 14, 4:19 PM EDT
- Duration
- 1h 7m
Langfuse's updates (2)
- investigating · Jul 14, 3:12 PM EDT
We experience occasional API errors with 502 Bad Gateway. The team is investigating the root cause currently.
- resolved · Jul 14, 4:19 PM EDT
We resolved the performance bottleneck. All APIs are responding as expected as of now.
What our checks recorded
We checked Langfuse 13 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 159 ms, against 131 ms over the 24 hours before. Langfuse posted the incident at Jul 14, 3:12 PM EDT.
Updates are Langfuse's own words from its status page (status: resolved); we never add an inferred cause.