October 2008
15 posts
Search unreachable from Sprint
search.twitter.com is unreachable from internet connections routed through Sprint/Nextel, as per the unfortunate news
Update: this has been corrected
Intermittent network failures
In the past 2 hours, we’ve experienced 2 periods of network issues as we installed new networking hardware.
These periods lasted approximately 3 minutes each. We do not expect any further issues.
Update on latency (fixed)
Monday and Tuesday of this week we have had connection problems to twitter.com between 0730 and 1400 PDT. Some users were seeing timeouts in their browsers on a regular basis through these periods.
We discovered the source of problem this evening and have fixed it.
For the technically inclined: It had to do with a limit set in our load balancer. We crossed a threshold of traffic that caused it...
Occasional Timeouts
We’re currently diagnosing some network latency that is resulting in occasional timeouts and site slowness for some folks.
Friday Bug Fixed
The bug reported on Friday about folks being able to see some protected updates by viewing XML source was fixed on Friday. If you protect your updates, only people you approve will receive them.
Search behind realtime
Twitter search is minutes behind realtime. We are working to resolve this.
Update: this has been resolved
User search disabled
We have temporarily turned off user search because of a problem affecting overall site performance. It will be re-enabled once we’ve solved the underlying problem.
Direct Message delivery problems
Direct Messages are not currently being delivered via SMS. You can still see any direct messages sent to you on the web or via email (if you elect to receive DMs that way).
We hope to resolve this problem quickly.
500 Errors in the API
API clients were seeing a higher than normal number of 500 errors this morning. We’re tracking down the problem and believe it is now resolved. More investigation is ongoing…
Email Delivery/Password Recovery Problems
All email from Twitter is currently being blocked by users with email accounts on AT&T, SBC or BellSouth. If your email account is with one of these providers, you will not receive mail from us and, therefore, will not be able to recover your password.
We are working with these ISPs to resolve the problem. In the meantime, if 1) your email account is with AT&T, SBC or BellSouth and 2) you...
IM: Not coming soon
In October 2006, just three months after Twitter launched publicly, we added IM support—i.e., the ability to get and send tweets via XMPP/Jabber/Google Talk. I was a big fan of this feature, because this interface, which millions of people were already familiar with, seemed a perfect fit for Twitter’s real-time nature.
In December of 2006, we extended that support to AIM, enabling a much...
Maintenance window tonight
We will have a 30 minute downtime tonight at 10p Pacific to perform system maintenance.
Search lost its style
We’re working on an issue with search not serving its formatting correctly, resulting in some funky looking results.
Update: This has been fixed.
Some delivery problems over SMS
In the past hour, some users will not have received all messages they should have via SMS. This includes the delivery of direct messages. All updates and DMs will be viewable on the web or over the API. This problem should be resolved in the next hour or so.
Fixed problem with API method
Yesterday we were throwing 500 errors on API requests to /users/show. This has now been fixed.
