You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/blog/2025-11-20-incident-report.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ import { BlogHeader } from "@/components/blog/BlogHeader";
15
15
authors={["maxdeichmann"]}
16
16
/>
17
17
18
-
On November 18th, Langfuse Cloud experienced a [multi-hour outage](https://status.langfuse.com/incident/768837) from 11:33am to 2:40pm UTC due to a global [Cloudflare incident](https://blog.cloudflare.com/18-november-2025-outage/). All API and UI traffic was unavailable during this period.
18
+
On November 18th, Langfuse Cloud experienced a [multi-hour outage](https://status.langfuse.com/incidents/01KAGW71ZPD2WTXCFZQBGV7EHH) from 11:33am to 2:40pm UTC due to a global [Cloudflare incident](https://blog.cloudflare.com/18-november-2025-outage/). All API and UI traffic was unavailable during this period.
19
19
20
20
This outage was unacceptable. While the root cause was a third-party infrastructure failure, we take full responsibility for our architecture's single point of failure. This report details what happened, our response, and the concrete steps we're taking to prevent similar incidents.
0 commit comments