CloudFlare Client API is currently returning 500 error

Developers API
1

The China colo request is throwing 500s:

$ curl -fsSL https://api.cloudflare.com/client/v4/ips?china_colo=1
curl: (22) The requested URL returned error: 500

It has been throwing 500s for about 45 minutes.

The regular IP list is not throwing 500s:

$ curl -fsSL https://api.cloudflare.com/client/v4/ips
{"result":{"ipv4_cidrs":["173.245.48.0\/20","103.21.244.0\/22","103.22.200.0\/22","103.31.4.0\/22","141.101.64.0\/18","108.162.192.0\/18","190.93.240.0\/20","
188.114.96.0\/20","197.234.240.0\/22","198.41.128.0\/17","162.158.0.0\/15","104.16.0.0\/13","104.24.0.0\/14","172.64.0.0\/13","131.0.72.0\/22"],"ipv6_cidrs":[
"2400:cb00::\/32","2606:4700::\/32","2803:f800::\/32","2405:b500::\/32","2405:8100::\/32","2a06:98c0::\/29","2c0f:f248::\/32"],"etag":"38f79d050aa027e3be3865e
495dcc9bc"},"success":true,"errors":[],"messages":[]}
2

I would like to request that in the future, rather than throwing errors, a best effort should be made to return the last successful results. We query these ranges to update security groups, and when the call fails, our automation to update security groups fails. We would rather not have to build in caching to our own solution, so if the API can handle that for us, that would be greatly appreciated.

3

This has also broken the Cloudflare Go library which has in turn broken the Terraform Cloudflare provider when using the cloudflare_ip_ranges data resource.

4

Hooray, it’s fixed Cloudflare Status - Cloudflare IPs API endpoint errors

5

Thanks for the update @user15569 .

Hopefully one of the devs reads this eventually… :slight_smile: I wonder if there’s an official way to report services being down?