Hey everyone, We recently updated the IPs our DNS addresses resolve to. Usually this is a transparent change that requires no action from you but we've noticed a number of requests are going to the old IPs.
This is most commonly caused by some code which resolves the IP of our DNS connection at startup and then keeps it until the service is completely restarted. We often change our IPs for load balancing and network performance reasons so it is really important that you use the DNS address when talking to the API. Our DNS entries also have a very short lifetime (30 seconds) so you want to make sure you refresh the DNS cache regularly. To know the currently configured IPs for our DNS you can use the command line tool dig. For example: dig +nocmd api.twitter.com +noall +answer api.twitter.com. 27 IN A 199.59.148.87 api.twitter.com. 27 IN A 199.59.148.20 api.twitter.com. 27 IN A 199.59.149.200 api.twitter.com. 27 IN A 199.59.149.232 If your service is communicating with the API on any other IPs please update your DNS cache and reconnect. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
