← Back to the carnage
UPSTASH

⚪ QStash's HTTP parser briefly forgot how to read the internet. Resolved faster than you can say 'DNS cache go brr.' If ghosts return, try clearing your DNS—turns out that's tech support's duct tape. 👻. (Auto-resolved: no updates in 24h)

⏰ Jul 16, 2026 Fixed (for now) spotted via status_rss

// The official story

QStash us-east-1 - URL Publish Errors

// Status page says

Jul 16 , 06:30 UTC Resolved - Partial outage due to http parsing errors. Problem was resolved couple minutes later. If problem continues, refreshing the DNS cache is recommended.

🔗 Official status page (for the PR-approved version)

https://status.upstash.com/incidents/d9xmrx1kx7wp

Upstash's Greatest Hits

🟢 UPSTASH Jun 25, 2026
🟡 Upstash Redis decided to take an unscheduled nap across eu-central-1, us-east-1, and us-west-1. Engineers are currently asking their Redis instances why they're playing dead. More news when someone figures out what happened. (Auto-resolved: no updates in 24h)
🟢 UPSTASH Jun 23, 2026
🟠 Someone flipped the wrong switch and made Upstash boxes into read-only ghosts for 3 hours. Your containers kept chugging along like nothing happened, but you couldn't touch them. The irony of 'serverless' infrastructure needing to be rebooted is apparently still funny. (Auto-resolved: no updates in 24h)
🟢 UPSTASH Jun 19, 2026
⚪ QStash EU region went full hermit mode for 34 minutes—some requests got ghosted during the networking blackout. They've since remembered that connectivity exists and are back to normal service. Postmortem TBA, presumably titled 'How We Lost Our Internet Privileges.'. (Auto-resolved: no updates in 24h)
🟢 UPSTASH Jun 04, 2026
🟡 Upstash Vector in IAD region decided to ghost users while Fly.io's networking team frantically checks if they unplugged the right cable. Connectivity's gone full Schrödinger's—both working and not working simultaneously. Thrilling times. (Auto-resolved: no updates in 24h)