Hi all, I'd just like to add that if you can also provide HTTP request/response headers and/or packet captures/dumps of actual API requests, that would be really really helpful in troubleshooting specific situations. Any patterns we can see emerging from this data will help us debug even faster.
Thanks, -Chad On Mon, Aug 17, 2009 at 7:41 PM, Ryan Sarver<rsar...@twitter.com> wrote: > > I wanted to email the list and update everyone on the current status > of the platform. Over the past ten days we have been dealing with a > lot of stress on our network and that has caused a number of our > partners to be knocked offline for extended periods of time. This is > obviously not something we want to happen and the platform and ops > teams have been working hard throughout that time to address the needs > of our ecosystem while protecting the system as a whole. We have made > some great progress today in tuning the system to a point that should > allow our partners to operate as they were before the recent issue > began. > > However, the system is still under stress so we will need to keep an > eye on the platform and make sure everyone is operational. If you were > experiencing issues over the weekend and into today, please recheck > the issues to see if they have been resolved. If you are still > experiencing problems, please provide the requested details to help us > debug your specific problem. If you don't provide at least some of the > additional information we will not be able to help you - so please do > some leg work and help us help you: > > 1. The IP of the machine making requests to the Twitter API. If you're > behind NAT, please be sure to send us your *external* IP. > 2. The IP address of the machine you're contacting in the Twitter > cluster. You can find this on UNIX machines via the "host" or > "nslookup" commands, and on Windows machines via the "nslookup" > command. > 3. The Twitter API URL (method) you're requesting and any other > details about the request (GET vs. POST, parameters, headers, etc.). > 4. Your host operating system, browser (including version), relevant > cookies, and any other pertinent information about your environment. > 5. What kind of network connection you have and from which provider, > and what kind of network connectivity devices you're using. > > We will continue to monitor the situation and the mailing list for any > new issues. We appreciate your patience and your support in helping us > get through the situation. Thank you to all the developers who > provided us with information to help us tune the system and get > everyone back online. > > Thanks again, Ryan > @rsarver >