bgpreport

Network · data from 2026-11-12

AS10493 GCN-AS - Grand Central Networks Inc.

Registry name: GCN-AS - Grand Central Networks Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10493, 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.
172.81.88.0/24 No ROA Other IRR onlyRADB 672 100% 67
172.81.89.0/24 No ROA Other IRR onlyRADB 672 100% 67
172.81.90.0/24 No ROA Other IRR onlyRADB 672 100% 67
172.81.91.0/24 No ROA Other IRR onlyRADB 672 100% 67
74.201.43.0/24 No ROA Other IRR onlyRADB 671 100% 67
50.31.163.0/24 No ROA RIR databaseARIN 672 100% 67

AS-SET

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

  • ROA: none6
  • Route object: RIR5
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none172.81.88.0/24No ROA covers it. Add a ROA for AS10493, maxLength 24.672 of 673
Route object: RIR172.81.88.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none172.81.89.0/24No ROA covers it. Add a ROA for AS10493, maxLength 24.672 of 673
Route object: RIR172.81.89.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none172.81.90.0/24No ROA covers it. Add a ROA for AS10493, maxLength 24.672 of 673
Route object: RIR172.81.90.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none172.81.91.0/24No ROA covers it. Add a ROA for AS10493, maxLength 24.672 of 673
Route object: RIR172.81.91.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none74.201.43.0/24No ROA covers it. Add a ROA for AS10493, maxLength 24.671 of 673
Route object: RIR74.201.43.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none50.31.163.0/24No ROA covers it. Add a ROA for AS10493, maxLength 24.672 of 673

Route objects not announced

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

66.150.106.0/24RADBNo ROA
74.201.36.0/23RADBNo ROA
74.201.36.0/24RADBNo ROA
74.201.37.0/24RADBNo ROA
74.201.38.0/23RADBNo ROA
74.201.38.0/24RADBNo ROA
74.201.39.0/24RADBNo ROA
74.201.40.0/23RADBNo ROA
74.201.40.0/24RADBNo ROA
74.201.41.0/24RADBNo ROA
74.201.42.0/23RADBNo ROA
74.201.42.0/24RADBNo ROA
172.81.88.0/22ALTDB, RADBNo 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.