bgpreport

Network · data from 2026-11-12

AS394456 EPIK-LLC - Epik LLC

Registry name: EPIK-LLC - Epik LLC, US · not in PeeringDB

14IPv4 routes 35.7% RPKI valid · 21.4% with a route object
2IPv6 routes 100.0% RPKI valid · 50.0% with a route object
4RPKI invalid 4 origin · 0 maxLength
5No ROA 12 with no route object for this origin
11Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS394456, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS394456, 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.

66.223.101.0/24 Invalid: origin None 3 0%low visibility 3
66.223.102.0/24 Invalid: origin None 3 0%low visibility 3
66.223.103.0/24 Invalid: origin None 3 0%low visibility 3
66.223.100.0/24 Invalid: origin None 2 0%low visibility 2
66.223.12.0/24 No ROA None 2 0%low visibility 2
66.223.13.0/24 No ROA None 2 0%low visibility 2
66.223.14.0/24 No ROA None 2 0%low visibility 2
66.223.15.0/24 No ROA None 2 0%low visibility 2
66.223.61.0/24 No ROA None 2 0%low visibility 2
209.196.146.0/24 Valid Nonecovered by 209.196.146.0/23 673 100% 67
209.196.147.0/24 Valid Nonecovered by 209.196.146.0/23 673 100% 67
2607:b6c0:6701::/48 Valid Nonecovered by 2607:b6c0::/32 3 0%low visibility 3
66.223.49.0/24 Valid RIR databaseARIN 673 100% 67
209.196.144.0/24 Valid RIR databaseARIN 673 100% 67
2607:b6c0::/32 Valid RIR databaseARIN 635 100% 67
185.83.214.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS394456 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 22 are in fix.csv.

  • ROA: origin4
  • ROA: none5
  • Route object: none12
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin66.223.101.0/24ROAs covering it name AS46572, not AS394456. If AS394456 should announce it, add a ROA for AS394456.3 of 673
Route object: none66.223.101.0/24No route object for it. Add a route object with origin AS394456 in the RIR database for the space.3 of 673
ROA: origin66.223.102.0/24ROAs covering it name AS46572, not AS394456. If AS394456 should announce it, add a ROA for AS394456.3 of 673
Route object: none66.223.102.0/24No route object for it. Add a route object with origin AS394456 in the RIR database for the space.3 of 673
ROA: origin66.223.103.0/24ROAs covering it name AS46572, not AS394456. If AS394456 should announce it, add a ROA for AS394456.3 of 673
Route object: none66.223.103.0/24No route object for it. Add a route object with origin AS394456 in the RIR database for the space.3 of 673
ROA: origin66.223.100.0/24ROAs covering it name AS46572, not AS394456. If AS394456 should announce it, add a ROA for AS394456.2 of 673
Route object: none66.223.100.0/24No route object for it. Add a route object with origin AS394456 in the RIR database for the space.2 of 673
ROA: none66.223.12.0/24No ROA covers it. Add a ROA for AS394456, maxLength 24.2 of 673
Route object: none66.223.12.0/24No route object for it. Add a route object with origin AS394456 in the RIR database for the space.2 of 673
ROA: none66.223.13.0/24No ROA covers it. Add a ROA for AS394456, maxLength 24.2 of 673
Route object: none66.223.13.0/24No route object for it. Add a route object with origin AS394456 in the RIR database for the space.2 of 673
ROA: none66.223.14.0/24No ROA covers it. Add a ROA for AS394456, maxLength 24.2 of 673
Route object: none66.223.14.0/24No route object for it. Add a route object with origin AS394456 in the RIR database for the space.2 of 673
ROA: none66.223.15.0/24No ROA covers it. Add a ROA for AS394456, maxLength 24.2 of 673
Route object: none66.223.15.0/24No route object for it. Add a route object with origin AS394456 in the RIR database for the space.2 of 673
ROA: none66.223.61.0/24No ROA covers it. Add a ROA for AS394456, maxLength 24.2 of 673
Route object: none66.223.61.0/24No route object for it. Add a route object with origin AS394456 in the RIR database for the space.2 of 673
Route object: none209.196.146.0/24No route object for it. A route object for 209.196.146.0/23 with origin AS394456 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394456 in the RIR database for the space.673 of 673
Route object: none209.196.147.0/24No route object for it. A route object for 209.196.146.0/23 with origin AS394456 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394456 in the RIR database for the space.673 of 673
Route object: none2607:b6c0:6701::/48No route object for it. A route object for 2607:b6c0::/32 with origin AS394456 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394456 in the RIR database for the space.3 of 636

Route objects not announced

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

209.196.146.0/23ARINValid

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.