Does anybody else have problems with Cloudflare's RPKI Validator with prefixes from LACNIC?
Customers were sending us some reports of issues with LACNIC's IPBlocks using Cloudflare RPKI as source of validation.
A friend and I did some checks. And looks like that some issue is happening on the Lacnic Trust Anchor, specifically on OctoRPKI. We took the Registro.Br Prefix to do the tests -> 200.160.0.0/20 -> AS22548