Skip to content
UpButler
ProductAgentsStatus pagesDocsPricing
Sign inStart free

Is Langfuse down?

Right now

No. Langfuse is operational.

No incidents reported.

Read from status.langfuse.com · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/langfuse/status.agent.json

MCP: upstream_status {"service":"langfuse"}

LLM tracing, prompt management and evals.

What Langfuse reports

Operational

Taken as is from Langfuse's own status page API. Incident titles and component names below are theirs.

Open status.langfuse.com

UpButler's independent probe

There is no keyless endpoint of Langfuse that says anything useful, so UpButler does not probe it. To check your own Langfuse account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Langfuse components

20 operational

  • Ingestion APIOperational
  • Prompts APIOperational
  • UIOperational
  • Public APIOperational
  • LLM-as-a-judgeOperational
  • Ingestion APIOperational
  • Prompts APIOperational
  • UIOperational
  • Public APIOperational
  • LLM-as-a-judgeOperational
  • Ingestion APIOperational
  • Prompts APIOperational
  • UIOperational
  • Public APIOperational
  • LLM-as-a-judgeOperational
  • Ingestion APIOperational
  • Prompts APIOperational
  • UIOperational
  • Public APIOperational
  • LLM-as-a-judgeOperational

Langfuse incidents, last 90 days

1 finished incident seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Langfuse.

Started (UTC)IncidentImpactLasted
Degraded ingestion for 20 projectsmajor6 h 20 min

Tell your outage from Langfuse's

Declare that your project depends on Langfuse. When one of your monitors fails while Langfuse has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start freeHow it works
upbutler.yaml
# upbutler.yaml
dependencies:
  - langfuse
Ask before you retry
curl -s https://upbutler.com/status/langfuse/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "langfuse",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Langfuse down right now?
No. As of 2026-10-10 05:10 UTC, Langfuse is operational. This page reads the status again every 2 minutes.
Where does this status come from?
From Langfuse's own status page API at https://status.langfuse.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Langfuse's words.
How can my agent or app check Langfuse status?
Fetch https://upbutler.com/status/langfuse/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"langfuse"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Langfuse's?
Add "langfuse" to the dependencies of your UpButler workspace. When one of your monitors fails while Langfuse has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in observability and analytics

UpButler is not affiliated with Langfuse. Status and incident text belong to Langfuse and are read from their public status source; the probe result is UpButler's own measurement.