What Broke Today

🟢 NPM Jan 19, 2026

⚪ npmjs.com had a brief identity crisis this afternoon but found itself again by evening. The package registry went dark for a few hours—apparently even the left-pad of the internet needs bathroom breaks. All systems are now pretending nothing happened. (Auto-resolved: no updates in 24h)

🟢 SNYK Jan 19, 2026

⚪ Snyk Code took an 8-minute power nap this afternoon, leaving developers refreshing their browsers like slot machines. The incident response team has been stood down, which is corporate speak for 'we're done panic-coding and have moved to denial.'. (Auto-resolved: no updates in 24h)

🟢 SNYK Jan 19, 2026

⚪ resolved - Snyk's recurring tests took an unscheduled nap yesterday and woke up fashionably late today. Engineers confirmed the environment is back to its baseline of "fine, everything's fine" while users enjoyed the thrilling 1-2 hour wait for their security scans to remember what they're supposed to do. (Auto-resolved: no updates in 24h)

🟢 SNYK Jan 19, 2026

⚪ Snyk's container scanner had beef with JAR files and went on a 3-day strike before someone deployed a fix. The service is now back to pretending it never happened, which is definitely how software engineering works. (Auto-resolved: no updates in 24h)

🟢 STYTCH Jan 19, 2026

🟠 Stytch's API decided to play the blame game with Cloudflare during a brief upstream meltdown. Error rates spiked across their test and live APIs like a perfectly timed comedy of finger-pointing, though the situation recovered faster than you can say 'it wasn't us.' Users who relied on Cloudflare got to enjoy the full stack of disappointment. (Auto-resolved: no updates in 24h)

🟢 PLAID Jan 19, 2026

⚪ Chase banking connections went full ghost mode on Plaid, bricking item adds and API calls for everyone downstream. Turns out even financial institutions need their beauty sleep—they just don't tell anyone until the damage is done. (Auto-resolved: no updates in 24h)

🟢 PLAID Jan 19, 2026

⚪ Plaid's instant payment rails took an unscheduled vacation, leaving Instant Payouts and RfP stranded at the digital airport. ACH transfers were still getting booked—just with the processing speed of a notarized letter. The lights are back on now. (Auto-resolved: no updates in 24h)

🟢 SENTRY Jan 19, 2026

⚪ Sentry's UI played dead for a bit when the database decided to become a bottleneck—turns out cramming too much data into one place makes things angry. Engineers applied the ancient remedy of 'turning it off and on again' and now it's pretending nothing happened. (Auto-resolved: no updates in 24h)

🟢 TRELLO Jan 19, 2026

🔴 Trello's task management became task *mismanagement* when 500 errors turned their platform into a digital graveyard for 2+ hours. Users got error pages instead of productivity—ironic, given Trello's job is literally organizing things. Engineering deployed a fix and the patient is stable, but that's a rough morning for anyone whose board depended on actually existing. (Auto-resolved: no updates in 24h)

🟢 CONFLUENCE Jan 19, 2026

⚪ Confluence took an unscheduled nap in us-east-1, leaving some users staring at blank pages and existential dread. The site's back online now, presumably after remembering how to be a wiki. Atlassian's infrastructure briefly auditioned for 'Weekend at Bernie's' and nailed the part. (Auto-resolved: no updates in 24h)

🟢 JIRA Jan 19, 2026

⚪ JIRA's create and view issue features took an unscheduled nap, leaving some customers staring at blank screens. The good news: it woke up, apologized, and promised to behave. The better news: nobody actually uses JIRA willingly anyway, so most didn't notice. (Auto-resolved: no updates in 24h)

🟢 FIGMA Jan 19, 2026

⚪ Figma's Sites and Make feature went dark when Cloudflare decided to take an unscheduled nap—turns out your design tool's reliability depends on someone else's infrastructure. They've now applied the digital equivalent of duct tape and claim everything's breathing normally again, though we're all holding our breath waiting for round two. (Auto-resolved: no updates in 24h)

🟢 FIGMA Jan 19, 2026

⚪ Figma Make spent 11 hours building files that refused to exist. Turns out the 'Make' was taking its name too literally—it was making nothing but errors. Crisis averted, but your patience was the real casualty here. (Auto-resolved: no updates in 24h)

🟢 LINEAR Jan 19, 2026

⚪ resolved - Linear's issue creation went missing for an hour Saturday thanks to some internal maintenance process that apparently skipped quality control. Turns out even the tool for tracking problems can't track its own problems. At least they added guard rails so this particular comedy show won't get a sequel. (Auto-resolved: no updates in 24h)

🟢 DISCORD Jan 19, 2026

⚪ Discord's API and homepage decided to play dead for 8 minutes while an upstream provider had what we'll charitably call 'a moment.' The fix has been deployed and Discord is back to doing whatever Discord does—probably hosting another cryptocurrency scam or something. (Auto-resolved: no updates in 24h)

🟢 DISCORD Jan 19, 2026

⚪ Discord's request handler took an unscheduled nap, turned out to be a classic case of 'have you tried turning it off and on again' - which, miraculously, actually worked this time. (Auto-resolved: no updates in 24h)

🟢 CODECOV Jan 19, 2026

⚪ Codecov's CLI uploader went full hostage situation thanks to Cloudflare's hiccup—turns out relying on someone else's infrastructure for your infrastructure is a bold strategy. Crisis averted after 3.5 hours of watching progress bars that went absolutely nowhere. (Auto-resolved: no updates in 24h)

🟢 BUILDKITE Jan 19, 2026

⚪ Buildkite's job dispatcher developed a sudden appreciation for slowness between 02:30-03:13 UTC—turns out a 'critical query optimization' was actually a critical query pessimization. Someone's feature flag is now permanently flipped to the 'off' position after its wild 43-minute joyride. (Auto-resolved: no updates in 24h)

🟢 BITBUCKET Jan 19, 2026

⚪ Bitbucket went full ghost mode for a hot minute on Jan 7, leaving developers staring at blank screens like their code had filed for divorce. Site's back up now, though someone's definitely getting asked uncomfortable questions in tomorrow's standup. (Auto-resolved: no updates in 24h)

🟢 GITHUB Jan 19, 2026

⚪ GitHub's Issues and Pull Requests decided to ghost both authenticated and unauthenticated users for 100 minutes straight. 10% of requests got the silent treatment at peak, which is apparently what happens when you give a service too much power over developer sanity. The good news: it's resolved now. The bad news: your code review is still pending from 2019. (Auto-resolved: no updates in 24h)

> cat /var/log/failures.log