bgpreport

Network · data from 2026-11-12

AS14634 SPINNNET - SpinnNet

Registry name: SPINNNET - SpinnNet, US · not in PeeringDB

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

Announced routes

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

67.22.178.0/24 Valid Nonecovered by 67.22.176.0/20 673 100% 67
67.22.187.0/24 Valid Nonecovered by 67.22.176.0/20 673 100% 67
67.22.183.0/24 Valid Other IRR onlyRADB 671 100% 68
216.223.229.0/24 Valid Other IRR onlyRADB 671 100% 68
216.223.231.0/24 Valid Other IRR onlyRADB 671 100% 68
216.223.232.0/24 Valid Other IRR onlyRADB 671 100% 68
216.223.237.0/24 Valid Other IRR onlyRADB 671 100% 68
216.223.238.0/24 Valid Other IRR onlyRADB 671 100% 68
67.22.176.0/20 Valid RIR databaseALTDB, ARIN, RADB 671 100% 68
216.223.224.0/20 Valid RIR databaseALTDB, ARIN, RADB 671 100% 68

AS-SET

AS14634 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: none2
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none67.22.178.0/24No route object for it. A route object for 67.22.176.0/20 with origin AS14634 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14634 in the RIR database for the space.673 of 673
Route object: none67.22.187.0/24No route object for it. A route object for 67.22.176.0/20 with origin AS14634 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14634 in the RIR database for the space.673 of 673
Route object: RIR67.22.183.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR216.223.229.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR216.223.231.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR216.223.232.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR216.223.237.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR216.223.238.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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