Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS57394 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS57394"
JSON Docs

Warning: AS57394 (EPIC-NETWORKS-AS) announces 2 IPv4 and 1 IPv6 prefixes. 2 warnings

AS pageAS57394
HolderEPIC-NETWORKS-AS EPIC NETWORKS S.R.L.
AllocationRIPE NCC, Italy (IT), allocated 2011-10-17
Prefixes (IPv4 / IPv6)2 / 1
RPKI valid0% (0 / 3)
Upstreams and peers2

What to fix

  1. Warning

    3 of 3 announced prefixes have no ROA (RPKI not found): 185.44.220.0/22, 193.150.60.0/22, 2a03:91c0::/32.

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS57394 and a max length equal to the prefix length:

    185.44.220.0/22 AS57394 max-length /22
    193.150.60.0/22 AS57394 max-length /22
    2a03:91c0::/32 AS57394 max-length /32

    Open in RPKI / ROA validator Guide

  2. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 3 of 3 announced prefixes have no ROA (RPKI not found): 185.44.220.0/22, 193.150.60.0/22, 2a03:91c0::/32.
  • Pass: AS57394 announces 2 IPv4 and 1 IPv6 prefixes.
  • Warning: 3 of 3 announced prefixes have no ROA (RPKI not found): 185.44.220.0/22, 193.150.60.0/22, 2a03:91c0::/32.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderEPIC-NETWORKS-AS EPIC NETWORKS S.R.L.
IPv4 prefixes2
IPv6 prefixes1
RPKI3 not found
Downstream networks0
Routes to fix
PrefixRPKI
185.44.220.0/22 No ROA
193.150.60.0/22 No ROA
2a03:91c0::/32 No ROA

Upstreams and peers seen to the left 2

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration The registry is limiting how often it can be asked. Please try again in a minute.
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup