What Broke Today

🟢 SNYK Jun 10, 2026

⚪ Snyk briefly unplugged the email-to-case feature, then plugged it back in and declared victory. The incident response team has stood down, which is either confidence or wishful thinking. Monitoring ensued to make sure it doesn't flake out again. (Auto-resolved: no updates in 24h)

🟢 SENDGRID Jun 10, 2026

🟡 SendGrid's delivery system caught a case of the stutters, bouncing some messages back with 500 errors like a rookie bouncer. The good news? You can still send emails into the void; they're just taking the scenic route. Engineers are pretending to investigate while your customers refresh their inboxes. (Auto-resolved: no updates in 24h)

🟢 GCP Jun 10, 2026

🔴 Delhi, Chennai, and Mumbai users watching their packets take the scenic route to GCP. A third-party data center decided to go full arson mode, forcing an emergency power shutdown. Latency spike incoming—your 10ms response time just became a 10-second existential crisis. (Auto-resolved: no updates in 24h)

🟢 CLERK Jun 09, 2026

🟡 Clerk's analytics endpoints are timing out while contemplating all the errors they're supposed to track. Dashboard charts are just loading spinners now. Investigation underway, which is corporate-speak for 'someone just noticed.'. (Auto-resolved: no updates in 24h)

🟢 LINEAR Jun 09, 2026

🟠 Linear's having an identity crisis across both regions—web, desktop, API, integrations all decided to move at geological timescales. Engineers are 'investigating,' which in incident-speak means refreshing Slack every 3 seconds while stress-eating. (Auto-resolved: no updates in 24h)

🟢 FLY Jun 09, 2026

🔴 Managed Postgres control plane decided the IAD region needed a surprise reboot party. Some clusters are currently experiencing what engineers call 'temporary permanence.' Fly's working on convincing them to come back online. (Auto-resolved: no updates in 24h)

🟢 SNYK Jun 09, 2026

⚪ Snyk's vulnerability scanner discovered its own vulnerability and fixed it within 2 hours. The incident response team has officially clocked out, confident they won't get paged again in 15 minutes. (Auto-resolved: no updates in 24h)

🟢 CONTENTFUL Jun 09, 2026

🟠 Optimization tab ghosted Personalization and Analytics customers mid-shift. The irony of an 'Optimization' feature being completely unavailable isn't lost on anyone with a sense of humor or a deadline. (Auto-resolved: no updates in 24h)

🟢 GITHUB Jun 08, 2026

🟠 GitHub decided unauthenticated users don't deserve to see pull requests or issues—peak gatekeeper energy. Investigation ongoing, which is corporate-speak for 'our on-call engineer just woke up.' At least the sign-in button still works, so there's that. (Auto-resolved: no updates in 24h)

⚪ WEBFLOW Jun 05, 2026

⚪ Webflow played keep-away with their own services for 35 minutes, then remembered they had a job to do. Engineering team managed to find the off/on switch without calling IT support.

🟢 GITHUB Jun 05, 2026

🟠 GitHub decided 1-2% of API requests weren't worth authenticating between 14:49-16:45 UTC. Your Slack/Teams integrations got ghosted. Endpoints played 'who are you?' with legitimate users, serving 4xx errors like denial of service with a smile. (Auto-resolved: no updates in 24h)

🟢 OPENAI Jun 05, 2026

🟠 OpenAI's Microsoft login theater is experiencing a partial outage—turns out even OAuth has trust issues. Engineers applied a bandage and are now watching to see if it sticks, which is basically tech's version of 'it's complicated.' Your Microsoft credentials have filed for separation. (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)

🟢 SNYK Jun 04, 2026

⚪ Snyk's daily test queue got backed up like a airport bathroom after the beverage service. They kicked it loose and everything's limping along normally again. Incident response team is clocking out. (Auto-resolved: no updates in 24h)

🟢 ELASTIC Jun 04, 2026

🟡 Elastic decided Azure serverless needed more 'server' and less 'less' — project creation now moves at geological timescales while existing deployments ghost their users. Engineers are investigating why their infrastructure apparently needs a coffee break. (Auto-resolved: no updates in 24h)

🟢 HONEYCOMB Jun 03, 2026

🟠 Canvas agents forgot how to paint with Honeycomb's internal tools. Like giving an artist brushes made of smoke. Devs stuck staring at blank canvases wondering if their observability just became art installation. (Auto-resolved: no updates in 24h)

🟢 REPLICATE Jun 03, 2026

🟡 Your L40S and H200 clusters are playing hot potato with model setup times. High contention means everyone's waiting in line while the hardware pretends to be busy. Engineers are investigating why expensive silicon doesn't want to cooperate. (Auto-resolved: no updates in 24h)

🟢 SHOPIFY Jun 03, 2026

⚪ Shopify's checkout decided to take an unscheduled vacation, leaving merchants staring at loading spinners like they were hypnotic art installations. The Great Sales Interruption has been resolved, and capitalism can resume its regularly scheduled programming. (Auto-resolved: no updates in 24h)

🟢 LINEAR Jun 03, 2026

🟠 Linear Agent's code intelligence tools went full Inception—trying to run code analysis but the upstream provider decided to take a unscheduled nap. Both US and EU regions are experiencing the cascading joy of depending on third-party infrastructure that apparently skipped the redundancy memo. (Auto-resolved: no updates in 24h)

🟢 FIVETRAN Jun 03, 2026

🔴 Fivetran's Shopify integration joined the broken API club after Shopify's own endpoints decided 404s were this week's personality. Your data pipeline is now a data paperweight until someone fixes upstream. (Auto-resolved: no updates in 24h)

> cat /var/log/failures.log