Update to Twitter outbound IP configuration (may affect Cards)



Starting on November 7, 2016, we will be making some changes to our network configurations. As a result, the IP addresses of our network crawlers (i.e. Twitterbot) are changing.

  • The current Twitter outbound IP addresses that developers optionally whitelist for access from our servers or the Cards crawler are listed as,,,,, – these will be retired
  • The new aggregate IP ranges to whitelist will be and

What is the impact?
If you have set up rules to allow access from Twitter’s crawler (i.e. Twitterbot) or otherwise to allow outbound Twitter traffic to access your site or server, and do not make these changes, the crawler may be unable to access your content. This may include being unable to index and render Cards for your content.

For a smooth transition, we request that you add the new aggregate IP ranges to your access controls over the next few weeks, and then retire or remove the older list of IP addresses after this change goes live on November 7, 2016.

If you should have any questions, feel free to post in the Cards category here on twittercommunity.com.

Card not displaying: Failed to fetch page due to: HttpConnectionTimeout
What's IPs of Twitter
Twitter Card Validator Internal Server Error
ERROR: Failed to fetch page due to: DnsResolutionRequestTimeout
Twitter Card summary_large_card not working for some (not all) URLs
Yet Another WARN: No Metatags Found Post
Twitter Card Images suddenly stopped working
A new crawler that is not Twitterbot
Card used to work now doesn't
Help with cards? "Card loaded successfully" but no image preview