bgpreport

Network · data from 2026-11-12

AS14102 GTVR - Transvision Reseau Inc.

Registry name: GTVR - Transvision Reseau Inc., CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14102, 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.
96.43.224.0/20 No ROA Other IRR onlyRADB 670 100% 67
198.246.28.0/22 No ROA Other IRR onlyRADB 670 100% 67
206.41.82.0/24 No ROA Other IRR onlyRADB 670 100% 67
206.41.83.0/24 No ROA Other IRR onlyRADB 670 100% 67
206.41.84.0/24 No ROA Other IRR onlyRADB 670 100% 67
206.41.85.0/24 No ROA Other IRR onlyRADB 670 100% 67
206.41.86.0/24 No ROA Other IRR onlyRADB 670 100% 67
209.222.224.0/20 No ROA Other IRR onlyRADB 670 100% 67

AS-SET

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

  • ROA: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none96.43.224.0/20No ROA covers it. Add a ROA for AS14102, maxLength 20.670 of 673
Route object: RIR96.43.224.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none198.246.28.0/22No ROA covers it. Add a ROA for AS14102, maxLength 22.670 of 673
Route object: RIR198.246.28.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none206.41.82.0/24No ROA covers it. Add a ROA for AS14102, maxLength 24.670 of 673
Route object: RIR206.41.82.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none206.41.83.0/24No ROA covers it. Add a ROA for AS14102, maxLength 24.670 of 673
Route object: RIR206.41.83.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none206.41.84.0/24No ROA covers it. Add a ROA for AS14102, maxLength 24.670 of 673
Route object: RIR206.41.84.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none206.41.85.0/24No ROA covers it. Add a ROA for AS14102, maxLength 24.670 of 673
Route object: RIR206.41.85.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none206.41.86.0/24No ROA covers it. Add a ROA for AS14102, maxLength 24.670 of 673
Route object: RIR206.41.86.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none209.222.224.0/20No ROA covers it. Add a ROA for AS14102, maxLength 20.670 of 673
Route object: RIR209.222.224.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS14102 is announced.

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.