bgpreport

Network · data from 2026-11-12

AS14112 NET-SECURENET-MTL - SecureNet Information Services

Registry name: NET-SECURENET-MTL - SecureNet Information Services, CA · not in PeeringDB

14IPv4 routes 64.3% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No 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 AS14112, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS14112, 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.
205.205.79.0/24 No ROA Other IRR onlyRADB 672 100% 67
205.236.41.0/24 No ROA Other IRR onlyALTDB, RADB 672 100% 67
205.236.147.0/24 No ROA Other IRR onlyALTDB, RADB 672 100% 67
205.236.150.0/24 No ROA Other IRR onlyALTDB, RADB 672 100% 67
205.236.151.0/24 No ROA Other IRR onlyRADB 672 100% 67
66.38.236.0/22 Valid Other IRR onlyALTDB, RADB 669 99% 67
66.38.236.0/24 Valid Other IRR onlyRADB 669 99% 67
66.38.237.0/24 Valid Other IRR onlyRADB 669 99% 67
66.38.238.0/24 Valid Other IRR onlyRADB 669 99% 67
66.38.239.0/24 Valid Other IRR onlyRADB 669 99% 67
66.201.208.0/24 Valid Other IRR onlyRADB 669 99% 67
216.6.204.0/23 Valid Other IRR onlyALTDB, RADB 669 99% 67
216.18.116.0/23 Valid Other IRR onlyALTDB, RADB 669 99% 67
216.18.122.0/23 Valid Other IRR onlyALTDB, RADB 669 99% 67

AS-SET

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

  • ROA: none5
  • Route object: RIR14
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none205.205.79.0/24No ROA covers it. Add a ROA for AS14112, maxLength 24.672 of 673
Route object: RIR205.205.79.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none205.236.41.0/24No ROA covers it. Add a ROA for AS14112, maxLength 24.672 of 673
Route object: RIR205.236.41.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none205.236.147.0/24No ROA covers it. Add a ROA for AS14112, maxLength 24.672 of 673
Route object: RIR205.236.147.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none205.236.150.0/24No ROA covers it. Add a ROA for AS14112, maxLength 24.672 of 673
Route object: RIR205.236.150.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none205.236.151.0/24No ROA covers it. Add a ROA for AS14112, maxLength 24.672 of 673
Route object: RIR205.236.151.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR66.38.236.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR66.38.236.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR66.38.237.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR66.38.238.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR66.38.239.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR66.201.208.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR216.6.204.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR216.18.116.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR216.18.122.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

64.18.74.0/23ALTDBNo ROA
64.18.76.0/22ALTDBNo 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.