Network · data from 2026-11-12
AS16667 MGMRI-AS - MGM Resorts International Operations, Inc.
Registry name: MGMRI-AS - MGM Resorts International Operations, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16667, 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.
| 69.162.0.0/24 | No ROA | Other origin onlycovered by 69.162.0.0/18 | 673 100% |
| 69.162.1.0/24 | No ROA | Other origin onlycovered by 69.162.0.0/18 | 673 100% |
| 69.162.2.0/24 | No ROA | Nonecovered by 69.162.0.0/18 | 673 100% |
| 69.162.3.0/24 | No ROA | Other origin onlycovered by 69.162.0.0/18 | 673 100% |
| 69.162.8.0/22 | No ROA | Other origin onlycovered by 69.162.0.0/18 | 673 100% |
| 69.162.12.0/22 | No ROA | Other origin onlycovered by 69.162.0.0/18 | 673 100% |
| 69.162.16.0/24 | No ROA | Nonecovered by 69.162.0.0/18 | 673 100% |
| 69.162.24.0/23 | No ROA | Nonecovered by 69.162.0.0/18 | 673 100% |
| 69.162.61.0/24 | No ROA | Nonecovered by 69.162.0.0/18 | 673 100% |
| 69.162.63.0/24 | No ROA | Nonecovered by 69.162.0.0/18 | 673 100% |
AS-SET
AS16667 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 24 are in fix.csv.
- ROA: none10
- Route object: none10
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 69.162.0.0/24 | No ROA covers it. Add a ROA for AS16667, maxLength 24. |
| Route object: none | 69.162.0.0/24 | Route objects for it name AS19905. A route object for 69.162.0.0/18 with origin AS16667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16667 in the RIR database for the space. |
| ROA: none | 69.162.1.0/24 | No ROA covers it. Add a ROA for AS16667, maxLength 24. |
| Route object: none | 69.162.1.0/24 | Route objects for it name AS19905. A route object for 69.162.0.0/18 with origin AS16667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16667 in the RIR database for the space. |
| ROA: none | 69.162.2.0/24 | No ROA covers it. Add a ROA for AS16667, maxLength 24. |
| Route object: none | 69.162.2.0/24 | No route object for it. A route object for 69.162.0.0/18 with origin AS16667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16667 in the RIR database for the space. |
| ROA: none | 69.162.3.0/24 | No ROA covers it. Add a ROA for AS16667, maxLength 24. |
| Route object: none | 69.162.3.0/24 | Route objects for it name AS19905. A route object for 69.162.0.0/18 with origin AS16667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16667 in the RIR database for the space. |
| ROA: none | 69.162.8.0/22 | No ROA covers it. Add a ROA for AS16667, maxLength 22. |
| Route object: none | 69.162.8.0/22 | Route objects for it name AS19905. A route object for 69.162.0.0/18 with origin AS16667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16667 in the RIR database for the space. |
| ROA: none | 69.162.12.0/22 | No ROA covers it. Add a ROA for AS16667, maxLength 22. |
| Route object: none | 69.162.12.0/22 | Route objects for it name AS19905. A route object for 69.162.0.0/18 with origin AS16667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16667 in the RIR database for the space. |
| ROA: none | 69.162.16.0/24 | No ROA covers it. Add a ROA for AS16667, maxLength 24. |
| Route object: none | 69.162.16.0/24 | No route object for it. A route object for 69.162.0.0/18 with origin AS16667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16667 in the RIR database for the space. |
| ROA: none | 69.162.24.0/23 | No ROA covers it. Add a ROA for AS16667, maxLength 23. |
| Route object: none | 69.162.24.0/23 | No route object for it. A route object for 69.162.0.0/18 with origin AS16667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16667 in the RIR database for the space. |
| ROA: none | 69.162.61.0/24 | No ROA covers it. Add a ROA for AS16667, maxLength 24. |
| Route object: none | 69.162.61.0/24 | No route object for it. A route object for 69.162.0.0/18 with origin AS16667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16667 in the RIR database for the space. |
| ROA: none | 69.162.63.0/24 | No ROA covers it. Add a ROA for AS16667, maxLength 24. |
| Route object: none | 69.162.63.0/24 | No route object for it. A route object for 69.162.0.0/18 with origin AS16667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16667 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16667 whose prefix no peer sees AS16667 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.165.24.0/24 | RADB | No ROA |
| 67.76.188.0/22 | RADB | No ROA |
| 69.162.0.0/18 | RADB | No ROA |
| 206.228.101.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.