bgpreport

Network · data from 2026-11-12

AS63483 SKYNET-AS-1 - Skynet

Registry name: SKYNET-AS-1 - Skynet, US · not in PeeringDB

38IPv4 routes 97.4% RPKI valid · 34.2% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 25 with no route object for this origin
12Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS63483, seen from no peer

Announced routes

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

50.59.82.0/24 No ROA Nonecovered by 50.59.82.0/23 2 0%low visibility 2
168.235.160.0/24 Valid Nonecovered by 168.235.160.0/20 673 100% 67
168.235.161.0/24 Valid Nonecovered by 168.235.160.0/20 673 100% 67
168.235.162.0/24 Valid Nonecovered by 168.235.160.0/20 673 100% 67
168.235.165.0/24 Valid Nonecovered by 168.235.160.0/20 673 100% 67
168.235.166.0/24 Valid Nonecovered by 168.235.160.0/20 673 100% 67
168.235.168.0/24 Valid Nonecovered by 168.235.160.0/20 673 100% 67
168.235.175.0/24 Valid Nonecovered by 168.235.160.0/20 673 100% 67
168.235.170.0/24 Valid Nonecovered by 168.235.160.0/20 672 100% 67
168.235.163.0/24 Valid Nonecovered by 168.235.160.0/20 671 100% 67
168.235.164.0/24 Valid Nonecovered by 168.235.160.0/20 671 100% 67
168.235.169.0/24 Valid Nonecovered by 168.235.160.0/20 671 100% 67
168.235.171.0/24 Valid Nonecovered by 168.235.160.0/20 671 100% 67
168.235.172.0/24 Valid Nonecovered by 168.235.160.0/20 671 100% 67
168.235.173.0/24 Valid Nonecovered by 168.235.160.0/20 671 100% 67
168.235.174.0/24 Valid Nonecovered by 168.235.160.0/20 671 100% 67
168.235.167.0/24 Valid Nonecovered by 168.235.160.0/20 670 100% 67
50.217.136.0/24 Valid None 2 0%low visibility 2
50.217.137.0/24 Valid None 2 0%low visibility 2
50.217.139.0/24 Valid None 2 0%low visibility 2
50.238.32.0/24 Valid None 2 0%low visibility 2
50.238.34.0/24 Valid None 2 0%low visibility 2
50.238.35.0/24 Valid None 2 0%low visibility 2
50.238.37.0/24 Valid None 2 0%low visibility 2
50.238.39.0/24 Valid None 2 0%low visibility 2
50.217.140.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
50.217.141.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
50.238.36.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
167.88.218.0/24 Valid RIR databaseARIN, RADB 673 100% 67
167.88.216.0/24 Valid RIR databaseARIN, RADB 672 100% 67
50.20.193.0/24 Valid RIR databaseARIN, RADB 671 100% 67
167.88.213.0/24 Valid RIR databaseARIN, RADB 671 100% 67
167.88.214.0/24 Valid RIR databaseARIN, RADB 671 100% 67
167.88.215.0/24 Valid RIR databaseARIN, RADB 671 100% 67
167.88.217.0/24 Valid RIR databaseARIN, RADB 671 100% 67
167.88.219.0/24 Valid RIR databaseARIN, RADB 671 100% 67
167.88.220.0/24 Valid RIR databaseARIN, RADB 671 100% 67
167.88.221.0/24 Valid RIR databaseARIN, RADB 671 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none25
  • Route object: RIR3
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none50.59.82.0/24No ROA covers it. Add a ROA for AS63483, maxLength 24.2 of 673
Route object: none50.59.82.0/24No route object for it. A route object for 50.59.82.0/23 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.2 of 673
Route object: none168.235.160.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.673 of 673
Route object: none168.235.161.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.673 of 673
Route object: none168.235.162.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.673 of 673
Route object: none168.235.165.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.673 of 673
Route object: none168.235.166.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.673 of 673
Route object: none168.235.168.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.673 of 673
Route object: none168.235.175.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.673 of 673
Route object: none168.235.170.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.672 of 673
Route object: none168.235.163.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.671 of 673
Route object: none168.235.164.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.671 of 673
Route object: none168.235.169.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.671 of 673
Route object: none168.235.171.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.671 of 673
Route object: none168.235.172.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.671 of 673
Route object: none168.235.173.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.671 of 673
Route object: none168.235.174.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.671 of 673
Route object: none168.235.167.0/24No route object for it. A route object for 168.235.160.0/20 with origin AS63483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63483 in the RIR database for the space.670 of 673
Route object: none50.217.136.0/24No route object for it. Add a route object with origin AS63483 in the RIR database for the space.2 of 673
Route object: none50.217.137.0/24No route object for it. Add a route object with origin AS63483 in the RIR database for the space.2 of 673
Route object: none50.217.139.0/24No route object for it. Add a route object with origin AS63483 in the RIR database for the space.2 of 673
Route object: none50.238.32.0/24No route object for it. Add a route object with origin AS63483 in the RIR database for the space.2 of 673
Route object: none50.238.34.0/24No route object for it. Add a route object with origin AS63483 in the RIR database for the space.2 of 673
Route object: none50.238.35.0/24No route object for it. Add a route object with origin AS63483 in the RIR database for the space.2 of 673
Route object: none50.238.37.0/24No route object for it. Add a route object with origin AS63483 in the RIR database for the space.2 of 673
Route object: none50.238.39.0/24No route object for it. Add a route object with origin AS63483 in the RIR database for the space.2 of 673
Route object: RIR50.217.140.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR50.217.141.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR50.238.36.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

50.59.82.0/23RADBNo ROA
50.217.142.0/24RADBValid
50.217.143.0/24RADBValid
168.235.160.0/20ARIN, RADBValid
2606:f680::/32RADBNo 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.