Langfuse incident

Longer v3 -> v4 propagation delay

Resolved after 4 hours 40 minutes, affecting EU (cloud.langfuse.com) (Ingestion API) and US (us.cloud.langfuse.com) (Ingestion API) and 1 more, on August 19, 2026.

resolved Aug 19, 2026, 03:10 PM UTC

Back to normal propagation delay

Started
Aug 19, 2026, 10:30 AM UTC
Resolved
Aug 19, 2026, 03:10 PM UTC
Duration
4h 40m
Detected by Pingoru
Aug 19, 2026, 10:30 AM UTC

Affected components

EU (cloud.langfuse.com) (Ingestion API)US (us.cloud.langfuse.com) (Ingestion API)HIPAA (hipaa.cloud.langfuse.com) (Ingestion API)JP (jp.cloud.langfuse.com (Ingestion API)

Update timeline

  1. monitoring Aug 19, 2026, 10:30 AM UTC

    We have scaled our database infrastructure to match the throughput demand

  2. monitoring Aug 19, 2026, 12:36 PM UTC

    We have scaled our database infrastructure to match the throughput demand

  3. monitoring Aug 19, 2026, 01:19 PM UTC

    Latest major SDK versions are not impacted. Find upgrade docs [here](https://langfuse.com/docs/observability/sdk/upgrade-path).

  4. monitoring Aug 19, 2026, 01:19 PM UTC

    Latest major SDK versions are not impacted. Find upgrade docs here: https://langfuse.com/docs/observability/sdk/upgrade-path.

  5. resolved Aug 19, 2026, 03:10 PM UTC

    Back to normal propagation delay

  6. resolved Aug 19, 2026, 03:10 PM UTC

    Back to normal propagation delay

  7. resolved Aug 19, 2026, 03:10 PM UTC

    Back to normal propagation delay

Your product runs on more than Langfuse

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →