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

AS12764 · 

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

Warning: AS12764 (AKNET-AS AKNET Ltd.) announces 62 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS12764
HolderAKNET-AS AKNET Ltd.
AllocationRIPE NCC, Kyrgyzstan (KG), allocated 1999-10-29
Prefixes (IPv4 / IPv6)62 / 0
RPKI valid0% (0 / 62)
Upstreams and peers1

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    10 of 62 announced prefixes have no ROA (RPKI not found): 31.186.48.0/21, 31.186.48.0/24, 31.186.49.0/24, 31.186.50.0/24, 31.186.53.0/24 (+5).

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

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

    31.186.48.0/21 AS12764 max-length /21
31.186.48.0/24 AS12764 max-length /24
31.186.49.0/24 AS12764 max-length /24
31.186.50.0/24 AS12764 max-length /24
31.186.53.0/24 AS12764 max-length /24
31.186.54.0/24 AS12764 max-length /24
31.186.55.0/24 AS12764 max-length /24
185.29.184.0/22 AS12764 max-length /22
185.29.184.0/24 AS12764 max-length /24
185.29.185.0/24 AS12764 max-length /24

    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 No IPv6 prefixes announced.
  • Pass: AS12764 announces 62 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 10 of 62 announced prefixes have no ROA (RPKI not found): 31.186.48.0/21, 31.186.48.0/24, 31.186.49.0/24, 31.186.50.0/24, 31.186.53.0/24 (+5).
  • Info: The RPKI state of 52 prefixes was not looked up (no ROA of AS12764 covers them; only the first 10 are checked).
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS8449): an outage there takes the whole network off the internet.
HolderAKNET-AS AKNET Ltd.
IPv4 prefixes62
IPv6 prefixes0
RPKI10 not found · 52 not looked up
Downstream networks12
Routes to fix
PrefixRPKI
31.186.48.0/21 No ROA
31.186.48.0/24 No ROA
31.186.49.0/24 No ROA
31.186.50.0/24 No ROA
31.186.53.0/24 No ROA
31.186.54.0/24 No ROA
31.186.55.0/24 No ROA
185.29.184.0/22 No ROA
185.29.184.0/24 No ROA
185.29.185.0/24 No ROA

Upstreams and peers seen to the left 1

AS8449 ElCat AS8449

Announced prefixes 62

31.186.48.0/21 31.186.48.0/24 31.186.49.0/24 31.186.50.0/24 31.186.53.0/24 31.186.54.0/24 31.186.55.0/24 185.29.184.0/22 185.29.184.0/24 185.29.185.0/24 185.29.186.0/24 185.29.187.0/24 212.112.96.0/19 212.112.96.0/20 212.112.96.0/22 212.112.96.0/24 212.112.97.0/24 212.112.98.0/24 212.112.99.0/24 212.112.100.0/24 212.112.101.0/24 212.112.102.0/24 212.112.103.0/24 212.112.104.0/24 212.112.105.0/24 212.112.106.0/24 212.112.107.0/24 212.112.108.0/24 212.112.109.0/24 212.112.110.0/24 212.112.111.0/24 212.112.112.0/20 212.112.112.0/21 212.112.112.0/22 212.112.112.0/24 212.112.113.0/24 212.112.114.0/24 212.112.115.0/24 212.112.116.0/22 212.112.116.0/24 212.112.117.0/24 212.112.118.0/23 212.112.118.0/24 212.112.119.0/24 212.112.120.0/22 212.112.120.0/24 212.112.121.0/24 212.112.122.0/24 212.112.123.0/24 212.112.124.0/22 212.112.124.0/24 212.112.125.0/24 212.112.126.0/24 212.112.127.0/24 213.109.64.0/21 213.109.64.0/24 213.109.65.0/24 213.109.66.0/24 213.109.67.0/24 213.109.68.0/24 213.109.69.0/24 213.109.71.0/24

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameAKNET-AS
HandleAS12764
RangeAS12764
Statusactive
Registered1970-01-01T00:00:00Z
Last changed2017-11-15T09:15:05Z
Abuse contactripe@aknet.kg
Allocation
Registry (RIR)RIPE NCC
CountryKyrgyzstan (KG)
Delegated on1999-10-29
StatusAllocated
Delegated rangeAS12764

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

Contacts
RoleNameEmail
registrant AS12764-MNT
registrant AKNET Ltd.
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role ripe@aknet.kg

Source: https://rdap.db.ripe.net/autnum/12764. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS12764 is in PeeringDB as AKNET.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
NetworkAKNET
AS numberAS12764
Type, Not Disclosed
TrafficNot Disclosed
Ratio requiredNo
Last updated2026-06-09

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup