Network · data from 2026-11-12

AS394542 MS-FIBER

Registry name: MS-FIBER - MS Fiber, LLC, US · PeeringDB

4IPv4 routes 25.0% RPKI valid · 25.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

2RPKI invalid 2 origin · 0 maxLength

1No ROA 3 with no route object for this origin

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

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

Announced routes

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


208.81.224.0/21	Invalid: origin	Other origin only	0 0%low visibility	1
208.93.98.0/23	Invalid: origin	Other origin only	0 0%low visibility	1
24.75.92.0/23	No ROA	Other origin only	0 0%low visibility	1
170.117.216.0/22	Valid	RIR databaseARIN	673 100%	67
2602:f962::/40	Valid	RIR databaseARIN	606 95%	67

208.81.224.0/21

Invalid: origin

Other origin only

0 0%low visibility

208.93.98.0/23

Invalid: origin

Other origin only

0 0%low visibility

24.75.92.0/23

No ROA

Other origin only

0 0%low visibility

170.117.216.0/22

Valid

RIR databaseARIN

673 100%

2602:f962::/40

Valid

RIR databaseARIN

606 95%

AS-SET

AS394542'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 6 are in fix.csv.

ROA: origin2
ROA: none1
Route object: none3

Change	Prefix or set	Detail	Full-table peers
ROA: origin	208.81.224.0/21	ROAs covering it name AS19709, not AS394542. If AS394542 should announce it, add a ROA for AS394542.	0 of 673
Route object: none	208.81.224.0/21	Route objects for it name AS19709. Add a route object with origin AS394542 in the RIR database for the space.	0 of 673
ROA: origin	208.93.98.0/23	ROAs covering it name AS19709, not AS394542. If AS394542 should announce it, add a ROA for AS394542.	0 of 673
Route object: none	208.93.98.0/23	Route objects for it name AS19709. Add a route object with origin AS394542 in the RIR database for the space.	0 of 673
ROA: none	24.75.92.0/23	No ROA covers it. Add a ROA for AS394542, maxLength 23.	0 of 673
Route object: none	24.75.92.0/23	Route objects for it name AS19709. Add a route object with origin AS394542 in the RIR database for the space.	0 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

208.81.224.0/21

ROAs covering it name AS19709, not AS394542. If AS394542 should announce it, add a ROA for AS394542.

0 of 673

Route object: none

208.81.224.0/21

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

0 of 673

ROA: origin

208.93.98.0/23

ROAs covering it name AS19709, not AS394542. If AS394542 should announce it, add a ROA for AS394542.

0 of 673

Route object: none

208.93.98.0/23

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

0 of 673

ROA: none

24.75.92.0/23

No ROA covers it. Add a ROA for AS394542, maxLength 23.

0 of 673

Route object: none

24.75.92.0/23

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

0 of 673

Route objects not announced

Every route object with origin AS394542 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.