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

AS27448 · 

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

Warning: AS27448 (KAYENTA) announces 2 IPv4 and 1 IPv6 prefixes. 3 warnings

AS pageAS27448
HolderKAYENTA - Kayenta Technologies
AllocationARIN, United States (US), assigned 2013-07-09
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): 162.217.76.0/22, 162.217.78.0/23, 2607:9640::/32.

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

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

    162.217.76.0/22 AS27448 max-length /22
162.217.78.0/23 AS27448 max-length /23
2607:9640::/32 AS27448 max-length /32

    Open in RPKI / ROA validator Guide

  2. 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

  3. 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 3 of 3 announced prefixes have no ROA (RPKI not found): 162.217.76.0/22, 162.217.78.0/23, 2607:9640::/32.
  • Pass: AS27448 announces 2 IPv4 and 1 IPv6 prefixes.
  • Warning: 3 of 3 announced prefixes have no ROA (RPKI not found): 162.217.76.0/22, 162.217.78.0/23, 2607:9640::/32.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderKAYENTA - Kayenta Technologies
IPv4 prefixes2
IPv6 prefixes1
RPKI3 not found
Downstream networks0
Routes to fix
PrefixRPKI
162.217.76.0/22 No ROA
162.217.78.0/23 No ROA
2607:9640::/32 No ROA

Upstreams and peers seen to the left 2

AS174 Cogent Communications, Inc. AS11071 InfoWest

Announced prefixes 3

162.217.76.0/22 162.217.78.0/23 2607:9640::/32

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.
NameKAYENTA
HandleAS27448
RangeAS27448
Statusactive
Registered2013-07-09T17:37:28-04:00
Last changed2016-05-20T01:09:09-04:00
Abuse contactabuse@kayenta.net
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2013-07-09
StatusAssigned
Delegated rangeAS27448

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

Contacts
RoleNameEmail
registrant Kayenta Technologies

Source: https://rdap.arin.net/registry/autnum/27448. 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: AS27448 is in PeeringDB as Kayenta Technologies.
  • 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.
NetworkKayenta Technologies
AS numberAS27448
Type, Not Disclosed
Websitehttp://kayenta.net
TrafficNot Disclosed
Ratio requiredNo
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup