X seems to be working again after struggling with an outage that took the service offline and made it slow to load for much of the morning. According to X’s developer platform class=”link ” href=”https://docs.x.com/status” data-i13n=”cpos:1;pos:1″ rel=”nofollow noopener” target=”_blank” data-ylk=”slk:page;cpos:1;pos:1;elm:context_link;itc:0;sec:content-canvas” data-yga=”{"yLinkText":"page","yLinkPosition":"1","yPosition":"1","yLinkElement":"context_link","yModuleName":"content-canvas"}”>page, there is an class=”link ” href=”https://docs.x.com/incidents” data-i13n=”cpos:2;pos:1″ rel=”nofollow noopener” target=”_blank” data-ylk=”slk:ongoing incident;cpos:2;pos:1;elm:context_link;itc:0;sec:content-canvas” data-yga=”{"yLinkText":"ongoing incident","yLinkPosition":"2","yPosition":"1","yLinkElement":"context_link","yModuleName":"content-canvas"}”>ongoing incident related to streaming endpoints that’s caused increased errors. The incident started at 7:39AM PT, according to the page.
That roughly coincides with a spike in reports at class=”link ” href=”https://downdetector.com/status/twitter/” data-i13n=”cpos:3;pos:1″ rel=”nofollow noopener” target=”_blank” data-ylk=”slk:Down Detector;cpos:3;pos:1;elm:context_link;itc:0;sec:content-canvas” data-yga=”{"yLinkText":"Down Detector","yLinkPosition":"3","yPosition":"1","yLinkElement":"context_link","yModuleName":"content-canvas"}”>Down Detector. The issues seemed to be somewhat intermittent. At some points, X’s website loaded partially and only…
