bgpreport

Network · data from 2026-11-12

AS270022 AS270022 - FULLNET SRL

Registry name: AS270022 - FULLNET SRL, AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270022, 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.
191.52.210.0/24 Valid Nonecovered by 191.52.208.0/22 671 100% 67
191.52.211.0/24 Valid Nonecovered by 191.52.208.0/22 671 100% 67
191.52.208.0/24 Valid Nonecovered by 191.52.208.0/22 670 100% 67
191.52.209.0/24 Valid Nonecovered by 191.52.208.0/22 670 100% 67
2803:d9e0:2000::/40 Valid Nonecovered by 2803:d9e0::/32 636 100% 67
2803:d9e0:ffff::/48 Valid Nonecovered by 2803:d9e0::/32 636 100% 67
2803:d9e0:1000::/40 Valid Nonecovered by 2803:d9e0::/32 635 100% 67
179.40.109.0/24 Valid RIR databaseLACNIC 671 100% 67
186.38.56.0/24 Valid RIR databaseLACNIC 671 100% 67
2803:d9e0::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

AS270022 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 8 are in fix.csv.

  • Route object: none7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none191.52.210.0/24No route object for it. A route object for 191.52.208.0/22 with origin AS270022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270022 in the RIR database for the space.671 of 673
Route object: none191.52.211.0/24No route object for it. A route object for 191.52.208.0/22 with origin AS270022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270022 in the RIR database for the space.671 of 673
Route object: none191.52.208.0/24No route object for it. A route object for 191.52.208.0/22 with origin AS270022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270022 in the RIR database for the space.670 of 673
Route object: none191.52.209.0/24No route object for it. A route object for 191.52.208.0/22 with origin AS270022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270022 in the RIR database for the space.670 of 673
Route object: none2803:d9e0:2000::/40No route object for it. A route object for 2803:d9e0::/32 with origin AS270022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270022 in the RIR database for the space.636 of 636
Route object: none2803:d9e0:ffff::/48No route object for it. A route object for 2803:d9e0::/32 with origin AS270022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270022 in the RIR database for the space.636 of 636
Route object: none2803:d9e0:1000::/40No route object for it. A route object for 2803:d9e0::/32 with origin AS270022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270022 in the RIR database for the space.635 of 636

Route objects not announced

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

191.52.208.0/22LACNICValid

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.