bgpreport

Network · data from 2026-11-12

AS63019 PAROLINK - Parolink.net

Registry name: PAROLINK - Parolink.net, CA · not in PeeringDB

7IPv4 routes 100.0% RPKI valid · 28.6% with a route object
3IPv6 routes 100.0% RPKI valid · 33.3% 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
0Route objects not announced registered with origin AS63019, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS63019, 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.
162.251.192.0/22 Valid Nonecovered by 162.251.192.0/21 673 100% 67
162.251.196.0/22 Valid Nonecovered by 162.251.192.0/21 673 100% 67
162.251.198.0/23 Valid Nonecovered by 162.251.192.0/21 670 100% 67
185.213.68.0/23 Valid Nonecovered by 185.213.68.0/22 670 100% 67
185.213.70.0/23 Valid Nonecovered by 185.213.68.0/22 670 100% 67
2602:ffce:30::/48 Valid Nonecovered by 2602:ffce::/36 636 100% 67
2602:ffce::/37 Valid Nonecovered by 2602:ffce::/36 635 100% 69
162.251.192.0/21 Valid RIR databaseARIN, RADB 672 100% 67
185.213.68.0/22 Valid RIR databaseARIN, RADB 670 100% 67
2602:ffce::/36 Valid RIR databaseARIN, RADB 635 100% 69

AS-SET

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

  • Route object: none7
ChangePrefix or setDetailFull-table peers
Route object: none162.251.192.0/22No route object for it. A route object for 162.251.192.0/21 with origin AS63019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63019 in the RIR database for the space.673 of 673
Route object: none162.251.196.0/22No route object for it. A route object for 162.251.192.0/21 with origin AS63019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63019 in the RIR database for the space.673 of 673
Route object: none162.251.198.0/23No route object for it. A route object for 162.251.192.0/21 with origin AS63019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63019 in the RIR database for the space.670 of 673
Route object: none185.213.68.0/23No route object for it. A route object for 185.213.68.0/22 with origin AS63019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63019 in the RIR database for the space.670 of 673
Route object: none185.213.70.0/23No route object for it. A route object for 185.213.68.0/22 with origin AS63019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63019 in the RIR database for the space.670 of 673
Route object: none2602:ffce:30::/48No route object for it. A route object for 2602:ffce::/36 with origin AS63019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63019 in the RIR database for the space.636 of 636
Route object: none2602:ffce::/37No route object for it. A route object for 2602:ffce::/36 with origin AS63019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63019 in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS63019 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.