<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><description>Updates on the status of the Twitter service.</description><title>Twitter Status</title><generator>Tumblr (3.0; @twitterstatus)</generator><link>http://status.twitter.com/</link><item><title>Brief service issue</title><description>&lt;p&gt;Between 14:01 and 14:20 PDT today, some users may have experienced issues viewing and sending Tweets on twitter.com and Twitter’s mobile apps.&lt;/p&gt;
&lt;p&gt;Traffic was redirected away from the components that were experiencing problems, and the issue has now been resolved.&lt;/p&gt;
&lt;p&gt;We apologize for any inconvenience.&lt;/p&gt;</description><link>http://status.twitter.com/post/87929090503</link><guid>http://status.twitter.com/post/87929090503</guid><pubDate>Thu, 05 Jun 2014 15:11:00 -0700</pubDate></item><item><title>Tweet Display Delay in Home Timeline</title><description>&lt;p class="p1"&gt;&lt;span&gt;Between 13:26-14:39 PDT, some users may have experienced a delay in Tweets showing up in their home timelines. This issue has now been resolved. We apologize for the inconvenience&lt;/span&gt;&lt;/p&gt;</description><link>http://status.twitter.com/post/86247488608</link><guid>http://status.twitter.com/post/86247488608</guid><pubDate>Mon, 19 May 2014 14:59:00 -0700</pubDate></item><item><title>Service issue.</title><description>&lt;p&gt;Update: Traffic was redirected away from the components that were experiencing problems, and the issue has been resolved as of 15:27 PDT.&lt;/p&gt;
&lt;p&gt;We apologize for any inconvenience.&lt;/p&gt;

&lt;p&gt;Some users may be experiencing issues viewing and sending Tweets on &lt;a href="http://twitter.com/" target="_blank"&gt;twitter.com&lt;/a&gt; and Twitter’s mobile apps.&lt;/p&gt;</description><link>http://status.twitter.com/post/85654361638</link><guid>http://status.twitter.com/post/85654361638</guid><pubDate>Tue, 13 May 2014 13:55:00 -0700</pubDate></item><item><title>SSL Security Update</title><description>&lt;p&gt;On 4/7/2014 we were made aware of a critical vulnerability in OpenSSL (CVE-2014-0160), the security library that is widely used across the internet and at Twitter.&lt;/p&gt;
&lt;p&gt;We were able to determine that twitter.com and api.twitter.com servers were not affected by this vulnerability.&lt;/p&gt;
&lt;p&gt;We are continuing to monitor the situation.&lt;/p&gt;</description><link>http://status.twitter.com/post/82109064906</link><guid>http://status.twitter.com/post/82109064906</guid><pubDate>Tue, 08 Apr 2014 10:57:55 -0700</pubDate></item><item><title>Tweet display issue</title><description>&lt;p&gt;Update [March 26 at 10:55am PDT]: This issue has been resolved, and affected Tweets, along with the favorites and retweets on those Tweets, have been restored.&lt;/p&gt;
&lt;p&gt;We are currently researching a bug that has caused some Tweets to not be displayed.&lt;/p&gt;</description><link>http://status.twitter.com/post/80718245447</link><guid>http://status.twitter.com/post/80718245447</guid><pubDate>Tue, 25 Mar 2014 15:41:00 -0700</pubDate></item><item><title>Service issue</title><description>&lt;p&gt;Update [12:12pm PDT]: During a planned deploy in one of our core services, we experienced unexpected complications that made Twitter unavailable for many users starting at 11:01am. We rolled back the change as soon as we identified the issue and began a controlled recovery to ensure stability of other parts of the service. The site was fully recovered by 11:47am PDT. We apologize for the inconvenience. &lt;/p&gt;
&lt;p&gt;Most users are experiencing issues accessing Twitter on web and mobile apps. We&amp;#8217;re looking into it. &lt;/p&gt;</description><link>http://status.twitter.com/post/79278902130</link><guid>http://status.twitter.com/post/79278902130</guid><pubDate>Tue, 11 Mar 2014 11:23:00 -0700</pubDate></item><item><title>Brief service issue</title><description>&lt;p&gt;Between 19:05 and 19:29 PST today, some users may have experienced issues viewing and sending Tweets on &lt;a href="http://twitter.com/" target="_blank"&gt;twitter.com&lt;/a&gt; and Twitter’s mobile apps.&lt;/p&gt;
&lt;p&gt;Traffic was redirected away from the components that were experiencing problems, and the issue has now been resolved.&lt;/p&gt;
&lt;p&gt;We apologize for any inconvenience.&lt;/p&gt;</description><link>http://status.twitter.com/post/78400054104</link><guid>http://status.twitter.com/post/78400054104</guid><pubDate>Sun, 02 Mar 2014 19:50:55 -0800</pubDate></item><item><title>Brief service issue</title><description>&lt;p&gt;&lt;span&gt;Between 13:19 and 13:37 PST today, some users may have experienced issues viewing and sending Tweets on &lt;/span&gt;&lt;a href="http://twitter.com/" target="_blank"&gt;twitter.com&lt;/a&gt;&lt;span&gt; and Twitter’s mobile apps. This was due to an issue with our caching layer in one region.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Traffic was redirected away from the problematic components, and the issue has now been resolved.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;We apologize for the inconvenience.&lt;/span&gt;&lt;/p&gt;</description><link>http://status.twitter.com/post/74877960893</link><guid>http://status.twitter.com/post/74877960893</guid><pubDate>Tue, 28 Jan 2014 15:05:57 -0800</pubDate></item><item><title>Brief service issue</title><description>&lt;p&gt;Between &lt;span class="aBn" data-term="goog_554616608"&gt;&lt;span class="aQJ"&gt;10:39AM and 10:48AM PST&lt;/span&gt;&lt;/span&gt; today, some users may have experienced issues viewing and sending Tweets on &lt;a href="http://twitter.com/" target="_blank"&gt;twitter.com&lt;/a&gt; and Twitter&amp;#8217;s mobile apps.&lt;/p&gt;
&lt;p&gt;This issue has been addressed and we apologize for the inconvenience.&lt;/p&gt;</description><link>http://status.twitter.com/post/73429900886</link><guid>http://status.twitter.com/post/73429900886</guid><pubDate>Wed, 15 Jan 2014 11:15:00 -0800</pubDate></item><item><title>Brief mobile service issue</title><description>&lt;p&gt;Between 14:02 and 14:16 PST today, some users were not able to load timelines on mobile devices.&lt;br/&gt;This issue has been addressed and we apologize for the inconvenience.&lt;/p&gt;</description><link>http://status.twitter.com/post/66717974698</link><guid>http://status.twitter.com/post/66717974698</guid><pubDate>Mon, 11 Nov 2013 14:39:03 -0800</pubDate></item><item><title>Issue viewing timelines</title><description>&lt;p&gt;&lt;span&gt;For about 5 minutes, from 13:36-13:41, users experienced issues viewing timelines on twitter.com. The issue also affected the ability to get new Tweets on mobile clients. This was due to a code-related error, which was quickly rolled back. We apologize for the inconvenience.&lt;/span&gt;&lt;br/&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;</description><link>http://status.twitter.com/post/63765159379</link><guid>http://status.twitter.com/post/63765159379</guid><pubDate>Fri, 11 Oct 2013 15:03:19 -0700</pubDate></item><item><title>Twitter site issue</title><description>&lt;p&gt;&lt;span&gt;Some users may experience issues trying to access &lt;/span&gt;&lt;a href="http://twitter.com/"&gt;&lt;span class="s1"&gt;twitter.com&lt;/span&gt;&lt;/a&gt;&lt;span&gt;. Access to Twitter on mobile apps is not affected.&lt;/span&gt;&lt;/p&gt;
&lt;p class="p1"&gt;&lt;span&gt;Update: &lt;/span&gt;&lt;span&gt;As of 14:19 PDT, this issue has been resolved. &lt;/span&gt;&lt;span&gt;Due to a code-related error, a series of web servers went down from 13:48-14:19 PDT, making the twitter.com website inaccessible for some users. We apologize for any inconvenience.&lt;/span&gt;&lt;/p&gt;</description><link>http://status.twitter.com/post/60295900552</link><guid>http://status.twitter.com/post/60295900552</guid><pubDate>Wed, 04 Sep 2013 14:02:00 -0700</pubDate></item><item><title>twitter service issue</title><description>&lt;p&gt;At &lt;span class="aBn"&gt;&lt;span class="aQJ"&gt;20:49 UTC&lt;/span&gt;&lt;/span&gt;, our DNS registrar experienced an issue in which it appears DNS records for various organizations were modified, including one of Twitter’s domains used for image serving, &lt;a href="http://twimg.com/" target="_blank"&gt;twimg.com&lt;/a&gt;. Viewing of images and photos was sporadically impacted. By &lt;span class="aBn"&gt;&lt;span class="aQJ"&gt;22:29 UTC&lt;/span&gt;&lt;/span&gt;, the original domain record for &lt;a href="http://twimg.com/" target="_blank"&gt;twimg.com&lt;/a&gt; was restored.  No Twitter user information was affected by this incident.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;[UPDATE, 8/28/13: Post updated to reflect that the issue was with our DNS registrar, not our DNS provider.]&lt;/em&gt;&lt;/p&gt;</description><link>http://status.twitter.com/post/59528478030</link><guid>http://status.twitter.com/post/59528478030</guid><pubDate>Tue, 27 Aug 2013 15:59:00 -0700</pubDate></item><item><title>Accessing twitter</title><description>&lt;p&gt;Update: As of 14:19 PDT, this issues has been resolved.&lt;/p&gt;
&lt;p&gt;Due to unexpected issues during a maintenance, some users were not able to get to twitter.com or load mobile timelines from 13:55 until 14:19 PDT. We apologize for the inconvenience.&lt;/p&gt;

&lt;p&gt;Some users may be experiencing issues reaching twitter right now.&lt;/p&gt;
&lt;p&gt;Our engineers are currently working to resolve this.&lt;/p&gt;</description><link>http://status.twitter.com/post/57549594622</link><guid>http://status.twitter.com/post/57549594622</guid><pubDate>Tue, 06 Aug 2013 14:19:00 -0700</pubDate></item><item><title>Twitter Site Issue</title><description>&lt;p&gt;Update: This issue has been resolved.&lt;/p&gt;

&lt;p class="MsoNormal"&gt;Due to an error in a routine change, Twitter was not available from 1:08pm PDT to 1:33pm PDT.  We rolled back the erroneous change as soon as we identified the issue. Additionally, some users may have experienced Tweet delivery delay from 1:33pm PDT and 1:53pm PDT.  We apologize for the inconvenience.&lt;/p&gt;

&lt;p&gt;&lt;!--EndFragment--&gt;&lt;/p&gt;

&lt;p&gt;Some users may be experiencing issues accessing Twitter. Our engineers are currently working to resolve the issue.&lt;/p&gt;</description><link>http://status.twitter.com/post/52079734757</link><guid>http://status.twitter.com/post/52079734757</guid><pubDate>Mon, 03 Jun 2013 13:22:00 -0700</pubDate></item><item><title>Twitter Service Issue</title><description>&lt;p&gt;Some web users may be experiencing empty timelines and some users may be experiencing an issue with Twitter on mobile devices. Our engineers are currently working on this issue.&lt;/p&gt;
&lt;p&gt;Update: This issue is resolved as of 6:37pm PST.&lt;/p&gt;</description><link>http://status.twitter.com/post/51182356736</link><guid>http://status.twitter.com/post/51182356736</guid><pubDate>Thu, 23 May 2013 16:22:00 -0700</pubDate></item><item><title>Photo Upload Issue</title><description>&lt;p&gt;&lt;span&gt;Update: This issue has been resolved.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Some users may be experiencing an issue when uploading a photo. Our engineers are currently working on this issue.&lt;/span&gt;&lt;/p&gt;</description><link>http://status.twitter.com/post/49351191080</link><guid>http://status.twitter.com/post/49351191080</guid><pubDate>Wed, 01 May 2013 03:50:00 -0700</pubDate></item><item><title>Twitter Service Issue</title><description>&lt;p&gt;Update: As of 8:50am PT, this issue has been resolved.&lt;/p&gt;
&lt;p&gt;Some users may be experiencing an issue with our service. Our engineers are currently working on this issue.&lt;/p&gt;</description><link>http://status.twitter.com/post/48691747345</link><guid>http://status.twitter.com/post/48691747345</guid><pubDate>Tue, 23 Apr 2013 06:33:00 -0700</pubDate></item><item><title>Issue with Links Contained within Tweets</title><description>&lt;p&gt;&lt;em&gt;Some users may have experienced an issue with links contained within Tweets. This issue has been resolved as of 7:10 am PST.&lt;/em&gt;&lt;/p&gt;</description><link>http://status.twitter.com/post/47701778304</link><guid>http://status.twitter.com/post/47701778304</guid><pubDate>Thu, 11 Apr 2013 07:28:46 -0700</pubDate></item><item><title>Twitter API v1: Temporary shutdown</title><description>&lt;p&gt;&lt;span&gt;We are temporarily turning off API v1 later today, Wednesday, March 20th, for one hour — approximately 3-4&amp;#160;pm PDT (10-11&amp;#160;pm GMT). **Only third-party applications that have not yet transitioned over to API v1.1, the new version of the API, will be affected.** If you’re using one of those apps during this one-hour window, you’ll experience a service disruption. Thank you for your patience during this test.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;This blackout test is one of several that will take place in the weeks leading up to retiring API v1. We’re doing this to help developers understand the impact that retirement will have on their applications and services. &lt;a href="https://dev.twitter.com/blog/api-v1-retirement-update"&gt;This post&lt;/a&gt; has more information; you can also follow &lt;a href="https://twitter.com/twitterapi"&gt;@twitterapi&lt;/a&gt; for updates.&lt;/p&gt;</description><link>http://status.twitter.com/post/45844838185</link><guid>http://status.twitter.com/post/45844838185</guid><pubDate>Wed, 20 Mar 2013 10:42:00 -0700</pubDate></item></channel></rss>
