bgpreport

Network · data from 2026-11-12

AS397893 OTZ-1 - OTZ Telecommunications, LLC

Registry name: OTZ-1 - OTZ Telecommunications, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS397893, 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.
64.178.240.0/24 No ROA None 2 0%low visibility 2
74.127.72.0/24 No ROA None 2 0%low visibility 2
74.127.73.0/24 No ROA None 2 0%low visibility 2
216.163.106.0/24 No ROA Nonecovered by 216.163.106.0/23 2 0%low visibility 2
216.198.123.0/24 No ROA None 2 0%low visibility 2
117.55.197.0/24 No ROA RIR databaseARIN 671 100% 68
117.55.196.0/24 No ROA RIR databaseARIN 670 100% 68

AS-SET

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

  • ROA: none7
  • Route object: none5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none64.178.240.0/24No ROA covers it. Add a ROA for AS397893, maxLength 24.2 of 673
Route object: none64.178.240.0/24No route object for it. Add a route object with origin AS397893 in the RIR database for the space.2 of 673
ROA: none74.127.72.0/24No ROA covers it. Add a ROA for AS397893, maxLength 24.2 of 673
Route object: none74.127.72.0/24No route object for it. Add a route object with origin AS397893 in the RIR database for the space.2 of 673
ROA: none74.127.73.0/24No ROA covers it. Add a ROA for AS397893, maxLength 24.2 of 673
Route object: none74.127.73.0/24No route object for it. Add a route object with origin AS397893 in the RIR database for the space.2 of 673
ROA: none216.163.106.0/24No ROA covers it. Add a ROA for AS397893, maxLength 24.2 of 673
Route object: none216.163.106.0/24No route object for it. A route object for 216.163.106.0/23 with origin AS397893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397893 in the RIR database for the space.2 of 673
ROA: none216.198.123.0/24No ROA covers it. Add a ROA for AS397893, maxLength 24.2 of 673
Route object: none216.198.123.0/24No route object for it. Add a route object with origin AS397893 in the RIR database for the space.2 of 673
ROA: none117.55.197.0/24No ROA covers it. Add a ROA for AS397893, maxLength 24.671 of 673
ROA: none117.55.196.0/24No ROA covers it. Add a ROA for AS397893, maxLength 24.670 of 673

Route objects not announced

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

117.55.196.0/23ARINNo ROA
216.163.106.0/23RADBNo ROA
216.163.116.0/23RADBNo 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.