bgpreport

Network · data from 2026-11-12

AS10662 NORFOLK-SOUTHERN - Norfolk Southern Corporation

Registry name: NORFOLK-SOUTHERN - Norfolk Southern Corporation, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10662, 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.
167.121.65.0/24 No ROA Nonecovered by 167.121.0.0/16 672 100% 67
167.121.0.0/16 No ROA Other IRR onlyRADB 668 99% 67

AS-SET

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

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none167.121.65.0/24No ROA covers it. Add a ROA for AS10662, maxLength 24.672 of 673
Route object: none167.121.65.0/24No route object for it. A route object for 167.121.0.0/16 with origin AS10662 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10662 in the RIR database for the space.672 of 673
ROA: none167.121.0.0/16No ROA covers it. Add a ROA for AS10662, maxLength 16.668 of 673
Route object: RIR167.121.0.0/16Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

198.62.0.0/21ARINValid
2620:d5:8000::/48ARINValid
2620:112:1000::/41ARINValid

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.