Network · data from 2026-11-12
AS397151 DC2-AS - Trans Union, LLC
Registry name: DC2-AS - Trans Union, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS397151, 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.
| 207.201.214.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 66.175.248.0/22 | Valid | Nonecovered by 66.175.240.0/20 | 672 100% |
| 66.175.248.0/23 | Valid | RIR databaseARIN | 673 100% |
| 66.175.250.0/24 | Valid | RIR databaseARIN | 673 100% |
| 198.47.91.0/24 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS397151 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 5 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 207.201.214.0/24 | No ROA covers it. Add a ROA for AS397151, maxLength 24. |
| Route object: none | 66.175.248.0/22 | No route object for it. A route object for 66.175.240.0/20 with origin AS397151 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397151 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS397151 whose prefix no peer sees AS397151 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.175.240.0/20 | ARIN | Valid |
| 172.83.72.0/21 | ARIN | No ROA |
| 198.47.90.0/23 | ARIN | Valid |
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.