Network · data from 2026-11-12
AS12028 MMINTERNET - MM Internet, Inc.
Registry name: MMINTERNET - MM Internet, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12028, 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.
| 66.159.48.0/20 | No ROA | RIR databaseARIN, NTTCOM, RADB | 672 100% |
| 216.86.192.0/19 | No ROA | RIR databaseARIN, NTTCOM, RADB | 672 100% |
AS-SET
AS12028 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 40 are in fix.csv.
- ROA: none2
- Route object: not announced38
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 66.159.48.0/20 | No ROA covers it. Add a ROA for AS12028, maxLength 20. |
| ROA: none | 216.86.192.0/19 | No ROA covers it. Add a ROA for AS12028, maxLength 19. |
Route objects not announced
Route objects with origin AS12028 whose prefix no peer sees AS12028 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 204.108.16.0/24 | NTTCOM | No ROA |
| 204.108.17.0/24 | NTTCOM | No ROA |
| 204.108.18.0/24 | NTTCOM | No ROA |
| 204.108.19.0/24 | NTTCOM | No ROA |
| 205.153.191.0/24 | RADB | No ROA |
| 216.86.192.0/24 | RADB | No ROA |
| 216.86.193.0/24 | RADB | No ROA |
| 216.86.194.0/24 | RADB | No ROA |
| 216.86.195.0/24 | RADB | No ROA |
| 216.86.196.0/24 | RADB | No ROA |
| 216.86.197.0/24 | RADB | No ROA |
| 216.86.198.0/24 | RADB | No ROA |
| 216.86.199.0/24 | RADB | No ROA |
| 216.86.200.0/24 | RADB | No ROA |
| 216.86.201.0/24 | RADB | No ROA |
| 216.86.202.0/24 | RADB | No ROA |
| 216.86.203.0/24 | RADB | No ROA |
| 216.86.204.0/24 | RADB | No ROA |
| 216.86.205.0/24 | RADB | No ROA |
| 216.86.206.0/24 | RADB | No ROA |
| 216.86.207.0/24 | RADB | No ROA |
| 216.86.208.0/21 | RADB | No ROA |
| 216.86.208.0/24 | RADB | No ROA |
| 216.86.209.0/24 | RADB | No ROA |
| 216.86.210.0/24 | RADB | No ROA |
| 216.86.211.0/24 | RADB | No ROA |
| 216.86.212.0/24 | RADB | No ROA |
| 216.86.213.0/24 | RADB | No ROA |
| 216.86.214.0/24 | RADB | No ROA |
| 216.86.215.0/24 | RADB | No ROA |
| 216.86.216.0/24 | RADB | No ROA |
| 216.86.217.0/24 | RADB | No ROA |
| 216.86.218.0/24 | RADB | No ROA |
| 216.86.219.0/24 | RADB | No ROA |
| 216.86.220.0/24 | RADB | No ROA |
| 216.86.221.0/24 | RADB | No ROA |
| 216.86.222.0/24 | RADB | No ROA |
| 216.86.223.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.