bgpreport

Network · data from 2026-11-12

AS10405 UPRR-ASN-01 - Union Pacific Railroad Company

Registry name: UPRR-ASN-01 - Union Pacific Railroad Company, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10405, 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.
45.54.128.0/17 No ROA Other IRR onlyRADB 672 100% 67
67.206.0.0/18 No ROA Other IRR onlyRADB 672 100% 67
69.58.192.0/18 No ROA Other IRR onlyRADB 672 100% 67
72.37.0.0/17 No ROA Other IRR onlyRADB 672 100% 67
167.132.0.0/16 No ROA Other IRR onlyRADB 672 100% 67
173.229.128.0/17 No ROA Other IRR onlyRADB 672 100% 67
198.47.128.0/17 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

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

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.54.128.0/17No ROA covers it. Add a ROA for AS10405, maxLength 17.672 of 673
Route object: RIR45.54.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none67.206.0.0/18No ROA covers it. Add a ROA for AS10405, maxLength 18.672 of 673
Route object: RIR67.206.0.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none69.58.192.0/18No ROA covers it. Add a ROA for AS10405, maxLength 18.672 of 673
Route object: RIR69.58.192.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none72.37.0.0/17No ROA covers it. Add a ROA for AS10405, maxLength 17.672 of 673
Route object: RIR72.37.0.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none167.132.0.0/16No ROA covers it. Add a ROA for AS10405, maxLength 16.672 of 673
Route object: RIR167.132.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none173.229.128.0/17No ROA covers it. Add a ROA for AS10405, maxLength 17.672 of 673
Route object: RIR173.229.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none198.47.128.0/17No ROA covers it. Add a ROA for AS10405, maxLength 17.672 of 673
Route object: RIR198.47.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

2620:0:800::/47RADBNo ROA
2620:0:802::/48RADBNo 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.