🔴 Vercel's dxb1 region decided to go offline, forcing your traffic into the Mumbai region like an overbooked flight. New deployments to Dubai are now accepting applications in the spring. Your ops team is definitely not fine. (Auto-resolved: no updates in 24h)

🟡 Vercel hit a snag where the Dashboard can't query runtime logs—classic case of selective amnesia. Build logs and ingestion still working, so at least they didn't burn the whole house down. Engineers are currently arguing with their own infrastructure. (Auto-resolved: no updates in 24h)

🟡 Vercel's community forums decided to ghost everyone mid-conversation. They're "investigating" which is tech-speak for "we have no idea when this ends." Discord servers about to explode with angry devs asking why their deploy buttons work but their discourse doesn't. (Auto-resolved: no updates in 24h)

⚪ 🔧 Vercel's Functions threw ERR_STREAM_PREMATURE_CLOSE errors after a Node.js security patch introduced a regression that murdered response streaming. node-fetch@2 users got the short end of the stick for ~7 hours while engineers played upstream whack-a-mole. (Auto-resolved: no updates in 24h)

⚪ Vercel's dashboard, API, and CLI all developed selective amnesia simultaneously. The backlog recovery is in progress, moving at the speed of a very determined sloth. Should be back to normal-ish in a couple hours, assuming the backfill doesn't decide to ghost them again. (Auto-resolved: no updates in 24h)