Networks of Cloudflare are being marked as anycast through the override of AS13335 (override-a3.txt), so only if they are being announced by AS13335. Of the 22 ranges that Cloudflare publishes (https://www.cloudflare.com/ips-v4 and ips-v6), 9 are not marked as anycast in the database of 2026-10-17, because they are being announced by other ASes of Cloudflare (141.101.64.0/18 by AS202623, 198.41.128.0/17 by AS395747), or because there is no announcement in the database at all (172.64.0.0/13, 173.245.48.0/20, 103.21.244.0/22, 2400:cb00::/32, 2803:f800::/32, 2405:8100::/32, 2a06:98c0::/29). The ranges could be imported like those of AWS, and marked as anycast.
https://git.ipfire.org/?p=location/libloc.git;a=commit;h=f6334e39d36648963d4ce5dc35748977d333220a Author: Michael Tremer <michael.tremer@ipfire.org> man: location-importer imports the IP ranges of Cloudflare Fixes: #14506 - Some IP ranges of Cloudflare are not being marked as anycast Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
This has been implemented in the master branch of libloc (03267db, f6334e3). "location-importer update-feeds" imports the IP ranges of Cloudflare as CLOUDFLARE-IPV4 and CLOUDFLARE-IPV6, and marks all of them as anycast. In a test database, all 22 ranges are marked as anycast now, including 172.64.0.0/13, 141.101.64.0/18 and 198.41.128.0/17. The ranges of Fastly (https://api.fastly.com/public-ip-list) have not been added, because Fastly says that the list has all of its IP ranges, including those that it connects to origins from, which are not necessarily anycast. This will be in the database once the importer with this change has been running.
http://git.ipfire.org/?p=location/libloc.git;a=commit;h=03267dba21c9cd1d310ce40c875a53fa21538329 Author: Michael Tremer <michael.tremer@ipfire.org> importer: Import the IP ranges of Cloudflare as anycast Networks of Cloudflare have only been marked as anycast if they were being announced by AS13335, which overrides mark as anycast. 9 of the 22 ranges that Cloudflare publishes were not, because other ASes of Cloudflare announce them, or because we have not seen them announced. They are now being imported with "update-feeds", and all of them are marked as anycast. Fixes: #14506 - Some IP ranges of Cloudflare are not being marked as anycast Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
http://git.ipfire.org/?p=location/libloc.git;a=commit;h=f6334e39d36648963d4ce5dc35748977d333220a Author: Michael Tremer <michael.tremer@ipfire.org> man: location-importer imports the IP ranges of Cloudflare Fixes: #14506 - Some IP ranges of Cloudflare are not being marked as anycast Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
https://git.ipfire.org/?p=location/libloc.git;a=commit;h=03267dba21c9cd1d310ce40c875a53fa21538329 Author: Michael Tremer <michael.tremer@ipfire.org> importer: Import the IP ranges of Cloudflare as anycast Networks of Cloudflare have only been marked as anycast if they were being announced by AS13335, which overrides mark as anycast. 9 of the 22 ranges that Cloudflare publishes were not, because other ASes of Cloudflare announce them, or because we have not seen them announced. They are now being imported with "update-feeds", and all of them are marked as anycast. Fixes: #14506 - Some IP ranges of Cloudflare are not being marked as anycast Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
This has been fixed in libloc 0.9.20, which has just been tagged. Closing this as fixed.