bgpreport

Network · data from 2026-11-12

AS135392 MILLENIALHOSTLIMITED-AS-GB - MillenialHost Limited

Registry name: MILLENIALHOSTLIMITED-AS-GB - MillenialHost Limited, HK · not in PeeringDB

26IPv4 routes 96.2% RPKI valid · 88.5% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No ROA 3 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS135392, seen from no peer

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 2
178.18.159.0/24 Valid None 671 100% 66
188.221.119.0/24 Valid None 671 100% 66
185.215.151.0/24 Valid None 670 100% 67
93.95.115.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
104.223.26.0/24 Valid RIR databaseARIN 672 100% 67
143.14.49.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
85.118.167.0/24 Valid RIR databaseRIPE 671 100% 66
45.84.242.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
64.253.89.0/24 Valid RIR databaseARIN, RADB 670 100% 67
87.58.193.0/24 Valid RIR databaseRIPE 670 100% 67
87.58.194.0/24 Valid RIR databaseRIPE 670 100% 68
87.85.128.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
93.152.214.0/24 Valid RIR databaseRIPE 670 100% 67
94.26.3.0/24 Valid RIR databaseRIPE 670 100% 67
109.66.178.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
150.237.67.0/24 Valid RIR databaseRIPE 670 100% 67
150.241.209.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
155.117.213.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
167.148.201.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
178.248.79.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
192.109.139.0/24 Valid RIR databaseRIPE 670 100% 67
194.77.197.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
194.77.222.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
194.122.82.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
212.222.169.0/24 Valid RIR databaseRADB, RIPE 670 100% 68

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
ChangePrefix or setDetailFull-table peers
ROA: origin68.67.193.0/24ROAs covering it name AS834, not AS135392. If AS135392 should announce it, add a ROA for AS135392.1 of 673
Route object: none178.18.159.0/24No route object for it. Add a route object with origin AS135392 in the RIR database for the space.671 of 673
Route object: none188.221.119.0/24No route object for it. Add a route object with origin AS135392 in the RIR database for the space.671 of 673
Route object: none185.215.151.0/24No route object for it. Add a route object with origin AS135392 in the RIR database for the space.670 of 673

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/24ARINValid
94.26.32.0/24RIPEValid
181.215.41.0/24RADB, RIPEValid
181.215.186.0/24RADB, RIPEValid
185.143.72.0/24NTTCOMNo 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.