These entries are queried from radb.net using whois, you can try my project getting these.
:AS52670 route: 170.82.164.0/22 descr: OPCAOTELECOM origin: AS52670 mnt-by: MAINT-AS18678 changed: noc [at] internexa.com 20190417 #13:18:08Z source: RADB last-modified: 2023-11-13T15:56:04Z rpki-ov-state: valid route: 170.82.164.0/22 origin: AS52670 remarks: Auto-created by TC IRR from NIC.br and RIPE RIS data notify: noc [at] digitalprovedor.com.br mnt-by: MAINT-AS52670 source: TC last-modified: 2022-07-18T21:07:09Z rpki-ov-state: valid route: 177.67.184.0/21 descr: OPCAOTELECOM origin: AS52670 mnt-by: MAINT-AS18678 changed: noc [at] internexa.com 20190417 #13:18:08Z source: RADB last-modified: 2023-11-13T15:56:04Z rpki-ov-state: valid route: 177.67.184.0/21 origin: AS52670 remarks: Auto-created by TC IRR from NIC.br and RIPE RIS data notify: noc [at] digitalprovedor.com.br mnt-by: MAINT-AS52670 source: TC last-modified: 2022-07-18T21:07:09Z rpki-ov-state: valid route6: 2804:1120::/32 origin: AS52670 remarks: Auto-created by TC IRR from NIC.br and RIPE RIS data notify: noc [at] digitalprovedor.com.br mnt-by: MAINT-AS52670 source: TC last-modified: 2022-07-18T21:07:10Z rpki-ov-state: valid route6: 2804:1120::/32 origin: AS52670 descr: ITX-OPCAOTELECOM mnt-by: MAINT-AS18678 changed: noc [at] internexa.com 20190417 #13:25:49Z source: RADB last-modified: 2023-11-13T15:56:04Z rpki-ov-state: valid