bgpreport

Network · data from 2026-11-12

AS12273 TRUELINK - Transunion Interactive, Inc.

Registry name: TRUELINK - Transunion Interactive, Inc., US · not in PeeringDB

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

Announced routes

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

199.21.170.0/23 No ROA Nonecovered by 199.21.168.0/22 672 100% 67
74.117.130.0/23 No ROA Nonecovered by 74.117.128.0/22 671 100% 67
199.21.168.0/23 No ROA Nonecovered by 199.21.168.0/22 671 100% 67
74.117.128.0/23 No ROA Other IRR onlyALTDB 672 100% 67
199.21.168.0/24 No ROA RIR databaseARIN 672 100% 70
199.21.169.0/24 No ROA RIR databaseARIN 672 100% 70
199.21.170.0/24 No ROA RIR databaseARIN 672 100% 70
199.21.171.0/24 No ROA RIR databaseARIN 672 100% 70
74.117.128.0/24 No ROA RIR databaseARIN 671 100% 70
74.117.129.0/24 No ROA RIR databaseARIN 671 100% 70
74.117.130.0/24 No ROA RIR databaseARIN 671 100% 70
74.117.131.0/24 No ROA RIR databaseARIN 671 100% 70

AS-SET

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

  • ROA: none12
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none199.21.170.0/23No ROA covers it. Add a ROA for AS12273, maxLength 23.672 of 673
Route object: none199.21.170.0/23No route object for it. A route object for 199.21.168.0/22 with origin AS12273 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12273 in the RIR database for the space.672 of 673
ROA: none74.117.130.0/23No ROA covers it. Add a ROA for AS12273, maxLength 23.671 of 673
Route object: none74.117.130.0/23No route object for it. A route object for 74.117.128.0/22 with origin AS12273 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12273 in the RIR database for the space.671 of 673
ROA: none199.21.168.0/23No ROA covers it. Add a ROA for AS12273, maxLength 23.671 of 673
Route object: none199.21.168.0/23No route object for it. A route object for 199.21.168.0/22 with origin AS12273 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12273 in the RIR database for the space.671 of 673
ROA: none74.117.128.0/23No ROA covers it. Add a ROA for AS12273, maxLength 23.672 of 673
Route object: RIR74.117.128.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none199.21.168.0/24No ROA covers it. Add a ROA for AS12273, maxLength 24.672 of 673
ROA: none199.21.169.0/24No ROA covers it. Add a ROA for AS12273, maxLength 24.672 of 673
ROA: none199.21.170.0/24No ROA covers it. Add a ROA for AS12273, maxLength 24.672 of 673
ROA: none199.21.171.0/24No ROA covers it. Add a ROA for AS12273, maxLength 24.672 of 673
ROA: none74.117.128.0/24No ROA covers it. Add a ROA for AS12273, maxLength 24.671 of 673
ROA: none74.117.129.0/24No ROA covers it. Add a ROA for AS12273, maxLength 24.671 of 673
ROA: none74.117.130.0/24No ROA covers it. Add a ROA for AS12273, maxLength 24.671 of 673
ROA: none74.117.131.0/24No ROA covers it. Add a ROA for AS12273, maxLength 24.671 of 673

Route objects not announced

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

74.117.128.0/22ALTDBNo ROA
199.21.168.0/22ALTDBNo ROA
206.159.99.0/24ALTDBNo 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.