Network · data from 2026-11-12

AS395911 MDLIVE-1 - Maryland Live! Casino

Registry name: MDLIVE-1 - Maryland Live! Casino, US · not in PeeringDB

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

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

5No ROA 0 with no route object for this origin

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

1Route objects not announced registered with origin AS395911, seen from no peer

Announced routes

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


192.133.117.0/24	No ROA	Other IRR onlyRADB	673 100%	67
192.147.250.0/24	No ROA	Other IRR onlyRADB	673 100%	67
192.190.24.0/24	No ROA	Other IRR onlyRADB	673 100%	67
199.180.200.0/24	No ROA	Other IRR onlyRADB	672 100%	67
148.59.28.0/24	No ROA	Other IRR onlyRADB	671 100%	67

AS-SET

AS395911 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 11 are in fix.csv.

ROA: none5
Route object: RIR5
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	192.133.117.0/24	No ROA covers it. Add a ROA for AS395911, maxLength 24.	673 of 673
Route object: RIR	192.133.117.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	192.147.250.0/24	No ROA covers it. Add a ROA for AS395911, maxLength 24.	673 of 673
Route object: RIR	192.147.250.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	192.190.24.0/24	No ROA covers it. Add a ROA for AS395911, maxLength 24.	673 of 673
Route object: RIR	192.190.24.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	199.180.200.0/24	No ROA covers it. Add a ROA for AS395911, maxLength 24.	672 of 673
Route object: RIR	199.180.200.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
ROA: none	148.59.28.0/24	No ROA covers it. Add a ROA for AS395911, maxLength 24.	671 of 673
Route object: RIR	148.59.28.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: none

192.133.117.0/24

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

673 of 673

Route object: RIR

192.133.117.0/24

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

673 of 673

ROA: none

192.147.250.0/24

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

673 of 673

Route object: RIR

192.147.250.0/24

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

673 of 673

ROA: none

192.190.24.0/24

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

673 of 673

Route object: RIR

192.190.24.0/24

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

673 of 673

ROA: none

199.180.200.0/24

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

672 of 673

Route object: RIR

199.180.200.0/24

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

672 of 673

ROA: none

148.59.28.0/24

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

671 of 673

Route object: RIR

148.59.28.0/24

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

671 of 673

Route objects not announced

Route objects with origin AS395911 whose prefix no peer sees AS395911 announce. Many are kept on purpose (backup routes, space announced only in some places).


192.238.16.0/24	RADB	No ROA

192.238.16.0/24

RADB

No ROA

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.