There is one change we need to do to our objects though: we have IRR objects for the US space in the RIPE DB (e.g. whois -h whois.ripe.net 220.127.116.11/23), and this has been deprecated over the past year: https://www.ripe.net/publications/news/announcements/changes-to-out-of-region-objects-in-the-ripe-database
We need to move these out to the ARIN IRR, so that needs some work...
From the RIPE ARC (Assisted Registry Check):
We found that the prefixes 18.104.22.168/22 and 2a02:ec80::/29 are in use but not documented in the RIPE Database as assignments.
You will need to create assignments (inetnum/inet6num) in the RIPE Database in order to conform with RIPE policy. The usage of IPv6 for this account must be documented in the RIPE Database as assignments (maximum of /48), sub-allocations or aggregations.
From the NLNOG IRR explorer: