bgpreport

Network · data from 2026-11-12

AS136750 CMI Cloud

Registry name: CMI-INT-AS-AP - China Mobile International Limited, HK · PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS136750, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136750, 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.
223.119.128.0/23 Valid RIR databaseAPNIC 672 100% 67
223.119.129.0/24 Valid RIR databaseAPNIC 672 100% 67
223.119.133.0/24 Valid RIR databaseAPNIC 672 100% 66
223.119.130.0/23 Valid RIR databaseAPNIC 670 100% 67
223.119.131.0/24 Valid RIR databaseAPNIC 670 100% 67
223.119.132.0/24 Valid RIR databaseAPNIC 670 100% 67
2402:4f00:f004::/48 Valid RIR databaseAPNIC 628 99% 67
2402:4f00:f004:600::/56 Valid RIR databaseAPNIC 59 9%low visibility 35
2402:4f00:f004:5::/64 Valid RIR databaseAPNIC 52 8%low visibility 32

AS-SET

AS136750's PeeringDB record names no 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 12 are in fix.csv.

  • Route object: not announced12

Route objects not announced

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

223.119.128.0/21APNICValid
223.119.128.0/24APNICValid
223.119.130.0/24APNICValid
223.119.204.0/24APNICValid
223.119.205.0/24APNICValid
223.119.206.0/24APNICValid
223.119.207.0/24APNICValid
223.119.208.0/24APNICValid
223.119.209.0/24APNICValid
223.119.210.0/24APNICValid
223.119.211.0/24APNICValid
2402:4f00:4004::/48APNICValid

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.