Network · data from 2026-11-12

AS398119 DORDT-UNIVERSITY - Dordt University

Registry name: DORDT-UNIVERSITY - Dordt University, US · not in PeeringDB

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

0IPv6 routes

3RPKI invalid 3 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 AS398119, seen from no peer

Announced routes

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


173.233.32.0/21	Invalid: origin	None	2 0%low visibility	2
173.233.40.0/22	Invalid: origin	None	2 0%low visibility	2
173.233.44.0/23	Invalid: origin	None	2 0%low visibility	2
198.97.44.0/24	No ROA	Other IRR onlyRADB	671 100%	68

173.233.32.0/21

Invalid: origin

None

2 0%low visibility

173.233.40.0/22

Invalid: origin

None

2 0%low visibility

173.233.44.0/23

Invalid: origin

None

2 0%low visibility

198.97.44.0/24

No ROA

Other IRR onlyRADB

671 100%

AS-SET

AS398119 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 8 are in fix.csv.

ROA: origin3
ROA: none1
Route object: none3
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: origin	173.233.32.0/21	ROAs covering it name AS53347, not AS398119. If AS398119 should announce it, add a ROA for AS398119.	2 of 673
Route object: none	173.233.32.0/21	No route object for it. Add a route object with origin AS398119 in the RIR database for the space.	2 of 673
ROA: origin	173.233.40.0/22	ROAs covering it name AS53347, not AS398119. If AS398119 should announce it, add a ROA for AS398119.	2 of 673
Route object: none	173.233.40.0/22	No route object for it. Add a route object with origin AS398119 in the RIR database for the space.	2 of 673
ROA: origin	173.233.44.0/23	ROAs covering it name AS53347, not AS398119. If AS398119 should announce it, add a ROA for AS398119.	2 of 673
Route object: none	173.233.44.0/23	No route object for it. Add a route object with origin AS398119 in the RIR database for the space.	2 of 673
ROA: none	198.97.44.0/24	No ROA covers it. Add a ROA for AS398119, maxLength 24.	671 of 673
Route object: RIR	198.97.44.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

173.233.32.0/21

ROAs covering it name AS53347, not AS398119. If AS398119 should announce it, add a ROA for AS398119.

2 of 673

Route object: none

173.233.32.0/21

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

2 of 673

ROA: origin

173.233.40.0/22

ROAs covering it name AS53347, not AS398119. If AS398119 should announce it, add a ROA for AS398119.

2 of 673

Route object: none

173.233.40.0/22

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

2 of 673

ROA: origin

173.233.44.0/23

ROAs covering it name AS53347, not AS398119. If AS398119 should announce it, add a ROA for AS398119.

2 of 673

Route object: none

173.233.44.0/23

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

2 of 673

ROA: none

198.97.44.0/24

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

671 of 673

Route object: RIR

198.97.44.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route objects not announced

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