outages.live
Live

Langfuse

Langfuse is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

17

Days with an incident

15

Median duration

1 h 12 min

Longest incident

6 h 20 min

Components

20
Ingestion API Operational
90 days agoNo incidentsToday
Prompts API Operational
90 days agoNo incidentsToday
UI Operational
90 days agoNo incidentsToday
Public API Operational
90 days agoNo incidentsToday
LLM-as-a-judge Operational
90 days agoNo incidentsToday
Ingestion API Operational
90 days agoNo incidentsToday
Prompts API Operational
90 days agoNo incidentsToday
UI Operational
90 days agoNo incidentsToday
Public API Operational
90 days agoNo incidentsToday
LLM-as-a-judge Operational
90 days agoNo incidentsToday
Ingestion API Operational
90 days agoNo incidentsToday
Prompts API Operational
90 days agoNo incidentsToday
UI Operational
90 days agoNo incidentsToday
Public API Operational
90 days agoNo incidentsToday
LLM-as-a-judge Operational
90 days agoNo incidentsToday
Ingestion API Operational
90 days agoNo incidentsToday
Prompts API Operational
90 days agoNo incidentsToday
UI Operational
90 days agoNo incidentsToday
Public API Operational
90 days agoNo incidentsToday
LLM-as-a-judge Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 21, 2026

Duration59 min07:46 to 08:45Slow trace data retirival across API and UI in EUDegraded

should be finally resolved

Oct 20, 2026

Duration48 min17:03 to 17:50Degraded performance in Halo (Langfuse Assistant)Notice

Issue with Langfuse Halo (assistant) is fixed.

Duration26 min15:54 to 16:20Degraded data serving in EUDegraded

Have been stable

Oct 19, 2026

Duration45 min10:01 to 10:46Degraded public API performanceDegraded

Problematic workload was identified and isolated.

Sep 30, 2026

Duration6 h 20 min09:10 to 15:30Degraded ingestion for 20 projectsPartial outage

All projects ingesting as normal

Sep 23, 2026

Duration7 min13:36 to 13:43Elevated error rates in In App AgentDegraded

The issue has been resolved.

Sep 16, 2026

Duration1 h 12 min20:20 to 21:31OTEL ingestion queue delay over 10 minutes in USDegraded

Issue is resolved and OTEL ingestion pipeline is back to regular ingestion speed.

Sep 14, 2026

Duration3 h 19 min02:51 to 06:10Delayed Ingestion for non v4 SDKsDegraded

The incident has been resolved.

Sep 8, 2026

Duration1 h 35 min17:26 to 19:00OTEL Ingestion Delay exceeds 10 minutesDegraded

OTEL ingestion latency spike is resolved

Sep 2, 2026

Duration54 min16:02 to 16:56Degraded OTEL ingestion in US regionDegraded

Completely back to normal

Aug 25, 2026

Duration1 h 5 min15:23 to 16:28Performance degradation on ingestion pathDegraded

Issue resolved. Latency is back to normal levels.

Duration3 h 26 min10:16 to 13:42Latency degradation on legacy ingestion queueDegraded

Issue resolved since 12:30. Legacy ingestion pipeline is fully operational.

Aug 20, 2026

Duration1 h 49 min08:06 to 09:55Evaluations are delayed in EUDegraded

All is back to normal

Aug 19, 2026

Duration2 h 34 min12:36 to 15:10Longer v3 -> v4 propagation delayDegraded

Back to normal propagation delay

Follow Langfuse

Your coding agent knows when Langfuse is down, and tells you when a failure is theirs, not yours. You can also get Langfuse incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "langfuse" and tell me if Langfuse has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=langfuse
Slack
/feed subscribe https://outages.cc/feed.xml?providers=langfuse

Go from tracking outages to fixing production issues with Polylane.

Try Polylane