Network · data from 2026-11-12

AS46701 STATE-OF-INDIANA-IOT4 - Indiana Office of Technology

Registry name: STATE-OF-INDIANA-IOT4 - Indiana Office of Technology, US · not in PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

5No ROA 1 with no route object for this origin

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

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

Announced routes

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


108.59.56.0/22	No ROA	Nonecovered by 108.59.48.0/20	672 100%	67
108.59.48.0/20	No ROA	Other IRR onlyRADB	671 100%	69
108.59.48.0/21	No ROA	Other IRR onlyRADB	671 100%	69
108.59.60.0/22	No ROA	Other IRR onlyRADB	671 100%	69
2620:1e:e000::/48	No ROA	Other IRR onlyRADB	635 100%	70

AS-SET

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

ROA: none5
Route object: none1
Route object: RIR4

Change	Prefix or set	Detail	Full-table peers
ROA: none	108.59.56.0/22	No ROA covers it. Add a ROA for AS46701, maxLength 22.	672 of 673
Route object: none	108.59.56.0/22	No route object for it. A route object for 108.59.48.0/20 with origin AS46701 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46701 in the RIR database for the space.	672 of 673
ROA: none	108.59.48.0/20	No ROA covers it. Add a ROA for AS46701, maxLength 20.	671 of 673
Route object: RIR	108.59.48.0/20	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
ROA: none	108.59.48.0/21	No ROA covers it. Add a ROA for AS46701, maxLength 21.	671 of 673
Route object: RIR	108.59.48.0/21	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
ROA: none	108.59.60.0/22	No ROA covers it. Add a ROA for AS46701, maxLength 22.	671 of 673
Route object: RIR	108.59.60.0/22	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
ROA: none	2620:1e:e000::/48	No ROA covers it. Add a ROA for AS46701, maxLength 48.	635 of 636
Route object: RIR	2620:1e:e000::/48	Route object only in RADB. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

108.59.56.0/22

No ROA covers it. Add a ROA for AS46701, maxLength 22.

672 of 673

Route object: none

108.59.56.0/22

No route object for it. A route object for 108.59.48.0/20 with origin AS46701 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46701 in the RIR database for the space.

672 of 673

ROA: none

108.59.48.0/20

No ROA covers it. Add a ROA for AS46701, maxLength 20.

671 of 673

Route object: RIR

108.59.48.0/20

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

671 of 673

ROA: none

108.59.48.0/21

No ROA covers it. Add a ROA for AS46701, maxLength 21.

671 of 673

Route object: RIR

108.59.48.0/21

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

671 of 673

ROA: none

108.59.60.0/22

No ROA covers it. Add a ROA for AS46701, maxLength 22.

671 of 673

Route object: RIR

108.59.60.0/22

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

671 of 673

ROA: none

2620:1e:e000::/48

No ROA covers it. Add a ROA for AS46701, maxLength 48.

635 of 636

Route object: RIR

2620:1e:e000::/48

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

635 of 636

Route objects not announced

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