<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/">
    <channel>
        <title>What Broke Today</title>
        <link>https://whatbroke.today</link>
        <description>Know when things break, before your boss asks.</description>
        <atom:link href="https://whatbroke.today/feed.xml" rel="self" type="application/rss+xml"/>
        
        <item>
            <title>GITHUB: Incident with Git Operations, Issues, Actions and Pull Requests</title>
            <link>https://whatbroke.today/incident/github-incident-with-git-operations-issues-actions-2026-10-07</link>
            <description><![CDATA[🟠 GitHub decided to ghost developers twice in one day—Git ops, Issues, Actions, and PRs all took an unscheduled siesta from 16:52-17:01 UTC. Systems are back online, but the incident playlist is starting to feel like a broken record.]]></description>
            <pubDate>2026-10-07 17:31:20</pubDate>
            <guid>https://whatbroke.today/incident/github-incident-with-git-operations-issues-actions-2026-10-07</guid>
            <enclosure url="https://whatbroke.today/api/og/github-incident-with-git-operations-issues-actions-2026-10-07.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/github-incident-with-git-operations-issues-actions-2026-10-07.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/github-incident-with-git-operations-issues-actions-2026-10-07.png" width="1200" height="630"/>
        </item>
        <item>
            <title>LOVABLE: Some users may see errors sending messages</title>
            <link>https://whatbroke.today/incident/lovable-some-users-may-see-errors-sending-2026-10-07</link>
            <description><![CDATA[🟡 Lovable's editor decided messages are optional now. Users report errors when trying to send anything—turns out the platform's commitment to communication was mostly aspirational. Engineers are speedrunning a fix before the irony becomes weaponized.]]></description>
            <pubDate>2026-10-07 14:15:59</pubDate>
            <guid>https://whatbroke.today/incident/lovable-some-users-may-see-errors-sending-2026-10-07</guid>
            <enclosure url="https://whatbroke.today/api/og/lovable-some-users-may-see-errors-sending-2026-10-07.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/lovable-some-users-may-see-errors-sending-2026-10-07.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/lovable-some-users-may-see-errors-sending-2026-10-07.png" width="1200" height="630"/>
        </item>
        <item>
            <title>OPENAI: Unable to create new ChatGPT Work threads in latest version of desktop app</title>
            <link>https://whatbroke.today/incident/openai-unable-to-create-new-chatgpt-work-2026-10-07</link>
            <description><![CDATA[🟡 OpenAI's desktop app decided Work threads are overrated. Users now experiencing the cutting-edge feature of threads that simply don't exist. Engineering team is 'investigating' what surely won't take 6 hours to fix.]]></description>
            <pubDate>2026-10-07 05:45:56</pubDate>
            <guid>https://whatbroke.today/incident/openai-unable-to-create-new-chatgpt-work-2026-10-07</guid>
            <enclosure url="https://whatbroke.today/api/og/openai-unable-to-create-new-chatgpt-work-2026-10-07.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/openai-unable-to-create-new-chatgpt-work-2026-10-07.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/openai-unable-to-create-new-chatgpt-work-2026-10-07.png" width="1200" height="630"/>
        </item>
        <item>
            <title>OPENAI: new thread failed on the latest desktop app version for personal accounts</title>
            <link>https://whatbroke.today/incident/openai-new-thread-failed-on-the-latest-2026-10-07</link>
            <description><![CDATA[🟡 OpenAI's desktop app decided threads were too mainstream, now refusing to create them for regular users. Codex is having commitment issues. Engineers are investigating whether this was a feature or a bug—spoiler: it's a bug.]]></description>
            <pubDate>2026-10-07 05:40:58</pubDate>
            <guid>https://whatbroke.today/incident/openai-new-thread-failed-on-the-latest-2026-10-07</guid>
            <enclosure url="https://whatbroke.today/api/og/openai-new-thread-failed-on-the-latest-2026-10-07.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/openai-new-thread-failed-on-the-latest-2026-10-07.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/openai-new-thread-failed-on-the-latest-2026-10-07.png" width="1200" height="630"/>
        </item>
        <item>
            <title>KRAKEN: Krak Card API outage (EEA/UK)</title>
            <link>https://whatbroke.today/incident/kraken-krak-card-api-outage-eeauk-2026-10-07</link>
            <description><![CDATA[🟡 Krak Card API decided to ghost European and UK users right when they needed it most. Transactions and orders are failing faster than crypto during a bear market. Engineers are frantically checking if they paid the API's electricity bill.]]></description>
            <pubDate>2026-10-07 04:26:02</pubDate>
            <guid>https://whatbroke.today/incident/kraken-krak-card-api-outage-eeauk-2026-10-07</guid>
            <enclosure url="https://whatbroke.today/api/og/kraken-krak-card-api-outage-eeauk-2026-10-07.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/kraken-krak-card-api-outage-eeauk-2026-10-07.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/kraken-krak-card-api-outage-eeauk-2026-10-07.png" width="1200" height="630"/>
        </item>
        <item>
            <title>SNYK: Snyk CLI SCA Scans Degraded due to Enrichment of Test Failure</title>
            <link>https://whatbroke.today/incident/snyk-snyk-cli-sca-scans-degraded-due-2026-10-07</link>
            <description><![CDATA[⚪ Snyk's dependency scanner got too ambitious analyzing test failures and face-planted hard. Engineers threw it in recovery mode, got it back on its feet, and confirmed the patient is breathing normally again. Crisis averted—for now.]]></description>
            <pubDate>2026-10-07 00:00:53</pubDate>
            <guid>https://whatbroke.today/incident/snyk-snyk-cli-sca-scans-degraded-due-2026-10-07</guid>
            <enclosure url="https://whatbroke.today/api/og/snyk-snyk-cli-sca-scans-degraded-due-2026-10-07.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/snyk-snyk-cli-sca-scans-degraded-due-2026-10-07.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/snyk-snyk-cli-sca-scans-degraded-due-2026-10-07.png" width="1200" height="630"/>
        </item>
        <item>
            <title>SENTRY: Sentry dashboard down</title>
            <link>https://whatbroke.today/incident/sentry-sentry-dashboard-down-2026-10-06</link>
            <description><![CDATA[🟡 Sentry's dashboard went blind in both US and EU regions. The irony of an error tracking platform becoming untrackable is *chef's kiss*. Engineers are investigating whether they need to file a bug report against themselves. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-06 19:01:08</pubDate>
            <guid>https://whatbroke.today/incident/sentry-sentry-dashboard-down-2026-10-06</guid>
            <enclosure url="https://whatbroke.today/api/og/sentry-sentry-dashboard-down-2026-10-06.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/sentry-sentry-dashboard-down-2026-10-06.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/sentry-sentry-dashboard-down-2026-10-06.png" width="1200" height="630"/>
        </item>
        <item>
            <title>SNYK: Snyk CLI Tests - 504 Gateway Timeouts</title>
            <link>https://whatbroke.today/incident/snyk-snyk-cli-tests-504-gateway-2026-10-06</link>
            <description><![CDATA[🟠 Snyk's vulnerability scanner discovered its own weakness: gateway timeouts turning 504s into a customer experience audit. Engineers found the problem and are speed-running fixes while tests crawl at 45-second intervals—proof that even security tools need security blankets. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-06 16:16:02</pubDate>
            <guid>https://whatbroke.today/incident/snyk-snyk-cli-tests-504-gateway-2026-10-06</guid>
            <enclosure url="https://whatbroke.today/api/og/snyk-snyk-cli-tests-504-gateway-2026-10-06.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/snyk-snyk-cli-tests-504-gateway-2026-10-06.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/snyk-snyk-cli-tests-504-gateway-2026-10-06.png" width="1200" height="630"/>
        </item>
        <item>
            <title>ELEVENLABS: EU Agents disruption in SIP calls</title>
            <link>https://whatbroke.today/incident/elevenlabs-eu-agents-disruption-in-sip-calls-2026-10-06</link>
            <description><![CDATA[🟡 ElevenLabs' EU telephony agents decided to ghost SIP calls entirely. Turns out 'voice AI' doesn't work when the voice part breaks. Engineering team is currently using Ouija board to communicate with the infrastructure. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-06 11:30:53</pubDate>
            <guid>https://whatbroke.today/incident/elevenlabs-eu-agents-disruption-in-sip-calls-2026-10-06</guid>
            <enclosure url="https://whatbroke.today/api/og/elevenlabs-eu-agents-disruption-in-sip-calls-2026-10-06.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/elevenlabs-eu-agents-disruption-in-sip-calls-2026-10-06.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/elevenlabs-eu-agents-disruption-in-sip-calls-2026-10-06.png" width="1200" height="630"/>
        </item>
        <item>
            <title>ZAPIER: Logging into Zapier using Facebook or Microsoft SSO shown a blank page after authentication.</title>
            <link>https://whatbroke.today/incident/zapier-logging-into-zapier-using-facebook-or-2026-10-05</link>
            <description><![CDATA[🟡 Zapier's Facebook and Microsoft login buttons led to the void after authentication. Engineers found the culprit and shipped a fix, now playing the waiting game to see if it actually stuck or just created new and exciting problems. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-05 19:45:58</pubDate>
            <guid>https://whatbroke.today/incident/zapier-logging-into-zapier-using-facebook-or-2026-10-05</guid>
            <enclosure url="https://whatbroke.today/api/og/zapier-logging-into-zapier-using-facebook-or-2026-10-05.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/zapier-logging-into-zapier-using-facebook-or-2026-10-05.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/zapier-logging-into-zapier-using-facebook-or-2026-10-05.png" width="1200" height="630"/>
        </item>
        <item>
            <title>AMPLITUDE: Guides and Surveys Service Disruption</title>
            <link>https://whatbroke.today/incident/amplitude-guides-and-surveys-service-disruption-2026-10-05</link>
            <description><![CDATA[⚪ Amplitude's Guides and Surveys service took an unexpected 8-minute nap between 11:40-11:48 AM PT, leaving users unable to create, edit, or publish anything. They've since woken up and claim everything's fine, though they're still checking if anyone left the stove on. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-05 19:03:14</pubDate>
            <guid>https://whatbroke.today/incident/amplitude-guides-and-surveys-service-disruption-2026-10-05</guid>
            <enclosure url="https://whatbroke.today/api/og/amplitude-guides-and-surveys-service-disruption-2026-10-05.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/amplitude-guides-and-surveys-service-disruption-2026-10-05.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/amplitude-guides-and-surveys-service-disruption-2026-10-05.png" width="1200" height="630"/>
        </item>
        <item>
            <title>CLOUDINARY: Usage reports unavailable in Console Dashboard</title>
            <link>https://whatbroke.today/incident/cloudinary-usage-reports-unavailable-in-console-dashboard-2026-10-05</link>
            <description><![CDATA[⚪ Your image metrics ghosted you for 33 minutes while Cloudinary's dashboard decided to stop counting. The good news: they found them under the couch. Everything's back to pretending to track your bandwidth now. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-05 12:20:59</pubDate>
            <guid>https://whatbroke.today/incident/cloudinary-usage-reports-unavailable-in-console-dashboard-2026-10-05</guid>
            <enclosure url="https://whatbroke.today/api/og/cloudinary-usage-reports-unavailable-in-console-dashboard-2026-10-05.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/cloudinary-usage-reports-unavailable-in-console-dashboard-2026-10-05.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/cloudinary-usage-reports-unavailable-in-console-dashboard-2026-10-05.png" width="1200" height="630"/>
        </item>
        <item>
            <title>CODECOV: Codecov app and services are down</title>
            <link>https://whatbroke.today/incident/codecov-codecov-app-and-services-are-down-2026-10-05</link>
            <description><![CDATA[{
  "skip": false,
  "headline": "Codecov vanishes into the void, investigation ongoing",
  "summary": "🔴 Codecov's entire app and services decided to ghost everyone simultaneously. Engineers are "investigating" which is corporate for "frantically searching the logs with a flashlight." Your code coverage reports are taking an unscheduled vacation."
}. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-05 06:56:03</pubDate>
            <guid>https://whatbroke.today/incident/codecov-codecov-app-and-services-are-down-2026-10-05</guid>
            <enclosure url="https://whatbroke.today/api/og/codecov-codecov-app-and-services-are-down-2026-10-05.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/codecov-codecov-app-and-services-are-down-2026-10-05.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/codecov-codecov-app-and-services-are-down-2026-10-05.png" width="1200" height="630"/>
        </item>
        <item>
            <title>DIGITALOCEAN: A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)</title>
            <link>https://whatbroke.today/incident/digitalocean-a-network-disruption-in-blr1-region-2026-10-03</link>
            <description><![CDATA[⚪ BLR1 region went full Sleeping Beauty from 11:59-13:02 UTC, ghosting Monitoring, App Platform, Databases, Functions, Load Balancers, Spaces, and the control panel. Users got the classic combo of latency, dropped connections, and errors—basically a networking horror movie where the power came back before anyone got to the climax. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-03 14:58:10</pubDate>
            <guid>https://whatbroke.today/incident/digitalocean-a-network-disruption-in-blr1-region-2026-10-03</guid>
            <enclosure url="https://whatbroke.today/api/og/digitalocean-a-network-disruption-in-blr1-region-2026-10-03.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/digitalocean-a-network-disruption-in-blr1-region-2026-10-03.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/digitalocean-a-network-disruption-in-blr1-region-2026-10-03.png" width="1200" height="630"/>
        </item>
        <item>
            <title>FLY: Partial outage in AMS</title>
            <link>https://whatbroke.today/incident/fly-partial-outage-in-ams-2026-10-03</link>
            <description><![CDATA[🟠 Fly's Amsterdam region decided to take an unscheduled nap. Management plane and AMS hosts are stumbling back online while engineers frantically assess the damage. MPG impact assessment in progress—translation: they're still counting the bodies. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-03 08:12:50</pubDate>
            <guid>https://whatbroke.today/incident/fly-partial-outage-in-ams-2026-10-03</guid>
            <enclosure url="https://whatbroke.today/api/og/fly-partial-outage-in-ams-2026-10-03.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/fly-partial-outage-in-ams-2026-10-03.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/fly-partial-outage-in-ams-2026-10-03.png" width="1200" height="630"/>
        </item>
        <item>
            <title>LANGSMITH: LangSmith Deployment Database Provisioning Error</title>
            <link>https://whatbroke.today/incident/langsmith-langsmith-deployment-database-provisioning-error-2026-10-03</link>
            <description><![CDATA[🟡 LangSmith deployments are choking during database setup across GCP regions—turns out their cloud provider's infrastructure decided to take an unscheduled nap. The Control Plane is having an identity crisis and can't spin up new dedicated instances. Someone's definitely stress-testing their oncall rotation right now. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-03 05:20:56</pubDate>
            <guid>https://whatbroke.today/incident/langsmith-langsmith-deployment-database-provisioning-error-2026-10-03</guid>
            <enclosure url="https://whatbroke.today/api/og/langsmith-langsmith-deployment-database-provisioning-error-2026-10-03.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/langsmith-langsmith-deployment-database-provisioning-error-2026-10-03.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/langsmith-langsmith-deployment-database-provisioning-error-2026-10-03.png" width="1200" height="630"/>
        </item>
        <item>
            <title>OPENAI: Issues with login, signup, and ads</title>
            <link>https://whatbroke.today/incident/openai-issues-with-login-signup-and-ads-2026-10-01</link>
            <description><![CDATA[🟡 OpenAI's login, signup, and ads infrastructure caught a sudden case of amnesia. Users can't get in, ads won't serve, and the API is playing dead. Nothing says 'we have this under control' like simultaneously breaking the front door and the cash register. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-01 19:11:06</pubDate>
            <guid>https://whatbroke.today/incident/openai-issues-with-login-signup-and-ads-2026-10-01</guid>
            <enclosure url="https://whatbroke.today/api/og/openai-issues-with-login-signup-and-ads-2026-10-01.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/openai-issues-with-login-signup-and-ads-2026-10-01.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/openai-issues-with-login-signup-and-ads-2026-10-01.png" width="1200" height="630"/>
        </item>
        <item>
            <title>OPENAI: Issues with login and signup</title>
            <link>https://whatbroke.today/incident/openai-issues-with-login-and-signup-2026-10-01</link>
            <description><![CDATA[🟡 OpenAI's login system caught in an identity crisis—you can't get in, they can't get in, nobody gets in. The irony of an AI company unable to authenticate humans is *chef's kiss*. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-01 18:55:53</pubDate>
            <guid>https://whatbroke.today/incident/openai-issues-with-login-and-signup-2026-10-01</guid>
            <enclosure url="https://whatbroke.today/api/og/openai-issues-with-login-and-signup-2026-10-01.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/openai-issues-with-login-and-signup-2026-10-01.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/openai-issues-with-login-and-signup-2026-10-01.png" width="1200" height="630"/>
        </item>
        <item>
            <title>PYPI: Multiple services unavailable</title>
            <link>https://whatbroke.today/incident/pypi-multiple-services-unavailable-2026-10-01</link>
            <description><![CDATA[🔴 Multiple python.org services went dark after deprecated API usage tanked their internal certificates. The classic 'we updated the library and broke everything' play. Now frantically renewing certs and praying things resurrect. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-10-01 11:16:56</pubDate>
            <guid>https://whatbroke.today/incident/pypi-multiple-services-unavailable-2026-10-01</guid>
            <enclosure url="https://whatbroke.today/api/og/pypi-multiple-services-unavailable-2026-10-01.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/pypi-multiple-services-unavailable-2026-10-01.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/pypi-multiple-services-unavailable-2026-10-01.png" width="1200" height="630"/>
        </item>
        <item>
            <title>ELEVENLABS: Agents, STT, and Creative Platform: Increased Latency, Conversation Failures, and STT Failures</title>
            <link>https://whatbroke.today/incident/elevenlabs-agents-stt-and-creative-platform-increased-2026-09-29</link>
            <description><![CDATA[🟠 ElevenLabs' speech-to-text took a vow of silence while Agents and Creative Platform discovered what 'latency' really means. Engineers found the culprit but apparently need a moment to perform CPR on their infrastructure. (Auto-resolved: no updates in 24h)]]></description>
            <pubDate>2026-09-29 19:41:03</pubDate>
            <guid>https://whatbroke.today/incident/elevenlabs-agents-stt-and-creative-platform-increased-2026-09-29</guid>
            <enclosure url="https://whatbroke.today/api/og/elevenlabs-agents-stt-and-creative-platform-increased-2026-09-29.png" type="image/png" length="0"/>
            <media:content url="https://whatbroke.today/api/og/elevenlabs-agents-stt-and-creative-platform-increased-2026-09-29.png" type="image/png" medium="image" width="1200" height="630"/>
            <media:thumbnail url="https://whatbroke.today/api/og/elevenlabs-agents-stt-and-creative-platform-increased-2026-09-29.png" width="1200" height="630"/>
        </item>
    </channel>
</rss>