bgpreport

Network · data from 2026-11-12

AS265342 AS265342 - R DA SILVA SOUSA & CIA LTDA-ME

Registry name: AS265342 - R DA SILVA SOUSA & CIA LTDA-ME, BR · not in PeeringDB

5IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No 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 AS265342, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265342, 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.

168.181.172.0/22 No ROA Other IRR onlyRADB, TC 668 99% 67
168.181.172.0/24 No ROA Other IRR onlyRADB, TC 668 99% 67
168.181.173.0/24 No ROA Other IRR onlyRADB, TC 668 99% 67
168.181.174.0/24 No ROA Other IRR onlyRADB, TC 668 99% 67
2804:2e60::/32 No ROA Other IRR onlyRADB, TC 631 99% 67
168.181.175.0/24 No ROA Other IRR onlyRADB, TC 120 18% 41

AS-SET

AS265342 isn't in PeeringDB, where networks name their 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 14 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none168.181.172.0/22No ROA covers it. Add a ROA for AS265342, maxLength 22.668 of 673
Route object: RIR168.181.172.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none168.181.172.0/24No ROA covers it. Add a ROA for AS265342, maxLength 24.668 of 673
Route object: RIR168.181.172.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none168.181.173.0/24No ROA covers it. Add a ROA for AS265342, maxLength 24.668 of 673
Route object: RIR168.181.173.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none168.181.174.0/24No ROA covers it. Add a ROA for AS265342, maxLength 24.668 of 673
Route object: RIR168.181.174.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:2e60::/32No ROA covers it. Add a ROA for AS265342, maxLength 32.631 of 636
Route object: RIR2804:2e60::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none168.181.175.0/24No ROA covers it. Add a ROA for AS265342, maxLength 24.120 of 673
Route object: RIR168.181.175.0/24Route object only in RADB, TC. Add it in the RIR database for the space.120 of 673

Route objects not announced

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

168.181.172.0/23RADBNo ROA
168.181.174.0/23RADBNo ROA

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.