bgpreport

Network · data from 2026-11-12

AS4759 ITEXTRON-AS-AP - TEXTRON CORPORATION

Registry name: ITEXTRON-AS-AP - TEXTRON CORPORATION, PH · not in PeeringDB

65IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
172Route objects not announced registered with origin AS4759, seen from no peer

Announced routes

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

210.16.0.0/18 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
210.16.0.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.5.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.6.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.7.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.8.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.9.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.10.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.11.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.12.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.13.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.14.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.33.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.34.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.35.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.36.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.48.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.49.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.50.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.51.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.52.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.53.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.54.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.55.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 66
210.16.56.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 66
210.16.57.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 66
210.16.58.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 66
210.16.59.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 66
210.16.60.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.61.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.62.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.63.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
210.16.1.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.2.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.3.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.4.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.15.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.16.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.17.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.18.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.19.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.20.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.21.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.22.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.23.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.24.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.25.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.26.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.27.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.28.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.29.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.30.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.31.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.32.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.37.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 670 100% 67
210.16.38.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 670 100% 67
210.16.39.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 670 100% 67
210.16.40.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.41.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.42.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.43.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.44.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.45.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.46.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
210.16.47.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67

AS-SET

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

  • Route object: not announced172

Route objects not announced

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

103.251.132.0/23RADBNo ROA
103.251.132.0/24RADBNo ROA
103.251.133.0/24RADBNo ROA
202.92.128.0/19NTTCOM, RADBNo ROA
202.92.143.0/24NTTCOM, RADBNo ROA
202.92.144.0/24REACHInvalid: origin
202.92.158.0/24NTTCOM, RADBNo ROA
202.151.34.0/23REACHInvalid: origin
202.151.34.0/24REACHInvalid: origin
203.80.140.0/24NTTCOM, RADBNo ROA
203.80.142.0/24NTTCOM, RADBNo ROA
203.80.143.0/24NTTCOM, RADBNo ROA
208.8.224.0/24NTTCOMNo ROA
208.8.225.0/24NTTCOMNo ROA
208.8.226.0/24NTTCOMNo ROA
208.8.227.0/24NTTCOMNo ROA
208.8.228.0/24NTTCOMNo ROA
208.8.229.0/24NTTCOMNo ROA
208.8.230.0/24NTTCOMNo ROA
208.8.231.0/24NTTCOMNo ROA
208.8.232.0/24NTTCOMNo ROA
208.8.233.0/24NTTCOMNo ROA
208.8.234.0/24NTTCOMNo ROA
208.8.235.0/24NTTCOMNo ROA
208.8.236.0/24NTTCOMNo ROA
208.8.237.0/24NTTCOMNo ROA
208.8.238.0/24NTTCOMNo ROA
208.8.239.0/24NTTCOMNo ROA
208.8.240.0/24NTTCOMNo ROA
208.8.241.0/24NTTCOMNo ROA
208.8.242.0/24NTTCOMNo ROA
208.8.243.0/24NTTCOMNo ROA
208.8.244.0/24NTTCOMNo ROA
208.8.245.0/24NTTCOMNo ROA
208.8.246.0/24NTTCOMNo ROA
208.8.247.0/24NTTCOMNo ROA
208.8.248.0/24NTTCOMNo ROA
208.8.249.0/24NTTCOMNo ROA
208.8.250.0/24NTTCOMNo ROA
208.8.251.0/24NTTCOMNo ROA
208.8.252.0/24NTTCOMNo ROA
208.8.253.0/24NTTCOMNo ROA
208.8.254.0/24NTTCOMNo ROA
208.8.255.0/24NTTCOMNo ROA
210.16.0.0/17NTTCOM, RADBNo ROA
210.16.0.0/19APNIC, NTTCOM, RADBValid
210.16.0.0/20APNIC, NTTCOM, RADB, REACHValid
210.16.0.0/21APNIC, NTTCOM, RADBValid
210.16.0.0/22APNIC, NTTCOM, RADBValid
210.16.0.0/23APNIC, NTTCOM, RADBValid
210.16.2.0/23APNIC, NTTCOM, RADBValid
210.16.4.0/22APNIC, NTTCOM, RADBValid
210.16.4.0/23APNIC, NTTCOM, RADBValid
210.16.6.0/23APNIC, NTTCOM, RADBValid
210.16.8.0/21APNIC, NTTCOM, RADBValid
210.16.8.0/22APNIC, NTTCOM, RADBValid
210.16.8.0/23APNIC, NTTCOM, RADBValid
210.16.10.0/23APNIC, NTTCOM, RADBValid
210.16.12.0/22APNIC, NTTCOM, RADBValid
210.16.12.0/23APNIC, NTTCOM, RADBValid
210.16.14.0/23APNIC, NTTCOM, RADBValid
210.16.16.0/20APNIC, NTTCOM, RADB, REACHValid
210.16.16.0/21APNIC, NTTCOM, RADBValid
210.16.16.0/22APNIC, NTTCOM, RADBValid
210.16.16.0/23APNIC, NTTCOM, RADBValid
210.16.18.0/23APNIC, NTTCOM, RADBValid
210.16.20.0/22APNIC, NTTCOM, RADBValid
210.16.20.0/23APNIC, NTTCOM, RADBValid
210.16.22.0/23APNIC, NTTCOM, RADBValid
210.16.24.0/21APNIC, NTTCOM, RADBValid
210.16.24.0/22APNIC, NTTCOM, RADBValid
210.16.24.0/23APNIC, NTTCOM, RADBValid
210.16.26.0/23APNIC, NTTCOM, RADBValid
210.16.28.0/22APNIC, NTTCOM, RADBValid
210.16.28.0/23APNIC, NTTCOM, RADBValid
210.16.30.0/23APNIC, NTTCOM, RADBValid
210.16.32.0/19APNIC, NTTCOM, RADBValid
210.16.32.0/20APNIC, NTTCOM, RADB, REACHValid
210.16.32.0/21APNIC, NTTCOM, RADBValid
210.16.32.0/22APNIC, NTTCOM, RADBValid
210.16.32.0/23APNIC, NTTCOM, RADBValid
210.16.34.0/23APNIC, NTTCOM, RADBValid
210.16.36.0/22APNIC, NTTCOM, RADBValid
210.16.36.0/23APNIC, NTTCOM, RADBValid
210.16.38.0/23APNIC, NTTCOM, RADBValid
210.16.40.0/21APNIC, NTTCOM, RADBValid
210.16.40.0/22APNIC, NTTCOM, RADBValid
210.16.40.0/23APNIC, NTTCOM, RADBValid
210.16.42.0/23APNIC, NTTCOM, RADBValid
210.16.44.0/22APNIC, NTTCOM, RADBValid
210.16.44.0/23APNIC, NTTCOM, RADBValid
210.16.46.0/23APNIC, NTTCOM, RADBValid
210.16.48.0/20APNIC, NTTCOM, RADBValid
210.16.48.0/21APNIC, NTTCOM, RADBValid
210.16.48.0/22APNIC, NTTCOM, RADB, REACHValid
210.16.48.0/23APNIC, NTTCOM, RADBValid
210.16.50.0/23APNIC, NTTCOM, RADBValid
210.16.52.0/22APNIC, NTTCOM, RADB, REACHValid
210.16.52.0/23APNIC, NTTCOM, RADBValid
210.16.54.0/23APNIC, NTTCOM, RADBValid
210.16.56.0/21APNIC, NTTCOM, RADBValid
210.16.56.0/22APNIC, NTTCOM, RADBValid
210.16.56.0/23APNIC, NTTCOM, RADBValid
210.16.58.0/23APNIC, NTTCOM, RADBValid
210.16.60.0/22APNIC, NTTCOM, RADBValid
210.16.60.0/23APNIC, NTTCOM, RADBValid
210.16.62.0/23APNIC, NTTCOM, RADBValid
210.16.64.0/18NTTCOM, RADBNo ROA
210.16.64.0/19NTTCOM, RADBNo ROA
210.16.64.0/20NTTCOM, RADBNo ROA
210.16.64.0/21NTTCOMNo ROA
210.16.69.0/24REACHInvalid: origin
210.16.70.0/24REACHInvalid: origin
210.16.72.0/21NTTCOM, RADBNo ROA
210.16.72.0/22NTTCOM, RADBNo ROA
210.16.72.0/23NTTCOM, RADBNo ROA
210.16.72.0/24NTTCOM, RADB, REACHNo ROA
210.16.73.0/24NTTCOM, RADB, REACHNo ROA
210.16.74.0/23NTTCOM, RADBNo ROA
210.16.74.0/24NTTCOM, RADB, REACHNo ROA
210.16.75.0/24NTTCOM, RADBNo ROA
210.16.76.0/22NTTCOM, RADBNo ROA
210.16.76.0/23NTTCOM, RADBNo ROA
210.16.76.0/24NTTCOM, RADBNo ROA
210.16.77.0/24NTTCOM, RADBNo ROA
210.16.78.0/23NTTCOM, RADBNo ROA
210.16.78.0/24NTTCOM, RADBNo ROA
210.16.79.0/24NTTCOM, RADBNo ROA
210.16.80.0/20NTTCOM, RADBNo ROA
210.16.80.0/21NTTCOM, RADBNo ROA
210.16.88.0/21NTTCOM, RADBNo ROA
210.16.92.0/22NTTCOM, RADBNo ROA
210.16.92.0/23NTTCOM, RADBNo ROA
210.16.94.0/23NTTCOM, RADBNo ROA
210.16.96.0/19NTTCOM, RADBNo ROA
210.16.96.0/20NTTCOM, RADBNo ROA
210.16.96.0/21NTTCOM, RADBNo ROA
210.16.100.0/22NTTCOM, RADBNo ROA
210.16.100.0/23NTTCOM, RADBNo ROA
210.16.100.0/24NTTCOM, RADBNo ROA
210.16.101.0/24REACHInvalid: origin
210.16.102.0/23NTTCOM, RADBNo ROA
210.16.102.0/24NTTCOM, RADBNo ROA
210.16.103.0/24NTTCOM, RADB, REACHNo ROA
210.16.104.0/21NTTCOM, RADBNo ROA
210.16.104.0/24REACHInvalid: origin
210.16.105.0/24REACHInvalid: origin
210.16.108.0/22NTTCOM, RADBNo ROA
210.16.108.0/23NTTCOM, RADBNo ROA
210.16.110.0/23NTTCOM, RADBNo ROA
210.16.112.0/20NTTCOM, RADBNo ROA
210.16.112.0/21NTTCOM, RADBNo ROA
210.16.112.0/22NTTCOM, RADBNo ROA
210.16.112.0/23NTTCOM, RADBNo ROA
210.16.112.0/24NTTCOM, RADBNo ROA
210.16.113.0/24NTTCOM, RADBNo ROA
210.16.114.0/23NTTCOM, RADBNo ROA
210.16.114.0/24NTTCOM, RADBNo ROA
210.16.115.0/24NTTCOM, RADBNo ROA
210.16.116.0/22NTTCOM, RADBNo ROA
210.16.116.0/23NTTCOM, RADBNo ROA
210.16.116.0/24NTTCOM, RADBNo ROA
210.16.117.0/24NTTCOM, RADBNo ROA
210.16.118.0/23NTTCOM, RADBNo ROA
210.16.118.0/24NTTCOM, RADBNo ROA
210.16.119.0/24NTTCOM, RADBNo ROA
210.16.120.0/21NTTCOM, RADBNo ROA
210.16.120.0/22NTTCOM, RADBNo ROA
210.16.122.0/23NTTCOM, RADBNo ROA
210.16.126.0/24REACHInvalid: origin
210.17.84.0/24REACHInvalid: origin
210.151.35.0/24REACHNo 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.