Network · data from 2026-11-12
AS135392 MILLENIALHOSTLIMITED-AS-GB - MillenialHost Limited
Registry name: MILLENIALHOSTLIMITED-AS-GB - MillenialHost Limited, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135392, 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.
| 68.67.193.0/24 | Invalid: origin | RIR databaseARIN, RADB | 1 0%low visibility |
| 178.18.159.0/24 | Valid | None | 671 100% |
| 188.221.119.0/24 | Valid | None | 671 100% |
| 185.215.151.0/24 | Valid | None | 670 100% |
| 93.95.115.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 104.223.26.0/24 | Valid | RIR databaseARIN | 672 100% |
| 143.14.49.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 85.118.167.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.84.242.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 64.253.89.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 87.58.193.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.58.194.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.85.128.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 93.152.214.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 94.26.3.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 109.66.178.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 150.237.67.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 150.241.209.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 155.117.213.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 167.148.201.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 178.248.79.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 192.109.139.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 194.77.197.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 194.77.222.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 194.122.82.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 212.222.169.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
AS-SET
AS135392 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 9 are in fix.csv.
- ROA: origin1
- Route object: none3
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 68.67.193.0/24 | ROAs covering it name AS834, not AS135392. If AS135392 should announce it, add a ROA for AS135392. |
| Route object: none | 178.18.159.0/24 | No route object for it. Add a route object with origin AS135392 in the RIR database for the space. |
| Route object: none | 188.221.119.0/24 | No route object for it. Add a route object with origin AS135392 in the RIR database for the space. |
| Route object: none | 185.215.151.0/24 | No route object for it. Add a route object with origin AS135392 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS135392 whose prefix no peer sees AS135392 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.94.252.0/24 | ARIN | Valid |
| 94.26.32.0/24 | RIPE | Valid |
| 181.215.41.0/24 | RADB, RIPE | Valid |
| 181.215.186.0/24 | RADB, RIPE | Valid |
| 185.143.72.0/24 | NTTCOM | 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.