bgpreport

Network · data from 2026-11-12

AS6421 AS6421 - TATA COMMUNICATIONS (AMERICA) INC

Registry name: AS6421 - TATA COMMUNICATIONS (AMERICA) INC, US · not in PeeringDB

38IPv4 routes 92.1% RPKI valid · 94.7% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
3No ROA 3 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
161Route objects not announced registered with origin AS6421, seen from no peer

Announced routes

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

103.16.252.32/27 Invalid: maxLength Nonecovered by 103.16.252.0/23 1 0%low visibility 1
2405:2001:100::/48 No ROA None 635 100% 67
138.104.230.0/24 No ROA RIR databaseNTTCOM, RADB, RIPE 671 100% 67
138.104.231.0/24 No ROA RIR databaseNTTCOM, RADB, RIPE 671 100% 67
202.183.66.0/24 Valid None 672 100% 67
180.87.29.0/24 Valid Other IRR onlyRADB 672 100% 67
116.0.66.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
180.87.13.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
180.87.68.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
180.87.121.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
180.87.126.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
180.87.138.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
180.87.139.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
180.87.140.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
180.87.141.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
180.87.191.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
202.183.75.0/24 Valid RIR databaseAPNIC 673 100% 67
180.87.91.0/24 Valid RIR databaseAPNIC 672 100% 67
180.87.115.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
180.87.120.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.183.65.0/24 Valid RIR databaseAPNIC 672 100% 67
202.183.72.0/24 Valid RIR databaseAPNIC 672 100% 67
103.16.254.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
180.87.92.0/24 Valid RIR databaseAPNIC 671 100% 67
180.87.122.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
180.87.124.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
180.87.127.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
180.87.152.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
180.87.153.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
180.87.190.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
202.183.69.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
202.183.70.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
202.183.76.0/24 Valid RIR databaseAPNIC 671 100% 67
202.183.77.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
202.183.79.0/24 Valid RIR databaseAPNIC 671 100% 67
180.87.119.0/24 Valid RIR databaseAPNIC 670 100% 67
103.16.252.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 596 89% 67
202.183.64.0/24 Valid RIR databaseAPNIC 99 15% 38
202.183.74.0/24 Valid RIR databaseAPNIC 99 15% 38

AS-SET

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

  • ROA: maxLength1
  • ROA: none3
  • Route object: none3
  • Route object: RIR11
  • Route object: not announced161
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.16.252.32/27ROA 103.16.252.0/23 AS6421 has maxLength 23; the route is a /27. Raise the maxLength, or add a ROA for 103.16.252.32/27.1 of 673
Route object: none103.16.252.32/27No route object for it. A route object for 103.16.252.0/23 with origin AS6421 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS6421 in the RIR database for the space.1 of 673
ROA: none2405:2001:100::/48No ROA covers it. Add a ROA for AS6421, maxLength 48.635 of 636
Route object: none2405:2001:100::/48No route object for it. Add a route object with origin AS6421 in the RIR database for the space.635 of 636
ROA: none138.104.230.0/24No ROA covers it. Add a ROA for AS6421, maxLength 24.671 of 673
ROA: none138.104.231.0/24No ROA covers it. Add a ROA for AS6421, maxLength 24.671 of 673
Route object: none202.183.66.0/24No route object for it. Add a route object with origin AS6421 in the RIR database for the space.672 of 673
Route object: RIR180.87.29.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.0.66.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR180.87.13.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR180.87.68.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR180.87.121.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR180.87.126.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR180.87.138.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR180.87.139.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR180.87.140.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR180.87.141.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR180.87.191.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

14.141.246.0/24APNICValid
14.141.247.0/24APNICValid
36.37.32.0/22NTTCOM, RADBNo ROA
36.37.32.0/23NTTCOM, RADBNo ROA
36.37.32.0/24NTTCOM, RADBNo ROA
36.37.33.0/24NTTCOM, RADBNo ROA
36.37.34.0/23NTTCOM, RADBNo ROA
36.37.34.0/24NTTCOM, RADBNo ROA
36.37.35.0/24NTTCOM, RADBNo ROA
41.77.24.0/22RADBNo ROA
41.77.28.0/22RADBNo ROA
41.160.0.0/14RADBNo ROA
41.160.56.0/21RADBNo ROA
41.160.107.0/24RADBNo ROA
41.160.168.0/21RADBNo ROA
41.160.176.0/23RADBNo ROA
41.160.212.0/22RADBNo ROA
41.160.216.0/21RADBNo ROA
41.161.0.0/21RADBNo ROA
41.161.8.0/21RADBNo ROA
41.161.8.0/23RADBNo ROA
41.161.60.0/22RADBNo ROA
41.161.64.0/22RADBNo ROA
41.162.156.0/22RADBNo ROA
41.168.0.0/16RADBNo ROA
41.169.23.0/24RADBNo ROA
41.174.0.0/17RADBNo ROA
59.164.76.0/24APNICValid
59.164.77.0/24APNICValid
64.185.160.0/19RADBNo ROA
64.185.167.0/24RADBNo ROA
64.185.176.0/24RADBNo ROA
64.185.179.0/24RADBNo ROA
64.185.181.0/24RADBNo ROA
87.236.68.0/24RADBNo ROA
91.240.195.0/24RADBNo ROA
91.240.204.0/23RADBNo ROA
103.15.25.0/24RADBNo ROA
105.235.160.0/20RADBNo ROA
105.235.168.0/21RADBNo ROA
105.235.170.0/24RADBNo ROA
115.85.131.0/24RADBNo ROA
115.110.74.0/24APNICValid
115.110.75.0/24APNICValid
115.112.20.0/24APNICValid
115.112.21.0/24APNICValid
121.240.218.0/24APNICValid
121.240.219.0/24APNICValid
121.240.248.0/24APNICValid
138.104.232.0/24RIPENo ROA
141.228.50.0/24RADBNo ROA
154.66.208.0/22RADBNo ROA
154.73.72.0/22RADBNo ROA
154.73.220.0/22RADBNo ROA
163.195.0.0/17RADBNo ROA
163.195.38.0/24RADBNo ROA
163.195.40.0/22RADBNo ROA
163.195.128.0/17RADBNo ROA
164.146.0.0/15RADBNo ROA
164.148.0.0/14RADBNo ROA
164.151.0.0/17RADBNo ROA
164.151.128.0/17RADBNo ROA
180.87.27.0/24NTTCOMValid
180.87.76.0/24NTTCOM, RADBValid
180.87.117.0/24RADBValid
180.87.129.0/24NTTCOMValid
180.87.182.0/24NTTCOMValid
192.8.59.0/24RADBNo ROA
192.96.234.0/24RADBNo ROA
192.96.235.0/24RADBNo ROA
192.96.236.0/24RADBNo ROA
192.96.237.0/24RADBNo ROA
192.96.238.0/24RADBNo ROA
192.96.239.0/24RADBNo ROA
192.96.240.0/24RADBNo ROA
192.96.241.0/24RADBNo ROA
192.96.242.0/24RADBNo ROA
192.96.243.0/24RADBNo ROA
196.3.57.0/24RADBNo ROA
196.4.0.0/24RADBNo ROA
196.4.2.0/24RADBNo ROA
196.4.3.0/24RADBNo ROA
196.4.17.0/24RADBNo ROA
196.4.17.0/29RADBNo ROA
196.4.81.0/24RADBNo ROA
196.9.0.0/16RADBNo ROA
196.9.3.0/24RADBNo ROA
196.9.10.0/24RADBNo ROA
196.9.32.0/20RADBNo ROA
196.9.48.0/21RADBNo ROA
196.9.94.0/24RADBNo ROA
196.9.108.0/24RADBNo ROA
196.9.119.0/24RADBNo ROA
196.9.137.0/24RADBNo ROA
196.9.157.0/24RADBNo ROA
196.9.161.0/24RADBNo ROA
196.9.162.0/24RADBNo ROA
196.9.163.0/24RADBNo ROA
196.9.164.0/24RADBNo ROA
196.9.165.0/24RADBNo ROA
196.9.166.0/24RADBNo ROA
196.9.182.0/24RADBNo ROA
196.9.183.0/24RADBNo ROA
196.9.199.0/24RADBNo ROA
196.9.200.0/24RADBNo ROA
196.9.201.0/24RADBNo ROA
196.9.203.0/24RADBNo ROA
196.9.204.0/22RADBNo ROA
196.9.209.0/24RADBNo ROA
196.9.210.0/24RADBNo ROA
196.9.211.0/24RADBNo ROA
196.9.212.0/24RADBNo ROA
196.9.214.0/24RADBNo ROA
196.9.218.0/24RADBNo ROA
196.9.222.0/24RADBNo ROA
196.9.224.0/24RADBNo ROA
196.9.231.0/24RADBNo ROA
196.9.235.0/24RADBNo ROA
196.9.236.0/24RADBNo ROA
196.9.239.0/24RADBNo ROA
196.9.240.0/24RADBNo ROA
196.9.241.0/24RADBNo ROA
196.9.243.0/24RADBNo ROA
196.9.244.0/24RADBNo ROA
196.9.245.0/24RADBNo ROA
196.9.250.0/24RADBNo ROA
196.9.252.0/24RADBNo ROA
196.9.253.0/24RADBNo ROA
196.9.254.0/24RADBNo ROA
196.9.255.0/24RADBNo ROA
196.13.126.0/24RADBNo ROA
196.13.127.0/24RADBNo ROA
196.13.129.0/24RADBNo ROA
196.13.131.0/24RADBNo ROA
196.13.144.0/24RADBNo ROA
196.13.147.0/24RADBNo ROA
196.43.204.0/24RADBNo ROA
196.43.208.0/24RADBNo ROA
196.46.23.0/24RADBNo ROA
196.46.30.0/24RADBNo ROA
196.216.172.0/22RADBNo ROA
196.216.172.0/24RADBNo ROA
196.216.173.0/24RADBNo ROA
196.216.174.0/24RADBNo ROA
196.216.175.0/24RADBNo ROA
196.216.236.0/23RADBNo ROA
197.255.240.0/22RADBNo ROA
198.54.1.0/24RADBNo ROA
198.54.2.0/24RADBNo ROA
198.54.3.0/24RADBNo ROA
198.54.4.0/22RADBNo ROA
198.54.7.0/24RADBNo ROA
198.54.8.0/24RADBNo ROA
198.54.9.0/24RADBNo ROA
198.54.10.0/24RADBNo ROA
202.183.73.0/24APNICValid
208.67.232.0/21RADBNo ROA
209.131.96.0/20RADBNo ROA
209.131.99.0/24RADBNo ROA
213.247.0.0/21RADBNo ROA
213.247.8.0/24RADBNo 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.