Engineering Log
Engineering insights, product updates, and dependency monitoring best practices.
Why the fast-path for Cloudflare Workers AI model @cf/baai/bge-m3 degrades narrowly and often — and how our community + SDK telemetry surfaces it an average of 7 minutes before the status page acknowledges the drift.
How a tier-2 rate-limit degradation on the OpenAI API propagated through retry storms, connection pools, and shared queue workers — and why our engine saw it 12 minutes before the status page did.
A technical walkthrough of the August 2024 Stripe degradation — what broke for webhook-heavy apps, for background-job payment flows, and for checkout-embedded pages. Drawn from the 14 of our own engine's 6,893 tracked incidents that touched stripe.com.
What actually changes when your team has proper upstream monitoring in place. A short story about the incident that wasn't.
How one DNS provider going down took out authentication, payments, email, and error tracking at the same time. A technical walkthrough of dependency chains.
Official status pages are slow to update, optimistic by design, and often wrong. Here's why crowd-sourced signals catch outages faster.
Every dependency in your lockfile is a bet on someone else's uptime. Here's how to start thinking about your dependency tree as a risk surface.
A realistic walkthrough of how a Stripe outage cascaded through a SaaS checkout flow, and why the first five minutes decide everything.
A practical guide to setting up dependency monitoring: what to watch, what thresholds to set, and how to respond when something goes wrong.
We got tired of finding out about outages from our users. So we built a tool that tells us first.