bgpreport

Network · data from 2026-11-12

AS20474 NCI Data.com

Registry name: NCIDATACOM - NCI Data.com, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20474, 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.
38.94.120.0/21 No ROA Other IRR onlyRADB 2 0%low visibility 2
64.139.96.0/20 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.96.0/21 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.96.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.98.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.100.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.102.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.104.0/21 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.104.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.106.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.108.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.110.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.112.0/20 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.112.0/21 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.112.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.114.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.116.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.118.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.120.0/21 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.120.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.122.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
64.139.124.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS20474: AS-NCIDATACOM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS20474 isn't in the set, or no route object for AS20474 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS20474 in itNot covered
AS-NCIDATACOM In no IRR database read today.

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

  • ROA: none1
  • Route object: RIR22
  • AS-SET: not found1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none38.94.120.0/21No ROA covers it. Add a ROA for AS20474, maxLength 21.2 of 673
Route object: RIR38.94.120.0/21Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.96.0/20Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.96.0/21Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.96.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.98.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.100.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.102.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.104.0/21Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.104.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.106.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.108.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.110.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.112.0/20Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.112.0/21Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.112.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.114.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.116.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.118.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.120.0/21Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.120.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.122.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR64.139.124.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
AS-SET: not foundAS-NCIDATACOMPeeringDB names AS-NCIDATACOM; no IRR database read has it.

Route objects not announced

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

64.139.96.0/19ARIN, RADBValid
64.139.105.0/24RADBValid
64.139.108.0/24RADBValid

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.