bgpreport

Network · data from 2026-11-12

AS21623 I2B Networks as21623

Registry name: SPACELINK - Spacelink Systems, US · PeeringDB

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

Announced routes

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

66.181.22.0/24 No ROA Nonecovered by 66.181.0.0/19 673 100% 67
2604:3200:3e8::/48 No ROA Nonecovered by 2604:3200::/32 1 0%low visibility 1
38.96.21.0/24 No ROA Other IRR onlyRADB 672 100% 67
65.50.224.0/19 No ROA RIR databaseARIN, RADB 673 100% 67
66.181.0.0/19 No ROA RIR databaseARIN, RADB 673 100% 67
2604:3200::/32 No ROA RIR databaseARIN, RADB 634 100% 68

AS-SET

AS21623's PeeringDB record names no 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 15 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none66.181.22.0/24No ROA covers it. Add a ROA for AS21623, maxLength 24.673 of 673
Route object: none66.181.22.0/24No route object for it. A route object for 66.181.0.0/19 with origin AS21623 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21623 in the RIR database for the space.673 of 673
ROA: none2604:3200:3e8::/48No ROA covers it. Add a ROA for AS21623, maxLength 48.1 of 636
Route object: none2604:3200:3e8::/48No route object for it. A route object for 2604:3200::/32 with origin AS21623 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21623 in the RIR database for the space.1 of 636
ROA: none38.96.21.0/24No ROA covers it. Add a ROA for AS21623, maxLength 24.672 of 673
Route object: RIR38.96.21.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none65.50.224.0/19No ROA covers it. Add a ROA for AS21623, maxLength 19.673 of 673
ROA: none66.181.0.0/19No ROA covers it. Add a ROA for AS21623, maxLength 19.673 of 673
ROA: none2604:3200::/32No ROA covers it. Add a ROA for AS21623, maxLength 32.634 of 636

Route objects not announced

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

69.55.229.0/24RADBNo ROA
69.55.231.0/24RADBNo ROA
192.58.123.0/24RADBNo ROA
192.58.222.0/24RADBNo ROA
209.177.67.0/24RADBNo ROA
2606:a0c0::/32ARINNo 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.