bgpreport

Network · data from 2026-11-12

AS19353 TUASN7 - Trans Union, LLC

Registry name: TUASN7 - Trans Union, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19353, 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.
65.201.27.0/24 No ROA RIR databaseARIN 673 100% 70
65.204.34.0/24 No ROA RIR databaseARIN 673 100% 70
66.175.240.0/22 Valid Nonecovered by 66.175.240.0/20 672 100% 67
66.175.244.0/22 Valid Nonecovered by 66.175.240.0/20 672 100% 67
66.175.240.0/23 Valid RIR databaseARIN 673 100% 70
66.175.242.0/23 Valid RIR databaseARIN 673 100% 70
66.175.244.0/23 Valid RIR databaseARIN 673 100% 70
66.175.247.0/24 Valid RIR databaseARIN 673 100% 70
198.47.90.0/24 Valid RIR databaseARIN 673 100% 70

AS-SET

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

  • ROA: none2
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none65.201.27.0/24No ROA covers it. Add a ROA for AS19353, maxLength 24.673 of 673
ROA: none65.204.34.0/24No ROA covers it. Add a ROA for AS19353, maxLength 24.673 of 673
Route object: none66.175.240.0/22No route object for it. A route object for 66.175.240.0/20 with origin AS19353 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19353 in the RIR database for the space.672 of 673
Route object: none66.175.244.0/22No route object for it. A route object for 66.175.240.0/20 with origin AS19353 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19353 in the RIR database for the space.672 of 673

Route objects not announced

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

66.175.240.0/20ARINValid
172.83.72.0/21ARINNo ROA
198.47.90.0/23ARINValid

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.