Network · data from 2026-11-12
AS14017 BNSF-AS - Burlington Northern Sante Fe Railway Corp
Registry name: BNSF-AS - Burlington Northern Sante Fe Railway Corp, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14017, 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.
| 170.49.0.0/16 | No ROA | None | 673 100% |
| 139.51.1.0/24 | No ROA | Nonecovered by 139.51.0.0/16 | 672 100% |
| 139.51.4.0/24 | No ROA | Nonecovered by 139.51.0.0/16 | 672 100% |
| 139.51.12.0/24 | No ROA | Nonecovered by 139.51.0.0/16 | 672 100% |
| 139.51.13.0/24 | No ROA | Nonecovered by 139.51.0.0/16 | 672 100% |
| 139.51.14.0/24 | No ROA | Nonecovered by 139.51.0.0/16 | 672 100% |
| 170.49.4.0/24 | No ROA | None | 2 0%low visibility |
| 170.49.8.0/24 | No ROA | None | 2 0%low visibility |
| 139.51.0.0/16 | No ROA | Other IRR onlyRADB | 673 100% |
| 170.49.66.0/24 | No ROA | Other IRR onlyALTDB | 2 0%low visibility |
| 170.49.84.0/24 | No ROA | Other IRR onlyALTDB | 2 0%low visibility |
| 170.49.114.0/24 | No ROA | Other IRR onlyALTDB | 2 0%low visibility |
| 170.49.116.0/23 | No ROA | Other IRR onlyALTDB | 2 0%low visibility |
AS-SET
AS14017 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 42 are in fix.csv.
- ROA: none13
- Route object: none8
- Route object: RIR5
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 170.49.0.0/16 | No ROA covers it. Add a ROA for AS14017, maxLength 16. |
| Route object: none | 170.49.0.0/16 | No route object for it. Add a route object with origin AS14017 in the RIR database for the space. |
| ROA: none | 139.51.1.0/24 | No ROA covers it. Add a ROA for AS14017, maxLength 24. |
| Route object: none | 139.51.1.0/24 | No route object for it. A route object for 139.51.0.0/16 with origin AS14017 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14017 in the RIR database for the space. |
| ROA: none | 139.51.4.0/24 | No ROA covers it. Add a ROA for AS14017, maxLength 24. |
| Route object: none | 139.51.4.0/24 | No route object for it. A route object for 139.51.0.0/16 with origin AS14017 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14017 in the RIR database for the space. |
| ROA: none | 139.51.12.0/24 | No ROA covers it. Add a ROA for AS14017, maxLength 24. |
| Route object: none | 139.51.12.0/24 | No route object for it. A route object for 139.51.0.0/16 with origin AS14017 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14017 in the RIR database for the space. |
| ROA: none | 139.51.13.0/24 | No ROA covers it. Add a ROA for AS14017, maxLength 24. |
| Route object: none | 139.51.13.0/24 | No route object for it. A route object for 139.51.0.0/16 with origin AS14017 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14017 in the RIR database for the space. |
| ROA: none | 139.51.14.0/24 | No ROA covers it. Add a ROA for AS14017, maxLength 24. |
| Route object: none | 139.51.14.0/24 | No route object for it. A route object for 139.51.0.0/16 with origin AS14017 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14017 in the RIR database for the space. |
| ROA: none | 170.49.4.0/24 | No ROA covers it. Add a ROA for AS14017, maxLength 24. |
| Route object: none | 170.49.4.0/24 | No route object for it. Add a route object with origin AS14017 in the RIR database for the space. |
| ROA: none | 170.49.8.0/24 | No ROA covers it. Add a ROA for AS14017, maxLength 24. |
| Route object: none | 170.49.8.0/24 | No route object for it. Add a route object with origin AS14017 in the RIR database for the space. |
| ROA: none | 139.51.0.0/16 | No ROA covers it. Add a ROA for AS14017, maxLength 16. |
| Route object: RIR | 139.51.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 170.49.66.0/24 | No ROA covers it. Add a ROA for AS14017, maxLength 24. |
| Route object: RIR | 170.49.66.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 170.49.84.0/24 | No ROA covers it. Add a ROA for AS14017, maxLength 24. |
| Route object: RIR | 170.49.84.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 170.49.114.0/24 | No ROA covers it. Add a ROA for AS14017, maxLength 24. |
| Route object: RIR | 170.49.114.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 170.49.116.0/23 | No ROA covers it. Add a ROA for AS14017, maxLength 23. |
| Route object: RIR | 170.49.116.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14017 whose prefix no peer sees AS14017 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 139.51.254.0/24 | ALTDB | No ROA |
| 170.49.0.0/24 | ALTDB | No ROA |
| 170.49.5.0/24 | ALTDB | No ROA |
| 170.49.7.0/24 | ALTDB | No ROA |
| 170.49.9.0/24 | ALTDB | No ROA |
| 170.49.10.0/24 | ALTDB | No ROA |
| 170.49.12.0/24 | ALTDB | No ROA |
| 170.49.13.0/24 | ALTDB | No ROA |
| 170.49.14.0/24 | ALTDB | No ROA |
| 170.49.15.0/24 | ALTDB | No ROA |
| 170.49.49.0/24 | ALTDB | No ROA |
| 170.49.112.0/23 | ALTDB | No ROA |
| 170.49.112.0/24 | ALTDB | No ROA |
| 170.49.126.0/24 | ALTDB | No ROA |
| 170.49.153.0/24 | ALTDB | No ROA |
| 170.49.254.0/24 | ALTDB | No 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.