Change in cloudfalre.com/ips-v4 API and IP ranges

[r.r.kras]

I have a script that diffs the last set of ips from cloudflare.com/ips-v4 and diff’s this against the previous week. This gives us a heads up if and IP range is added.

It has run fine for a year or so. Today it failed. It appears there is an API change and a possible IP range change.

• First, the API url changed and is now a 301 redirect:
  https://www.cloudflare.com/ips-v4 => https://www.cloudflare.com/ips-v4**/**

• Next, the data returns but the last line no longer ends in a newline

• Third - one of the IP ranges now returned changed.

• 104.24.0.0/14 is now 104.24.0.0/12

The cloudflare.com/ips page has an “updates” section, and neither the IP or the URL change is mentioned.

1. Can someone verify the IP range change, or is this an error in the web site?
   2, Can you add it to the “updates” section to make customers aware of it.
2. Maybe note the api change as well.

[sandro]

The page actually says when it was last updated, which was almost a year ago.

The CIDR you referred to is still /14 and not /12.

As for the redirect, just follow any redirects, but generally neither the URLs nor the addresses have changed.

[michael]

@r.r.kras

First, the API url changed and is now a 301 redirect:

That is not the API. The API is documented here:

https://api.cloudflare.com/#cloudflare-ips-cloudflare-ip-details

[r.r.kras]

yeah - it’s not the API as in ‘Cloudflare API v4’ -

but it’s where cloudflare.com/ips points you to download a (supposedly authoritative list) of IPs used by Cloudflare proxies.

If this should be in a different section then, moderators please locate correctly.

[sandro]

As mentioned, nothing has changed in almost a year.

If you you are concerned about any new lines and can’t handle them in your code, it might be a good idea to use the API instead.