Cloudflare proxy failure causes complete API and UI unavailability

critical

availabilityUpdated Nov 20, 2025(via Exa)

Sources

Incident Report for Nov 18, 2025 - Langfuse Bloglangfuse.com

Technologies:

Langfusesubject

CloudflareThe root cause of this issue originates in Cloudflare

How to detect:

When Cloudflare proxy experiences an outage, all API and UI traffic to Langfuse fails with 500 error codes. All ingestion and prompt management endpoints become completely unavailable as traffic cannot reach AWS infrastructure.

Recommended action:

Implement infrastructure diversification: migrate DNS management away from Cloudflare, assess alternative WAF and proxy solutions, establish multi-provider routing to eliminate single point of failure. During active incident, consider publishing DNS-based bypasses directly to AWS ALBs if Cloudflare dashboard is accessible.