bgpreport

Network · data from 2026-11-12

AS57394 EPIC-NETWORKS-AS EPIC NETWORKS S.R.L.

Registry name: EPIC-NETWORKS-AS EPIC NETWORKS S.R.L., IT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57394, 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.
185.44.220.0/22 No ROA RIR databaseRIPE 673 100% 66
193.150.60.0/22 No ROA RIR databaseRIPE 673 100% 66
2a03:91c0::/32 No ROA RIR databaseRIPE 635 100% 67

AS-SET

AS57394 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: none3
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none185.44.220.0/22No ROA covers it. Add a ROA for AS57394, maxLength 22.673 of 673
ROA: none193.150.60.0/22No ROA covers it. Add a ROA for AS57394, maxLength 22.673 of 673
ROA: none2a03:91c0::/32No ROA covers it. Add a ROA for AS57394, maxLength 32.635 of 636

Route objects not announced

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

185.44.220.0/23RIPENo ROA
185.44.220.0/24RIPENo ROA
185.44.221.0/24RIPENo ROA
185.44.222.0/23RIPENo ROA
185.44.222.0/24RIPENo ROA
185.44.223.0/24RIPENo ROA
193.150.60.0/23RIPENo ROA
193.150.60.0/24RIPENo ROA
193.150.61.0/24RIPENo ROA
193.150.62.0/23RIPENo ROA
193.150.62.0/24RIPENo ROA
193.150.63.0/24RIPENo 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.