bgpreport

Network · data from 2026-11-12

AS17887 TCC Technology/ISP

Registry name: TCCT-AS-TH-AP - T.C.C. Technology Co., Ltd., TH · PeeringDB

39IPv4 routes 100.0% RPKI valid · 100.0% with a route object
6IPv6 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
1Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS17887, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17887, 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.
202.60.196.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
202.60.198.0/24 Valid Other IRR onlyRADB 673 100% 68
202.60.200.0/21 Valid Other IRR onlyNTTCOM 673 100% 68
202.60.200.0/22 Valid Other IRR onlyRADB 673 100% 68
202.60.200.0/24 Valid Other IRR onlyRADB 673 100% 68
202.60.203.0/24 Valid Other IRR onlyRADB 673 100% 68
202.60.204.0/22 Valid Other IRR onlyRADB 673 100% 68
202.60.205.0/24 Valid Other IRR onlyRADB 673 100% 68
43.247.56.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
43.247.56.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
43.247.57.0/24 Valid RIR databaseAPNIC 673 100% 68
103.11.12.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
103.106.8.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
103.106.8.0/24 Valid RIR databaseAPNIC 673 100% 68
103.213.204.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
103.213.204.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.213.205.0/24 Valid RIR databaseAPNIC 673 100% 68
202.60.192.0/21 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
202.60.192.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
202.60.195.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
202.60.199.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
202.60.204.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
202.60.207.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.159.72.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
203.159.96.0/19 Valid RIR databaseAPNIC, RADB 673 100% 68
203.159.96.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.159.100.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.159.101.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.159.103.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.159.104.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.159.107.0/24 Valid RIR databaseAPNIC 673 100% 68
203.159.111.0/24 Valid RIR databaseAPNIC 673 100% 68
203.159.112.0/24 Valid RIR databaseAPNIC 673 100% 68
203.159.120.0/24 Valid RIR databaseAPNIC 673 100% 68
203.159.124.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.159.125.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.159.126.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.159.127.0/24 Valid RIR databaseAPNIC 673 100% 68
2405:6d00::/32 Valid RIR databaseAPNIC 636 100% 69
2405:6d00:104::/48 Valid RIR databaseAPNIC, RADB 636 100% 69
2405:6d00:105::/48 Valid RIR databaseAPNIC 636 100% 69
2405:6d00:106::/48 Valid RIR databaseAPNIC 636 100% 69
2405:6d00:100::/48 Valid RIR databaseAPNIC 317 50% 63
2405:6d00:101::/48 Valid RIR databaseAPNIC 317 50% 63
103.106.10.0/24 Valid RIR databaseAPNIC 3 0%low visibility 3

AS-SET

AS17887'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 14 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: RIR202.60.196.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.60.198.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.60.200.0/21Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.60.200.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.60.200.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.60.203.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.60.204.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.60.205.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

202.60.192.0/20APNICValid
203.159.72.0/24APNIC, RADBValid
203.159.73.0/24APNIC, RADBValid
203.159.74.0/24APNIC, RADBValid
203.159.75.0/24APNIC, RADBValid
203.159.108.0/24APNICValid

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.