bgpreport

Network · data from 2026-11-12

AS132167 Nine Communications Co.Ltd

Registry name: U9-MM - Nine Communications Company Limited, MM · PeeringDB

47IPv4 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
0Low visibility seen by under 10% of full-table peers
78Route objects not announced registered with origin AS132167, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS132167, 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.

43.224.84.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
43.224.85.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
43.224.86.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
69.160.5.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
69.160.11.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
69.160.24.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
69.160.25.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
69.160.27.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
69.160.28.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
69.160.29.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
69.160.30.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
69.160.31.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.242.99.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
69.160.0.0/21 Valid RIR databaseAPNIC, RADB 671 100% 67
69.160.2.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
69.160.3.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
69.160.4.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
69.160.6.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
69.160.8.0/21 Valid RIR databaseAPNIC 671 100% 67
69.160.8.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
69.160.9.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
69.160.13.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
69.160.16.0/21 Valid RIR databaseAPNIC 671 100% 67
69.160.24.0/21 Valid RIR databaseAPNIC, RADB 671 100% 67
74.50.212.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
74.50.213.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
74.50.214.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
74.50.215.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.242.97.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.242.98.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
69.160.1.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
69.160.17.0/24 Valid RIR databaseAPNIC 670 100% 67
69.160.18.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
69.160.19.0/24 Valid RIR databaseAPNIC 670 100% 67
74.50.208.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
74.50.209.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
69.160.0.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 669 99% 67
69.160.14.0/24 Valid RIR databaseAPNIC 669 99% 66
69.160.16.0/24 Valid RIR databaseAPNIC 669 99% 66
74.50.210.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 669 99% 67
69.160.10.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 66
69.160.20.0/24 Valid RIR databaseAPNIC 668 99% 67
69.160.21.0/24 Valid RIR databaseAPNIC 668 99% 67
69.160.23.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67
69.160.26.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 66
74.50.211.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 667 99% 66
69.160.7.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 665 99% 66
2407:f300:108::/48 Valid RIR databaseAPNIC 635 100% 67
2407:f300:100::/48 Valid RIR databaseAPNIC 632 99% 67
2407:f300:101::/48 Valid RIR databaseAPNIC 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS132167: AS132167:AS-GLOBAL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS132167 isn't in the set, or no route object for AS132167 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS132167 in itNot covered
AS132167:AS-GLOBAL APNIC 87113,338 Yes 0

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 78 are in fix.csv.

  • Route object: not announced78

Route objects not announced

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

43.224.84.0/22APNIC, NTTCOM, RADBValid
45.254.44.0/22NTTCOM, RADBNo ROA
45.254.44.0/23NTTCOM, RADBNo ROA
45.254.44.0/24NTTCOM, RADBNo ROA
45.254.45.0/24NTTCOM, RADBNo ROA
45.254.46.0/23NTTCOM, RADBNo ROA
45.254.46.0/24NTTCOM, RADBNo ROA
45.254.47.0/24NTTCOM, RADBNo ROA
69.160.0.0/19APNIC, RADBValid
69.160.22.0/24APNICValid
74.50.208.0/21APNIC, RADBValid
103.13.32.0/22NTTCOMNo ROA
103.47.185.0/24NTTCOM, RADBNo ROA
103.64.20.0/22NTTCOM, RADBNo ROA
103.76.184.0/23NTTCOM, RADBNo ROA
103.80.36.0/22NTTCOM, RADBNo ROA
103.80.36.0/23NTTCOM, RADBNo ROA
103.80.36.0/24NTTCOMNo ROA
103.80.37.0/24NTTCOMNo ROA
103.80.38.0/23NTTCOM, RADBNo ROA
103.80.38.0/24NTTCOMNo ROA
103.80.39.0/24NTTCOMNo ROA
103.94.52.0/22NTTCOM, RADBNo ROA
103.94.52.0/23NTTCOM, RADBNo ROA
103.94.52.0/24NTTCOM, RADBNo ROA
103.94.53.0/24NTTCOM, RADBNo ROA
103.94.54.0/23NTTCOM, RADBNo ROA
103.94.54.0/24NTTCOM, RADBNo ROA
103.94.55.0/24NTTCOM, RADBNo ROA
103.94.144.0/22NTTCOM, RADBNo ROA
103.94.144.0/23NTTCOM, RADBNo ROA
103.94.144.0/24NTTCOM, RADBNo ROA
103.94.145.0/24NTTCOM, RADBNo ROA
103.94.146.0/23NTTCOM, RADBNo ROA
103.94.146.0/24NTTCOM, RADBNo ROA
103.94.147.0/24NTTCOM, RADBNo ROA
103.97.110.0/24NTTCOMNo ROA
103.116.159.0/24NTTCOM, RADBNo ROA
103.121.224.0/21NTTCOM, RADBNo ROA
103.121.224.0/22NTTCOM, RADBNo ROA
103.121.224.0/23NTTCOM, RADBNo ROA
103.121.226.0/23NTTCOM, RADBNo ROA
103.138.252.0/23NTTCOM, RADBNo ROA
103.143.246.0/23NTTCOM, RADBNo ROA
103.143.246.0/24NTTCOM, RADBNo ROA
103.143.247.0/24NTTCOM, RADBNo ROA
103.144.8.0/23NTTCOM, RADBNo ROA
103.144.8.0/24NTTCOM, RADBNo ROA
103.144.9.0/24NTTCOM, RADBNo ROA
103.146.48.0/23NTTCOMNo ROA
103.146.48.0/24NTTCOMNo ROA
103.146.49.0/24NTTCOMNo ROA
103.197.196.0/22RADBNo ROA
103.197.196.0/23RADBNo ROA
103.197.198.0/23RADBNo ROA
103.203.132.0/22NTTCOMNo ROA
103.203.132.0/23NTTCOM, RADBNo ROA
103.203.134.0/23NTTCOM, RADBNo ROA
103.219.108.0/22RADBNo ROA
103.242.96.0/22APNIC, NTTCOM, RADBValid
122.10.248.0/23NTTCOM, RADBNo ROA
122.10.248.0/24NTTCOM, RADBNo ROA
122.10.249.0/24NTTCOM, RADBNo ROA
130.40.180.0/24NTTCOM, RADBNo ROA
157.240.173.0/24NTTCOM, RADBNo ROA
163.171.190.0/24NTTCOM, RADBNo ROA
180.235.116.0/22NTTCOMNo ROA
180.235.116.0/23NTTCOM, RADBNo ROA
180.235.118.0/23NTTCOM, RADBNo ROA
194.156.176.0/22NTTCOMNo ROA
194.156.176.0/23NTTCOMNo ROA
194.156.178.0/23NTTCOMNo ROA
203.166.158.0/23NTTCOM, RADBNo ROA
203.166.158.0/24NTTCOM, RADBNo ROA
203.166.159.0/24NTTCOM, RADBNo ROA
2407:f300::/32APNICValid
2407:f300:100::/44APNICValid
2407:f300:110::/44APNICValid

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.