Network · data from 2026-11-12

AS100 FMC Central Engineering Laboratories

Registry name: FMC-CTC - FMC Central Engineering Laboratories, US · PeeringDB

5IPv4 routes 0.0% RPKI valid · 0.0% with a route object

0IPv6 routes

1RPKI invalid 1 origin · 0 maxLength

4No ROA 5 with no route object for this origin

2Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS100, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS100, 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.


102.210.158.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
12.30.153.0/24	No ROA	None	673 100%	67
192.118.48.0/24	No ROA	None	672 100%	67
38.22.219.0/24	No ROA	None	422 63%	65
74.123.89.0/24	No ROA	Other origin only	1 0%low visibility	2

102.210.158.0/24

Invalid: origin

Other origin only

2 0%low visibility

12.30.153.0/24

No ROA

None

673 100%

192.118.48.0/24

No ROA

None

672 100%

38.22.219.0/24

No ROA

None

422 63%

74.123.89.0/24

No ROA

Other origin only

1 0%low visibility

AS-SET

AS100'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 10 are in fix.csv.

ROA: origin1
ROA: none4
Route object: none5

Change	Prefix or set	Detail	Full-table peers
ROA: origin	102.210.158.0/24	ROAs covering it name AS329381, not AS100. If AS100 should announce it, add a ROA for AS100.	2 of 673
Route object: none	102.210.158.0/24	Route objects for it name AS329381. Add a route object with origin AS100 in the RIR database for the space.	2 of 673
ROA: none	12.30.153.0/24	No ROA covers it. Add a ROA for AS100, maxLength 24.	673 of 673
Route object: none	12.30.153.0/24	No route object for it. Add a route object with origin AS100 in the RIR database for the space.	673 of 673
ROA: none	192.118.48.0/24	No ROA covers it. Add a ROA for AS100, maxLength 24.	672 of 673
Route object: none	192.118.48.0/24	No route object for it. Add a route object with origin AS100 in the RIR database for the space.	672 of 673
ROA: none	38.22.219.0/24	No ROA covers it. Add a ROA for AS100, maxLength 24.	422 of 673
Route object: none	38.22.219.0/24	No route object for it. Add a route object with origin AS100 in the RIR database for the space.	422 of 673
ROA: none	74.123.89.0/24	No ROA covers it. Add a ROA for AS100, maxLength 24.	1 of 673
Route object: none	74.123.89.0/24	Route objects for it name AS40620. Add a route object with origin AS100 in the RIR database for the space.	1 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

102.210.158.0/24

ROAs covering it name AS329381, not AS100. If AS100 should announce it, add a ROA for AS100.

2 of 673

Route object: none

102.210.158.0/24

Route objects for it name AS329381. Add a route object with origin AS100 in the RIR database for the space.

2 of 673

ROA: none

12.30.153.0/24

No ROA covers it. Add a ROA for AS100, maxLength 24.

673 of 673

Route object: none

12.30.153.0/24

No route object for it. Add a route object with origin AS100 in the RIR database for the space.

673 of 673

ROA: none

192.118.48.0/24

No ROA covers it. Add a ROA for AS100, maxLength 24.

672 of 673

Route object: none

192.118.48.0/24

No route object for it. Add a route object with origin AS100 in the RIR database for the space.

672 of 673

ROA: none

38.22.219.0/24

No ROA covers it. Add a ROA for AS100, maxLength 24.

422 of 673

Route object: none

38.22.219.0/24

No route object for it. Add a route object with origin AS100 in the RIR database for the space.

422 of 673

ROA: none

74.123.89.0/24

No ROA covers it. Add a ROA for AS100, maxLength 24.

1 of 673

Route object: none

74.123.89.0/24

Route objects for it name AS40620. Add a route object with origin AS100 in the RIR database for the space.

1 of 673

Route objects not announced

Every route object with origin AS100 is announced.

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.