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"
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
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.