bgpreport

Network · data from 2026-11-12

AS61862 Prove Net

Registry name: AS61862 - PROVEDOR DE INTERNET DE ANAPU LTDA - ME, BR · PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS61862, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61862, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
138.185.172.0/22 Valid Other IRR onlyRADB 673 100% 66
138.185.172.0/24 Valid Other IRR onlyRADB 673 100% 66
138.185.175.0/24 Valid Other IRR onlyRADB 673 100% 66
201.150.120.0/22 Valid Other IRR onlyALTDB, RADB 673 100% 66
138.185.173.0/24 Valid Other IRR onlyRADB 672 100% 66
138.185.174.0/24 Valid Other IRR onlyRADB 672 100% 66
138.185.172.0/23 Valid Other IRR onlyRADB 667 99% 67
138.185.174.0/23 Valid Other IRR onlyRADB 667 99% 67
201.150.120.0/23 Valid Other IRR onlyRADB 667 99% 67
201.150.122.0/23 Valid Other IRR onlyRADB 667 99% 67
2804:1a7c::/32 Valid Other IRR onlyRADB 635 100% 69
2804:1a7c::/33 Valid Other IRR onlyRADB 635 100% 69
2804:1a7c:8000::/33 Valid Other IRR onlyRADB 635 100% 69

AS-SET

AS61862's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 15 are in fix.csv.

  • Route object: RIR13
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR138.185.172.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR138.185.172.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR138.185.175.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR201.150.120.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR138.185.173.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.185.174.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.185.172.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR138.185.174.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR201.150.120.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR201.150.122.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:1a7c::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1a7c::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1a7c:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Route objects with origin AS61862 whose prefix no peer sees AS61862 announce. Many are kept on purpose (backup routes, space announced only in some places).

201.150.120.0/24RADBValid
201.150.123.0/24RADBValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.