<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr">Same error message for me in NJ via multiple circuits. Unsurprisingly their status page (status.twitter.com) reports no issues.</div><div dir="ltr"><br></div><div dir="ltr">-joe</div><div dir="ltr"><br><blockquote type="cite">On Oct 15, 2020, at 5:58 PM, Ryan McGinnis via Outages <outages@outages.org> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"> <div>TWITTER’S FULL!</div><div><br></div><div>But seriously, it’s also down for me here in Nebraska. Didn’t log me out but I get the “something went wrong” message. <caret></caret></div><div><br></div><div id="protonmail_signature_block" class="protonmail_signature_block"><div><div>-Ryan McGinnis<br></div><div>http://www.bigstormpicture.com<br></div><div>PGP Fingerprint: 5C73 8727 EE58 786A 777C 4F1D B5AA 3FA3 486E D7AD<br></div></div></div> <div><br></div><div><br></div>On Thu, Oct 15, 2020 at 16:45, Patrick W. Gilmore via Outages <<a href="mailto:outages@outages.org" class="">outages@outages.org</a>> wrote:<blockquote class="protonmail_quote" type="cite"> Interestingly, http://downforme.org/is-twitter.com-down-today-for-everyone confirms, but https://downforeveryoneorjustme.com/twitter says it is up.<br><br>I can get to the server, but get the “something went wrong, try again”. Perhaps the second URL above only checked HTTP response?<br><br>Been down a few minutes.<br><br>--<br>TTFN,<br>patrick<br><br>_______________________________________________<br>Outages mailing list<br>Outages@outages.org<br>https://puck.nether.net/mailman/listinfo/outages<br></blockquote><div><br></div><div><br></div>
<span>_______________________________________________</span><br><span>Outages mailing list</span><br><span>Outages@outages.org</span><br><span>https://puck.nether.net/mailman/listinfo/outages</span><br></div></blockquote></body></html>