Langfuse logo

Is Langfuse Down?

SaaSLive status, outages, and incident history

No. Langfuse is up right now.

Every monitored Langfuse system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment Langfuse breaks

Langfuse is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Langfuse status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Langfuse Component Status

The main Langfuse systems on this page. All 5 are operational right now.

5operational
Ingestion API
Operational
LLM-as-a-judge
Operational
Prompts API
Operational

2 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Public API, UI.

See all of them free

Component statuses may change independently during partial outages.

Recent Langfuse Outages & Incidents

Incident history from the official Langfuse status page, including resolution updates.

Elevated error rates in In App AgentResolved Sep 23, 2026 · 6 minResolved

The issue has been resolved. --- [2026-09-23T13:36:59Z] (investigating) We're observing elevated error rates across our In-App agent across multiple regions. Our team is investigating.

OTEL ingestion queue delay over 10 minutes in USResolved Sep 16, 2026 · 1h 11mResolved

Issue is resolved and OTEL ingestion pipeline is back to regular ingestion speed. --- [2026-09-16T20:20:04Z] (investigating) We're investigating degraded performance in the ingestion flow

Delayed Ingestion for non v4 SDKsResolved Sep 14, 2026 · 3h 18mResolved

The incident has been resolved. --- [2026-09-14T05:14:36Z] (monitoring) We're making consistent progress in our backlog and are currently seeing delays of about 60 minutes. --- [2026-09-14T03:52:08Z] (investigating) We considerably increased throughput of the batch job to write data into v4 data model. We are currently catching up processing data. --- [2026-09-14T02:51:34Z] (investigating) 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.

Langfuse Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Langfuse incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 5 days with incidentsSep 25

Live Langfuse Outage Reports

Problems reported by engineers using Langfuse. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Langfuse problems reported yet.

Something wrong with Langfuse on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Langfuse

Is Langfuse down? Langfuse reports live availability for 20 components at status.langfuse.com, among them Ingestion API, LLM-as-a-judge and Prompts API. Track Langfuse outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Langfuse uptime at 100.00%. Response times, incident history, and SLA tracking for Langfuse are available on the PulsAPI dashboard.

Langfuse Status FAQ

Is Langfuse down right now?

The verdict at the top of this page comes from the latest poll of the official Langfuse status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Langfuse is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Langfuse recovers.

How do I check Langfuse uptime history?

PulsAPI tracks Langfuse uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Langfuse changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Langfuse outages?

PulsAPI reads the official Langfuse status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Langfuse components?

Yes. PulsAPI monitors 5 individual Langfuse components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Langfuse goes down?

Yes. Create a free account and subscribe to Langfuse: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Langfuse to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Langfuse problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Langfuse?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Langfuse plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Langfuse with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services