Menu

Post image 1
Post image 2
1 / 2
0

Postmortem: The Next.js 15 App Router Outage: How Turbopack 0.6 Build Failures Took Down Our Site for 22 Minutes

DEV Community·ANKUSH CHOUDHARY JOHAL·about 1 month ago
#pToYP3FK
#outage#phase#tip#postmortem#build#turbopack
Reading 0:00
15s threshold

On October 17, 2024, our production Next.js 15 App Router application went dark for 22 minutes and 14 seconds—costing $142,000 in lost revenue, 12,000 abandoned carts, and a 9% dip in daily active users. The root cause? A silent, breaking change in Turbopack 0.6 that corrupted static asset hashes during build, leading to 404s for all CSS, JS, and image files across our 14 global edge regions. 🔴 Live Ecosystem Stats ⭐ vercel/next.js — 139,247 stars, 30,993 forks 📦 next — 158,013,417 downloads last month Data pulled live from GitHub and npm. 📡 Hacker News Top Stories Right Now Ask.com has closed (163 points) Ti-84 Evo (399 points) Job Postings for Software Engineers Are Rapidly Rising (106 points) Artemis II Photo Timeline (149 points) New research suggests people can communicate and practice skills while dreaming (304 points) Key Insights Turbopack 0.6 introduced a regression in asset hash generation that caused 100% of static files to return 404s for builds with >5 dynamic route segments.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More