Network · data from 2026-11-12

AS22401 FC-POTAWATOMI-MKE-BINGO-CASINO - Potawatomi Bingo Casino

Registry name: FC-POTAWATOMI-MKE-BINGO-CASINO - Potawatomi Bingo Casino, US · not in PeeringDB

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

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

4No ROA 1 with no route object for this origin

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

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

Announced routes

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


199.34.120.0/24	No ROA	Nonecovered by 199.34.120.0/23	673 100%	67
207.250.98.0/24	No ROA	Other IRR onlyRADB	672 100%	67
199.34.120.0/23	No ROA	Other IRR onlyRADB	668 99%	67
64.187.102.0/24	No ROA	Other IRR onlyRADB	1 0%low visibility	1

199.34.120.0/24

No ROA

Nonecovered by 199.34.120.0/23

673 100%

207.250.98.0/24

No ROA

Other IRR onlyRADB

672 100%

199.34.120.0/23

No ROA

Other IRR onlyRADB

668 99%

64.187.102.0/24

No ROA

Other IRR onlyRADB

1 0%low visibility

AS-SET

AS22401 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: none4
Route object: none1
Route object: RIR3

Change	Prefix or set	Detail	Full-table peers
ROA: none	199.34.120.0/24	No ROA covers it. Add a ROA for AS22401, maxLength 24.	673 of 673
Route object: none	199.34.120.0/24	No route object for it. A route object for 199.34.120.0/23 with origin AS22401 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22401 in the RIR database for the space.	673 of 673
ROA: none	207.250.98.0/24	No ROA covers it. Add a ROA for AS22401, maxLength 24.	672 of 673
Route object: RIR	207.250.98.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
ROA: none	199.34.120.0/23	No ROA covers it. Add a ROA for AS22401, maxLength 23.	668 of 673
Route object: RIR	199.34.120.0/23	Route object only in RADB. Add it in the RIR database for the space.	668 of 673
ROA: none	64.187.102.0/24	No ROA covers it. Add a ROA for AS22401, maxLength 24.	1 of 673
Route object: RIR	64.187.102.0/24	Route object only in RADB. Add it in the RIR database for the space.	1 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

199.34.120.0/24

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

673 of 673

Route object: none

199.34.120.0/24

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

673 of 673

ROA: none

207.250.98.0/24

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

672 of 673

Route object: RIR

207.250.98.0/24

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

672 of 673

ROA: none

199.34.120.0/23

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

668 of 673

Route object: RIR

199.34.120.0/23

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

668 of 673

ROA: none

64.187.102.0/24

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

1 of 673

Route object: RIR

64.187.102.0/24

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

1 of 673

Route objects not announced

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