CINXE.COM

<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[System Status Page]]></title><description><![CDATA[Status Feed]]></description><link>https://status.io/pages/564314ae3309c22c3b0002fa</link><generator>RSS for Node</generator><lastBuildDate>Tue, 22 Aug 2023 23:32:33 GMT</lastBuildDate><atom:link href="https://status.io/pages/564314ae3309c22c3b0002fa/rss" rel="self" type="application/rss+xml"/><ttl>10</ttl><item><title><![CDATA[Twitter service disruption]]></title><description><![CDATA[October 15, 2020 10:10PM UTC Investigating - We know people are having trouble Tweeting and using Twitter. We’re working to fix this issue as quickly as possible. October 15, 2020 10:41PM UTC Investigating - We have no evidence this outage is caused by a security breach or hack. We’re currently investigating internal root causes and will share more soon. October 16, 2020 12:06AM UTC Identified - The recent issue was caused by an inadvertent change we made to our internal systems. Twitter should be working for everyone within the next few hours. October 16, 2020 3:33AM UTC Resolved - And we’re all clear –– Twitter should be working as expected for everyone. We appreciate you sticking with us. ]]></description><link>https://status.io/pages/incident/564314ae3309c22c3b0002fa/5f88c8e77f50b304c1e7c234</link><guid isPermaLink="false">5f88c8e77f50b304c1e7c234</guid><pubDate>Fri, 16 Oct 2020 03:33:26 GMT</pubDate></item><item><title><![CDATA[Some users may be experiencing issues using Twitter]]></title><description><![CDATA[February 7, 2020 9:38PM UTC Investigating - You might be experiencing trouble sending new Tweets, but we’re working on fixing this now. Sorry for the interruption and we’ll let you know when things are back to normal. February 7, 2020 10:07PM UTC Resolved - You can get back to Tweeting –– this problem has been fixed! Thanks for sticking with us through that. ]]></description><link>https://status.io/pages/incident/564314ae3309c22c3b0002fa/5e3dd8db11859604c48a3761</link><guid isPermaLink="false">5e3dd8db11859604c48a3761</guid><pubDate>Fri, 07 Feb 2020 22:07:41 GMT</pubDate></item><item><title><![CDATA[Some users may be experiencing issues using Twitter]]></title><description><![CDATA[October 2, 2019 8:23AM UTC Investigating - We've been experiencing outages across Twitter and TweetDeck. You might have had trouble Tweeting, getting notifications, or viewing DMs. We're currently working on a fix, and should be back to normal soon. October 2, 2019 10:52AM UTC Resolved - The issue is just about fixed. You should be able to access Twitter as usual. If not, give it a few more minutes! Thanks for waiting ]]></description><link>https://status.io/pages/incident/564314ae3309c22c3b0002fa/5d945e99b9ff556cc55db407</link><guid isPermaLink="false">5d945e99b9ff556cc55db407</guid><pubDate>Wed, 02 Oct 2019 10:52:23 GMT</pubDate></item><item><title><![CDATA[Issues accessing Twitter]]></title><description><![CDATA[July 11, 2019 6:58PM UTC Investigating - We are currently investigating issues people are having accessing Twitter. We will keep you updated on whats happening. July 11, 2019 7:56PM UTC Identified - The outage was due to an internal configuration change, which we're now fixing. Some people may be able to access Twitter again and we're working to make sure Twitter is available to everyone as quickly as possible. July 11, 2019 9:10PM UTC Monitoring - Twitter is now back up for most people. We're working to get to 100% soon. July 12, 2019 6:49PM UTC Resolved - Thanks for your patience, Twitter is now back to 100% ]]></description><link>https://status.io/pages/incident/564314ae3309c22c3b0002fa/5d2786d7d1fca743f20be3f3</link><guid isPermaLink="false">5d2786d7d1fca743f20be3f3</guid><pubDate>Fri, 12 Jul 2019 18:49:10 GMT</pubDate></item><item><title><![CDATA[April 20, 2018 service disruptions]]></title><description><![CDATA[April 20, 2018 6:14PM UTC Investigating - Currently people are unable to Tweet, engineering teams are investigating. April 20, 2018 6:34PM UTC Resolved - Earlier today, people were unable to send Tweets on Twitter for about 30 minutes. We've resolved the internal issue and we're sorry for the disruption. ]]></description><link>https://status.io/pages/incident/564314ae3309c22c3b0002fa/5ada2d8e7afe4904e701f820</link><guid isPermaLink="false">5ada2d8e7afe4904e701f820</guid><pubDate>Fri, 20 Apr 2018 18:34:00 GMT</pubDate></item><item><title><![CDATA[Some users my have experienced issues sending Tweets]]></title><description><![CDATA[May 19, 2017 6:41AM UTC Resolved - Starting at 10:01 PDT some user may have had issues sending tweets from twitter.com and the mobile apps. The team has been working hard on this and the issue has now been resolved. ]]></description><link>https://status.io/pages/incident/564314ae3309c22c3b0002fa/591e937de69f3884250016a8</link><guid isPermaLink="false">591e937de69f3884250016a8</guid><pubDate>Fri, 19 May 2017 06:41:01 GMT</pubDate></item><item><title><![CDATA[Twitter intermittently unavailable for some users]]></title><description><![CDATA[November 7, 2016 6:44AM UTC Investigating - Starting at 21:46 PDT some user may have had issues reaching twitter.com and using the mobile apps. The issue is thought to be resolved at this time but we are continuing to investigate the root cause. November 7, 2016 7:01AM UTC Resolved - As of 22:18 PDT service was restored and engineers continue to investigate the root cause of this incident. ]]></description><link>https://status.io/pages/incident/564314ae3309c22c3b0002fa/582022b6052367c562000a50</link><guid isPermaLink="false">582022b6052367c562000a50</guid><pubDate>Mon, 07 Nov 2016 07:01:00 GMT</pubDate></item><item><title><![CDATA[Some users may have experienced issues reaching twitter domains.]]></title><description><![CDATA[October 21, 2016 4:44PM UTC Identified - Since ~8:52 PDT the external DNS service which twitter uses is once again seeing problems affecting multiple internet services, including twitter.com. October 21, 2016 9:09PM UTC Resolved - As of 13:25, the significant attacks hindering the external DNS provider have been mitigated by them. Twitter should once again be available to all users. Engineers continue to investigate the root causes and mitigation strategies. ]]></description><link>https://status.io/pages/incident/564314ae3309c22c3b0002fa/580a45e07170c621190011e9</link><guid isPermaLink="false">580a45e07170c621190011e9</guid><pubDate>Fri, 21 Oct 2016 21:09:15 GMT</pubDate></item><item><title><![CDATA[Some users may have experienced issues reaching twitter domains.]]></title><description><![CDATA[October 21, 2016 2:28PM UTC Resolved - Between approximately 4:10 and 6:10 PDT, various Twitter domains, including twitter.com may have been inaccessible for users in some regions, due to failures resolving particular DNS hostnames. This issue has now been resolved. We apologize for any inconvenience, and thanks for your patience! ]]></description><link>https://status.io/pages/incident/564314ae3309c22c3b0002fa/580a25fbe60a2e2019001342</link><guid isPermaLink="false">580a25fbe60a2e2019001342</guid><pubDate>Fri, 21 Oct 2016 14:28:11 GMT</pubDate></item><item><title><![CDATA[Issue reaching twitter.com]]></title><description><![CDATA[August 16, 2016 1:49AM UTC Investigating - Some users may be experiencing issues reaching twitter.com. Mobile apps and api are not affected. Team is investigating. August 16, 2016 2:37AM UTC Resolved - This issue has now been resolved. The problem was related to a code deploy, which has been rolled back. We apologize for any inconvenience, and thanks for your patience! ]]></description><link>https://status.io/pages/incident/564314ae3309c22c3b0002fa/57b2713d2d8d333607001411</link><guid isPermaLink="false">57b2713d2d8d333607001411</guid><pubDate>Tue, 16 Aug 2016 02:37:08 GMT</pubDate></item></channel></rss>