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

AS395839 ·

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

Problem: AS395839 (HOSTKEY-USA) announces 51 IPv4 and 1 IPv6 prefixes. 1 problem · 3 warnings

AS pageAS395839
HolderHOSTKEY-USA - HOSTKEY
AllocationARIN, United States (US), assigned 2017-01-03
Prefixes (IPv4 / IPv6)51 / 1
RPKI valid96% (50 / 52)
Upstreams and peers4
Peering policyOpen

What to fix

  1. Problem

    1 of 52 announced prefixes are RPKI invalid: 191.96.148.0/24.

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 52 announced prefixes have no ROA (RPKI not found): 2604:5940::/32.

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

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

    2604:5940::/32 AS395839 max-length /32

    Open in RPKI / ROA validator Guide

  3. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  4. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI 1 of 52 announced prefixes are RPKI invalid: 191.96.148.0/24.
  • Pass: AS395839 announces 51 IPv4 and 1 IPv6 prefixes.
  • Problem: 1 of 52 announced prefixes are RPKI invalid: 191.96.148.0/24.
  • Warning: 1 of 52 announced prefixes have no ROA (RPKI not found): 2604:5940::/32.
  • Info: 50 of 52 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 4 upstreams and peers, 5 downstream networks seen.
HolderHOSTKEY-USA - HOSTKEY
IPv4 prefixes51
IPv6 prefixes1
RPKI50 valid · 1 invalid · 1 not found
Downstream networks5
Routes to fix
PrefixRPKI
191.96.148.0/24 RPKI invalid
2604:5940::/32 No ROA

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
NameHOSTKEY-USA
HandleAS395839
RangeAS395839
Statusactive
Registered2017-01-03T14:06:50-05:00
Last changed2017-01-03T14:06:50-05:00
Abuse contactabuse@hostkey.us
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2017-01-03
StatusAssigned
Delegated rangeAS395839

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant HOSTKEY

Source: https://rdap.arin.net/registry/autnum/395839. Registration data from rdap.arin.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS395839 is in PeeringDB as HOSTKEY-USA.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkHOSTKEY-USA (HOSTKEY USA, Inc.)
AS numberAS395839
TypeContent, Not Disclosed
Websitehttp://www.hostkey.com
Prefixes (IPv4 / IPv6)0 / 0
Traffic5-10Gbps, Heavy Outbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Looking glasshttp://lg.hostkey.net
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup