bgpreport

Network · data from 2026-11-12

AS263105 AS263105 - Plugnet Informatica Ltda

Registry name: AS263105 - Plugnet Informatica Ltda, BR · not in PeeringDB

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

Announced routes

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

179.127.116.0/24 No ROA Nonecovered by 179.127.116.0/22 670 100% 66
179.127.117.0/24 No ROA Nonecovered by 179.127.116.0/22 670 100% 66
179.127.118.0/24 No ROA Nonecovered by 179.127.116.0/22 670 100% 66
179.127.119.0/24 No ROA Nonecovered by 179.127.116.0/22 670 100% 66
2804:16e0::/33 No ROA Nonecovered by 2804:16e0::/32 634 100% 67
2804:16e0:8000::/33 No ROA Nonecovered by 2804:16e0::/32 634 100% 67
179.127.116.0/22 No ROA Other IRR onlyRADB 671 100% 66
2804:16e0::/32 No ROA Other IRR onlyRADB 635 100% 69

AS-SET

AS263105 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none179.127.116.0/24No ROA covers it. Add a ROA for AS263105, maxLength 24.670 of 673
Route object: none179.127.116.0/24No route object for it. A route object for 179.127.116.0/22 with origin AS263105 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263105 in the RIR database for the space.670 of 673
ROA: none179.127.117.0/24No ROA covers it. Add a ROA for AS263105, maxLength 24.670 of 673
Route object: none179.127.117.0/24No route object for it. A route object for 179.127.116.0/22 with origin AS263105 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263105 in the RIR database for the space.670 of 673
ROA: none179.127.118.0/24No ROA covers it. Add a ROA for AS263105, maxLength 24.670 of 673
Route object: none179.127.118.0/24No route object for it. A route object for 179.127.116.0/22 with origin AS263105 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263105 in the RIR database for the space.670 of 673
ROA: none179.127.119.0/24No ROA covers it. Add a ROA for AS263105, maxLength 24.670 of 673
Route object: none179.127.119.0/24No route object for it. A route object for 179.127.116.0/22 with origin AS263105 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263105 in the RIR database for the space.670 of 673
ROA: none2804:16e0::/33No ROA covers it. Add a ROA for AS263105, maxLength 33.634 of 636
Route object: none2804:16e0::/33No route object for it. A route object for 2804:16e0::/32 with origin AS263105 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263105 in the RIR database for the space.634 of 636
ROA: none2804:16e0:8000::/33No ROA covers it. Add a ROA for AS263105, maxLength 33.634 of 636
Route object: none2804:16e0:8000::/33No route object for it. A route object for 2804:16e0::/32 with origin AS263105 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263105 in the RIR database for the space.634 of 636
ROA: none179.127.116.0/22No ROA covers it. Add a ROA for AS263105, maxLength 22.671 of 673
Route object: RIR179.127.116.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:16e0::/32No ROA covers it. Add a ROA for AS263105, maxLength 32.635 of 636
Route object: RIR2804:16e0::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS263105 is announced.

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.