From the CAIDA study on this: "In October 2021, we found matching Route Origin Authorization objects (ROAs) for around 20% of RADB IRR records, and a consistency of 38% and 60% in v4 and v6." Do think much has improved here. 

On Wed, Jul 10, 2024 at 10:52 PM Job Snijders via NANOG <nanog@nanog.org> wrote:
On Wed, Jul 10, 2024 at 07:10:48PM -0400, Aliaksei Sheshka wrote:
> nothing!  I suspect the mirror is out of sync.
>
> Now NTT mirror:

Seems reloading helped:

$ date
Thu Jul 11 03:50:22 UTC 2024

$ whois -h rr.ntt.net 199.52.73.0/24
route:          199.52.73.0/24
origin:         AS132055
descr:          EY India
admin-c:        IAM12-ARIN
tech-c:         DNSAD85-ARIN
tech-c:         IAM12-ARIN
mnt-by:         MNT-EYL-Z
created:        2022-10-19T08:37:50Z
last-modified:  2023-11-27T15:10:44Z
source:         ARIN
rpki-ov-state:  valid


route:          199.52.73.0/24
descr:          RPKI ROA for 199.52.73.0/24 / AS132055
remarks:        This AS132055 route object represents routing data retrieved
                from the RPKI. This route object is the result of an automated
                RPKI-to-IRR conversion process performed by IRRd.
max-length:     24
origin:         AS132055
source:         RPKI  # Trust Anchor: arin