bgpreport

Network · data from 2026-11-12

AS13893 EHI-NA-AS-1 - Enterprise Holdings, Inc.

Registry name: EHI-NA-AS-1 - Enterprise Holdings, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13893, 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.
77.111.200.0/24 No ROA Nonecovered by 77.111.200.0/23 671 100% 67
77.111.201.0/24 No ROA Nonecovered by 77.111.200.0/23 671 100% 67
2620:103:e001::/48 No ROA None 636 100% 67
2620:103:e002::/48 No ROA None 636 100% 67
2620:103:e019::/48 No ROA None 636 100% 67
2620:103:e029::/48 No ROA None 636 100% 67
2620:103:e0f9::/48 No ROA None 636 100% 67
65.116.51.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
65.197.19.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
65.207.197.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
208.47.116.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
148.78.92.0/24 No ROA RIR databaseARIN 672 100% 67
148.78.93.0/24 No ROA RIR databaseARIN 672 100% 67
148.78.95.0/24 No ROA RIR databaseARIN 672 100% 67
148.78.75.0/24 No ROA RIR databaseARIN 670 100% 67

AS-SET

AS13893 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 29 are in fix.csv.

  • ROA: none15
  • Route object: none7
  • Route object: RIR4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none77.111.200.0/24No ROA covers it. Add a ROA for AS13893, maxLength 24.671 of 673
Route object: none77.111.200.0/24No route object for it. A route object for 77.111.200.0/23 with origin AS13893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13893 in the RIR database for the space.671 of 673
ROA: none77.111.201.0/24No ROA covers it. Add a ROA for AS13893, maxLength 24.671 of 673
Route object: none77.111.201.0/24No route object for it. A route object for 77.111.200.0/23 with origin AS13893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13893 in the RIR database for the space.671 of 673
ROA: none2620:103:e001::/48No ROA covers it. Add a ROA for AS13893, maxLength 48.636 of 636
Route object: none2620:103:e001::/48No route object for it. Add a route object with origin AS13893 in the RIR database for the space.636 of 636
ROA: none2620:103:e002::/48No ROA covers it. Add a ROA for AS13893, maxLength 48.636 of 636
Route object: none2620:103:e002::/48No route object for it. Add a route object with origin AS13893 in the RIR database for the space.636 of 636
ROA: none2620:103:e019::/48No ROA covers it. Add a ROA for AS13893, maxLength 48.636 of 636
Route object: none2620:103:e019::/48No route object for it. Add a route object with origin AS13893 in the RIR database for the space.636 of 636
ROA: none2620:103:e029::/48No ROA covers it. Add a ROA for AS13893, maxLength 48.636 of 636
Route object: none2620:103:e029::/48No route object for it. Add a route object with origin AS13893 in the RIR database for the space.636 of 636
ROA: none2620:103:e0f9::/48No ROA covers it. Add a ROA for AS13893, maxLength 48.636 of 636
Route object: none2620:103:e0f9::/48No route object for it. Add a route object with origin AS13893 in the RIR database for the space.636 of 636
ROA: none65.116.51.0/24No ROA covers it. Add a ROA for AS13893, maxLength 24.672 of 673
Route object: RIR65.116.51.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none65.197.19.0/24No ROA covers it. Add a ROA for AS13893, maxLength 24.672 of 673
Route object: RIR65.197.19.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none65.207.197.0/24No ROA covers it. Add a ROA for AS13893, maxLength 24.672 of 673
Route object: RIR65.207.197.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none208.47.116.0/24No ROA covers it. Add a ROA for AS13893, maxLength 24.672 of 673
Route object: RIR208.47.116.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none148.78.92.0/24No ROA covers it. Add a ROA for AS13893, maxLength 24.672 of 673
ROA: none148.78.93.0/24No ROA covers it. Add a ROA for AS13893, maxLength 24.672 of 673
ROA: none148.78.95.0/24No ROA covers it. Add a ROA for AS13893, maxLength 24.672 of 673
ROA: none148.78.75.0/24No ROA covers it. Add a ROA for AS13893, maxLength 24.670 of 673

Route objects not announced

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

63.76.126.0/24NTTCOMNo ROA
77.111.200.0/23RIPENo ROA
148.78.94.0/24ARINNo 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.