bgpreport

Network · data from 2026-11-12

AS21734 Trading Technologies Intl

Registry name: TRADINGTECH-TTNET - Trading Technologies Intl, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21734, 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.
64.95.191.0/24 No ROA Other IRR onlyRADB 672 100% 67
160.72.217.0/24 No ROA Other IRR onlyRADB 672 100% 66
64.124.221.0/24 Valid Other IRR onlyRADB 673 100% 67
128.177.160.0/24 Valid Other IRR onlyRADB 673 100% 67
95.172.76.0/24 Valid Other IRR onlyRADB 672 100% 67
195.122.186.0/24 Valid Other IRR onlyRADB 672 100% 66
208.50.27.0/24 Valid Other IRR onlyRADB 672 100% 66
207.218.154.0/24 Valid Other IRR onlyRADB 669 99% 67
64.74.225.0/24 Valid RIR databaseARIN, RADB 673 100% 66
69.25.152.0/24 Valid RIR databaseARIN, RADB 673 100% 66
103.99.4.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.99.5.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.99.6.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.99.7.0/24 Valid RIR databaseAPNIC 673 100% 67
103.196.141.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.196.142.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.196.143.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
74.201.141.0/24 Valid RIR databaseARIN, RADB 672 100% 66
74.201.251.0/24 Valid RIR databaseARIN 672 100% 66
61.90.251.0/24 Valid RIR databaseAPNIC, RADB 670 100% 69
83.126.50.0/24 Valid RIR databaseRIPE 670 100% 67
103.196.140.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67

AS-SET

AS21734'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.

  • ROA: none2
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none64.95.191.0/24No ROA covers it. Add a ROA for AS21734, maxLength 24.672 of 673
Route object: RIR64.95.191.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none160.72.217.0/24No ROA covers it. Add a ROA for AS21734, maxLength 24.672 of 673
Route object: RIR160.72.217.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR64.124.221.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR128.177.160.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR95.172.76.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR195.122.186.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR208.50.27.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR207.218.154.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

64.191.2.0/24RADBNo ROA
111.221.56.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.