bgpreport

Network · data from 2026-11-12

AS395948 EFI-NTX - ELEKTRAFI INC.

Registry name: EFI-NTX - ELEKTRAFI INC., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS395948, 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.
23.165.128.0/24 No ROA Other origin only 2 0%low visibility 2
38.65.70.0/24 No ROA RIR databaseARIN, NTTCOM 670 100% 68
38.65.71.0/24 No ROA RIR databaseARIN, NTTCOM 670 100% 68
38.65.72.0/22 No ROA RIR databaseARIN, NTTCOM 670 100% 68
38.65.76.0/22 No ROA RIR databaseARIN, NTTCOM 670 100% 68
38.96.224.0/22 No ROA RIR databaseARIN, NTTCOM 670 100% 68
38.96.228.0/22 No ROA RIR databaseARIN, NTTCOM 670 100% 68
38.123.124.0/22 No ROA RIR databaseARIN, NTTCOM 670 100% 68
38.134.12.0/22 No ROA RIR databaseARIN, NTTCOM 670 100% 68
38.135.40.0/22 No ROA RIR databaseARIN, NTTCOM 670 100% 68
172.99.252.0/22 Valid RIR databaseARIN, NTTCOM 670 100% 68

AS-SET

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

  • ROA: none10
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none23.165.128.0/24No ROA covers it. Add a ROA for AS395948, maxLength 24.2 of 673
Route object: none23.165.128.0/24Route objects for it name AS5650, AS400097. Add a route object with origin AS395948 in the RIR database for the space.2 of 673
ROA: none38.65.70.0/24No ROA covers it. Add a ROA for AS395948, maxLength 24.670 of 673
ROA: none38.65.71.0/24No ROA covers it. Add a ROA for AS395948, maxLength 24.670 of 673
ROA: none38.65.72.0/22No ROA covers it. Add a ROA for AS395948, maxLength 22.670 of 673
ROA: none38.65.76.0/22No ROA covers it. Add a ROA for AS395948, maxLength 22.670 of 673
ROA: none38.96.224.0/22No ROA covers it. Add a ROA for AS395948, maxLength 22.670 of 673
ROA: none38.96.228.0/22No ROA covers it. Add a ROA for AS395948, maxLength 22.670 of 673
ROA: none38.123.124.0/22No ROA covers it. Add a ROA for AS395948, maxLength 22.670 of 673
ROA: none38.134.12.0/22No ROA covers it. Add a ROA for AS395948, maxLength 22.670 of 673
ROA: none38.135.40.0/22No ROA covers it. Add a ROA for AS395948, maxLength 22.670 of 673

Route objects not announced

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

38.65.79.0/24NTTCOMNo 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.