Many users are receiving incorrect “Rate Limit Exceeded” errors through the Twitter API. We are investigating the cause and will update when it is resolved.

http://status.twitter.com/post/781763549http://status.twitter.com/post/781763549Wed, 07 Jul 2010 10:56:34 -0700Incorrect Rate-Limiting

We’re hearing reports from developers that they’re running into some incorrect rate limits; we’re looking into it.

http://status.twitter.com/post/777268689http://status.twitter.com/post/777268689Tue, 06 Jul 2010 09:17:30 -0700Missing @ Replies

Some users are experiencing an issue in which they’re not receiving all of their @ replies; we’re working on a fix.

http://status.twitter.com/post/773257081http://status.twitter.com/post/773257081Mon, 05 Jul 2010 09:33:56 -0700Mobile Website

We’re working to resolve an issue with the mobile website, http://mobile.twitter.com.

UPDATE: Resolved at 15:31 UTC / 8:31 PDT.

http://status.twitter.com/post/773077785http://status.twitter.com/post/773077785Mon, 05 Jul 2010 08:25:00 -0700Investigating Elevated Error Rates

We’ve received reports of elevated error rates for users; we’re currently investigating.

Update (9:47 AM PST, 16:47 UTC): This is unplanned downtime. Infrastructure and operations engineers are working to fully restore Twitter. Expect more updates soon.

Update (9:55 AM PST, 16:55 UTC): We are now recovering from a period of high unavailability.

http://status.twitter.com/post/761957887http://status.twitter.com/post/761957887Fri, 02 Jul 2010 09:03:00 -0700API issues.

We are experiencing an issue temporarily with the intermediary SSL certificate for the API; we expect the issue to be resolved shortly. In the meantime, you may experience issues using the API; we’re working to resolve the issue now.

Update (8:22 AM PST, 15:22 UTC): This issue is resolved.

http://status.twitter.com/post/757821815http://status.twitter.com/post/757821815Thu, 01 Jul 2010 07:51:00 -0700Site Tweaks

We’re temporarily lowering the API rate-limit to 75 from 175; we do plan to reestablish the higher API rate-limit later today.

Update (9:35 AM PST, 16:35 UTC): We’ve temporarily disabled integrated search.

Update (9:50 AM PST, 16:50 UTC): We’ve reenabled integrated search.

Update (10:20 AM PST, 17:20 UTC): The API rate-limit has been restored to 175.

Update (13:09 PST, 20:09 UTC): Users may be experiencing some delay with their timelines; we’re aware of this and working to resolve this.

Update (13:45 PST, 20:45 UTC): Timelines are no longer delayed.

Update (20:55 PST, 03:45 UTC): Lists are temporarily disabled.

Update (21:22 PST, 04:22 UTC): Users will temporarily not see Tweet counts on their home pages; they remain on the profile pages. SMS delivery of tweets was disabled for approximately 30 minutes but should now be restored.

Update (22:05 PST, 05:05 UTC):Lists and Tweet counts are now back.

http://status.twitter.com/post/750140886http://status.twitter.com/post/750140886Tue, 29 Jun 2010 09:32:00 -0700Site Tweaks

We’ll be making adjustments to some site features throughout the day in an attempt to maximize site availability and stability.

Update (7:25 AM PST, 14:25 UTC): RSS and Atom feeds are currently disabled.

Update (8:05 AM PST, 15:05 UTC): API is temporarily rate-limited to 175.

Update (16:05 PM PST, 23:05 UTC): RSS and Atom feeds are re-enabled.

http://status.twitter.com/post/731461313http://status.twitter.com/post/731461313Thu, 24 Jun 2010 07:19:00 -0700Dealing with high whales (errors) as the result of high load.

Dealing with high whales (errors) as the result of high load. Ops and engineering are responding. Also go #usa!

http://status.twitter.com/post/729248199http://status.twitter.com/post/729248199Wed, 23 Jun 2010 09:19:21 -0700 Periodic high rates of errors on Twitter.com

We’re seeing periodic high rates of errors on Twitter.com.

http://status.twitter.com/post/729182197http://status.twitter.com/post/729182197Wed, 23 Jun 2010 08:15:49 -0700Periodic high rates of errors on Twitter.com

We’re seeing periodic high rates of errors on Twitter.com.

http://status.twitter.com/post/725629754http://status.twitter.com/post/725629754Tue, 22 Jun 2010 08:30:11 -0700High Error Rate on Twitter.com

We’re seeing periodic high rates of errors on Twitter.com.

Update Jun 21 17:42 UTC: The rate of errors has been reduced to a moderate level.

http://status.twitter.com/post/721918879http://status.twitter.com/post/721918879Mon, 21 Jun 2010 06:54:00 -0700Moderate Error Rate on Twitter.com

We’re seeing periodic moderate rates of errors on Twitter.com.

http://status.twitter.com/post/715119716http://status.twitter.com/post/715119716Sat, 19 Jun 2010 07:54:06 -0700Twitter Unavailable

22:20 UTC - 3:20 PDT Twitter is unavailable. Engineering and ops are responding.

22:59 UTC - 4:00 PDT Site is recovering.

http://status.twitter.com/post/709347163http://status.twitter.com/post/709347163Thu, 17 Jun 2010 15:34:00 -0700High Error Rate on Twitter.com

We’re seeing periodic high rates of errors on Twitter.com. This is the result of testing and maintenance. We expect our maintenance to end at approximately @ Wed Jun 16 14:30 UTC

You can read more here.

http://status.twitter.com/post/704452963http://status.twitter.com/post/704452963Wed, 16 Jun 2010 06:23:00 -0700Network Maintenance June 16th @ 13:00-14:30 UTC (6-7:30AM PDT)

MAINTENANCE ACTION:
—————————
We’ll be working with our network provider to perform some tests and maintenance. During this time you can expect a high rate of errors (whales)

DATE/TIME WINDOW:
—————————
June 16th @ 13:00-14:30 UTC (6-7:30AM PDT)

AFFECTED RESOURCES:

———————————

Twitter.com and Api.twitter.com

Update: Wed Jun 16 17:08:12 UTC 2010: We’re extending what is more accurately described as a window of observation. We expect to close this window of observation at 18:00 UTC.

http://status.twitter.com/post/704415654http://status.twitter.com/post/704415654Wed, 16 Jun 2010 06:06:00 -0700Trends have been temporarily disabled

Trends have been temporarily disabled. We’ll re-enable them in approximately in two hours.

Update 2:38PM PDT: Trends have been re-enabled.

http://status.twitter.com/post/701815165http://status.twitter.com/post/701815165Tue, 15 Jun 2010 12:23:00 -0700Temporarily Missing Tweets

Users may temporarily experience missing or duplicate tweets from their timelines. This is the result of the Failed Enhancement of Our Timeline Cache last night.

Normal timelines can restored by repeated refreshing your browser.

http://status.twitter.com/post/701488906http://status.twitter.com/post/701488906Tue, 15 Jun 2010 10:17:20 -0700High Error Rate on Twitter.com

We’re currently experiencing a high rate of errors (whales) on Twitter.com.

Our infrastructure and operations engineers are responding to the incident.

Update 9:22 AM PDT: We’ve temporarily turned off our Twitter Places (Geo) feature to reduce the high rate of errors.

Update 2:39 PDT: Twitter Places has been re-enabled.

Please Note: Users may temporarily experience missing or duplicate tweets from their timelines. Normal timelines can restored by refreshing your browser.

http://status.twitter.com/post/701016717http://status.twitter.com/post/701016717Tue, 15 Jun 2010 06:59:00 -0700Site Availability Issues Due to Failed Enhancement of Our Timeline Cache

Update: We’re currently experiencing site availability issues resulting from the failed enhancement of a new approach to timeline caching. Our infrastructure and operations engineers are currently working to resolve this. We’ll update you soon with an ETA.

Update: 10:17 PM PDT: Users may temporarily experience missing tweets from their timelines. They will be restored shortly.

Update: 11:51 PM PDT: We’re recovering from the site outage. Remember, users may temporarily experience missing or duplicate tweets from their timelines. Normal timelines will be restored shortly.

Update: June 15th 04:11 AM: The site is fully recovered.

Please Note: Users may temporarily experience missing or duplicate tweets from their timelines. Normal timelines can restored by refreshing your browser.

http://status.twitter.com/post/699623494http://status.twitter.com/post/699623494Mon, 14 Jun 2010 20:17:00 -0700">Updates on the status of the Twitter service.Twitter StatusTumblr (3.0; @twitterstatus)http://status.twitter.com/Investigating "Rate Limit Exceeded" issues

Many users are receiving incorrect “Rate Limit Exceeded” errors through the Twitter API. We are investigating the cause and will update when it is resolved.

http://status.twitter.com/post/781763549http://status.twitter.com/post/781763549Wed, 07 Jul 2010 10:56:34 -0700Incorrect Rate-Limiting

We’re hearing reports from developers that they’re running into some incorrect rate limits; we’re looking into it.

http://status.twitter.com/post/777268689http://status.twitter.com/post/777268689Tue, 06 Jul 2010 09:17:30 -0700Missing @ Replies

Some users are experiencing an issue in which they’re not receiving all of their @ replies; we’re working on a fix.

http://status.twitter.com/post/773257081http://status.twitter.com/post/773257081Mon, 05 Jul 2010 09:33:56 -0700Mobile Website

We’re working to resolve an issue with the mobile website, http://mobile.twitter.com.

UPDATE: Resolved at 15:31 UTC / 8:31 PDT.

http://status.twitter.com/post/773077785http://status.twitter.com/post/773077785Mon, 05 Jul 2010 08:25:00 -0700Investigating Elevated Error Rates

We’ve received reports of elevated error rates for users; we’re currently investigating.

Update (9:47 AM PST, 16:47 UTC): This is unplanned downtime. Infrastructure and operations engineers are working to fully restore Twitter. Expect more updates soon.

Update (9:55 AM PST, 16:55 UTC): We are now recovering from a period of high unavailability.

http://status.twitter.com/post/761957887http://status.twitter.com/post/761957887Fri, 02 Jul 2010 09:03:00 -0700API issues.

We are experiencing an issue temporarily with the intermediary SSL certificate for the API; we expect the issue to be resolved shortly. In the meantime, you may experience issues using the API; we’re working to resolve the issue now.

Update (8:22 AM PST, 15:22 UTC): This issue is resolved.

http://status.twitter.com/post/757821815http://status.twitter.com/post/757821815Thu, 01 Jul 2010 07:51:00 -0700Site Tweaks

We’re temporarily lowering the API rate-limit to 75 from 175; we do plan to reestablish the higher API rate-limit later today.

Update (9:35 AM PST, 16:35 UTC): We’ve temporarily disabled integrated search.

Update (9:50 AM PST, 16:50 UTC): We’ve reenabled integrated search.

Update (10:20 AM PST, 17:20 UTC): The API rate-limit has been restored to 175.

Update (13:09 PST, 20:09 UTC): Users may be experiencing some delay with their timelines; we’re aware of this and working to resolve this.

Update (13:45 PST, 20:45 UTC): Timelines are no longer delayed.

Update (20:55 PST, 03:45 UTC): Lists are temporarily disabled.

Update (21:22 PST, 04:22 UTC): Users will temporarily not see Tweet counts on their home pages; they remain on the profile pages. SMS delivery of tweets was disabled for approximately 30 minutes but should now be restored.

Update (22:05 PST, 05:05 UTC):Lists and Tweet counts are now back.

http://status.twitter.com/post/750140886http://status.twitter.com/post/750140886Tue, 29 Jun 2010 09:32:00 -0700Site Tweaks

We’ll be making adjustments to some site features throughout the day in an attempt to maximize site availability and stability.

Update (7:25 AM PST, 14:25 UTC): RSS and Atom feeds are currently disabled.

Update (8:05 AM PST, 15:05 UTC): API is temporarily rate-limited to 175.

Update (16:05 PM PST, 23:05 UTC): RSS and Atom feeds are re-enabled.

http://status.twitter.com/post/731461313http://status.twitter.com/post/731461313Thu, 24 Jun 2010 07:19:00 -0700Dealing with high whales (errors) as the result of high load.

Dealing with high whales (errors) as the result of high load. Ops and engineering are responding. Also go #usa!

http://status.twitter.com/post/729248199http://status.twitter.com/post/729248199Wed, 23 Jun 2010 09:19:21 -0700 Periodic high rates of errors on Twitter.com

We’re seeing periodic high rates of errors on Twitter.com.

http://status.twitter.com/post/729182197http://status.twitter.com/post/729182197Wed, 23 Jun 2010 08:15:49 -0700Periodic high rates of errors on Twitter.com

We’re seeing periodic high rates of errors on Twitter.com.

http://status.twitter.com/post/725629754http://status.twitter.com/post/725629754Tue, 22 Jun 2010 08:30:11 -0700High Error Rate on Twitter.com

We’re seeing periodic high rates of errors on Twitter.com.

Update Jun 21 17:42 UTC: The rate of errors has been reduced to a moderate level.

http://status.twitter.com/post/721918879http://status.twitter.com/post/721918879Mon, 21 Jun 2010 06:54:00 -0700Moderate Error Rate on Twitter.com

We’re seeing periodic moderate rates of errors on Twitter.com.

http://status.twitter.com/post/715119716http://status.twitter.com/post/715119716Sat, 19 Jun 2010 07:54:06 -0700Twitter Unavailable

22:20 UTC - 3:20 PDT Twitter is unavailable. Engineering and ops are responding.

22:59 UTC - 4:00 PDT Site is recovering.

http://status.twitter.com/post/709347163http://status.twitter.com/post/709347163Thu, 17 Jun 2010 15:34:00 -0700High Error Rate on Twitter.com

We’re seeing periodic high rates of errors on Twitter.com. This is the result of testing and maintenance. We expect our maintenance to end at approximately @ Wed Jun 16 14:30 UTC

You can read more here.

http://status.twitter.com/post/704452963http://status.twitter.com/post/704452963Wed, 16 Jun 2010 06:23:00 -0700Network Maintenance June 16th @ 13:00-14:30 UTC (6-7:30AM PDT)

MAINTENANCE ACTION:
—————————
We’ll be working with our network provider to perform some tests and maintenance. During this time you can expect a high rate of errors (whales)

DATE/TIME WINDOW:
—————————
June 16th @ 13:00-14:30 UTC (6-7:30AM PDT)

AFFECTED RESOURCES:

———————————

Twitter.com and Api.twitter.com

Update: Wed Jun 16 17:08:12 UTC 2010: We’re extending what is more accurately described as a window of observation. We expect to close this window of observation at 18:00 UTC.

http://status.twitter.com/post/704415654http://status.twitter.com/post/704415654Wed, 16 Jun 2010 06:06:00 -0700Trends have been temporarily disabled

Trends have been temporarily disabled. We’ll re-enable them in approximately in two hours.

Update 2:38PM PDT: Trends have been re-enabled.

http://status.twitter.com/post/701815165http://status.twitter.com/post/701815165Tue, 15 Jun 2010 12:23:00 -0700Temporarily Missing Tweets

Users may temporarily experience missing or duplicate tweets from their timelines. This is the result of the Failed Enhancement of Our Timeline Cache last night.

Normal timelines can restored by repeated refreshing your browser.

http://status.twitter.com/post/701488906http://status.twitter.com/post/701488906Tue, 15 Jun 2010 10:17:20 -0700High Error Rate on Twitter.com

We’re currently experiencing a high rate of errors (whales) on Twitter.com.

Our infrastructure and operations engineers are responding to the incident.

Update 9:22 AM PDT: We’ve temporarily turned off our Twitter Places (Geo) feature to reduce the high rate of errors.

Update 2:39 PDT: Twitter Places has been re-enabled.

Please Note: Users may temporarily experience missing or duplicate tweets from their timelines. Normal timelines can restored by refreshing your browser.

http://status.twitter.com/post/701016717http://status.twitter.com/post/701016717Tue, 15 Jun 2010 06:59:00 -0700Site Availability Issues Due to Failed Enhancement of Our Timeline Cache

Update: We’re currently experiencing site availability issues resulting from the failed enhancement of a new approach to timeline caching. Our infrastructure and operations engineers are currently working to resolve this. We’ll update you soon with an ETA.

Update: 10:17 PM PDT: Users may temporarily experience missing tweets from their timelines. They will be restored shortly.

Update: 11:51 PM PDT: We’re recovering from the site outage. Remember, users may temporarily experience missing or duplicate tweets from their timelines. Normal timelines will be restored shortly.

Update: June 15th 04:11 AM: The site is fully recovered.

Please Note: Users may temporarily experience missing or duplicate tweets from their timelines. Normal timelines can restored by refreshing your browser.

http://status.twitter.com/post/699623494http://status.twitter.com/post/699623494Mon, 14 Jun 2010 20:17:00 -0700