<story><title>Incident with Issues and Pull Requests</title><url>https://www.githubstatus.com/incidents/nf7s6933tnn8</url></story><parent_chain><item><author>dbingham</author><text>What is going on over there?  Third day in a row is... kind of impressive.</text></item></parent_chain><comment><author>aranw</author><text>Lots of copilot generated code failing</text></comment>
<story><title>Incident with Issues and Pull Requests</title><url>https://www.githubstatus.com/incidents/nf7s6933tnn8</url></story><parent_chain><item><author>dbingham</author><text>What is going on over there?  Third day in a row is... kind of impressive.</text></item></parent_chain><comment><author>iepathos</author><text>They blamed the march and april outages on some database query that was changed due to an infrastructure change they rolled out.  I&amp;#x27;m guessing their infrastructure change caused some other race condition issue that they are only seeing after major production failure due to not load testing enough in their staging environment &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.blog&amp;#x2F;2023-05-03-github-availability-report-april-2023&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.blog&amp;#x2F;2023-05-03-github-availability-report-ap...&lt;/a&gt;</text></comment>