bgpreport

Network · data from 2026-11-12

AS3389 Ford Motor Company

Registry name: FORDSRL-AS - Ford Motor Company, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3389, 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.
2620:0:402::/48 No ROA Nonecovered by 2620:0:400::/40 635 100% 67
2620:0:403::/48 No ROA Nonecovered by 2620:0:400::/40 635 100% 67
128.5.0.0/20 No ROA Nonecovered by 128.5.0.0/16 3 0%low visibility 3
19.12.72.0/21 No ROA Other IRR onlyRADB 672 100% 67
19.12.88.0/21 No ROA Other IRR onlyRADB 672 100% 67
19.12.128.0/21 No ROA Other IRR onlyRADB 672 100% 67
19.12.136.0/21 No ROA Other IRR onlyRADB 672 100% 67
19.12.96.0/20 No ROA Other IRR onlyRADB 669 99% 67
19.12.112.0/20 No ROA Other IRR onlyRADB 669 99% 67

AS-SET

AS3389's PeeringDB record names no 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 22 are in fix.csv.

  • ROA: none9
  • Route object: none3
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2620:0:402::/48No ROA covers it. Add a ROA for AS3389, maxLength 48.635 of 636
Route object: none2620:0:402::/48No route object for it. A route object for 2620:0:400::/40 with origin AS3389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3389 in the RIR database for the space.635 of 636
ROA: none2620:0:403::/48No ROA covers it. Add a ROA for AS3389, maxLength 48.635 of 636
Route object: none2620:0:403::/48No route object for it. A route object for 2620:0:400::/40 with origin AS3389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3389 in the RIR database for the space.635 of 636
ROA: none128.5.0.0/20No ROA covers it. Add a ROA for AS3389, maxLength 20.3 of 673
Route object: none128.5.0.0/20No route object for it. A route object for 128.5.0.0/16 with origin AS3389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3389 in the RIR database for the space.3 of 673
ROA: none19.12.72.0/21No ROA covers it. Add a ROA for AS3389, maxLength 21.672 of 673
Route object: RIR19.12.72.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none19.12.88.0/21No ROA covers it. Add a ROA for AS3389, maxLength 21.672 of 673
Route object: RIR19.12.88.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none19.12.128.0/21No ROA covers it. Add a ROA for AS3389, maxLength 21.672 of 673
Route object: RIR19.12.128.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none19.12.136.0/21No ROA covers it. Add a ROA for AS3389, maxLength 21.672 of 673
Route object: RIR19.12.136.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none19.12.96.0/20No ROA covers it. Add a ROA for AS3389, maxLength 20.669 of 673
Route object: RIR19.12.96.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none19.12.112.0/20No ROA covers it. Add a ROA for AS3389, maxLength 20.669 of 673
Route object: RIR19.12.112.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

19.0.0.0/8RADBNo ROA
128.5.0.0/16RADBNo ROA
2620:0:400::/40RADBNo ROA
2620:0:400::/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.