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

AS59589 ·

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

Warning: AS59589 (KA2 LLC KA-2) announces 2 IPv4 and 1 IPv6 prefixes. 1 warning

AS pageAS59589
HolderKA2 LLC KA-2
AllocationRIPE NCC, Russia (RU), allocated 2020-03-16
Prefixes (IPv4 / IPv6)2 / 1
RPKI valid100% (3 / 3)
Upstreams and peers22

What to fix

  1. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI AS59589 announces 2 IPv4 and 1 IPv6 prefixes.
  • Pass: AS59589 announces 2 IPv4 and 1 IPv6 prefixes.
  • Pass: All 3 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 22 upstreams and peers, 8 downstream networks seen.
HolderKA2 LLC KA-2
IPv4 prefixes2
IPv6 prefixes1
RPKI3 valid
Downstream networks8

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.
NameKA2
HandleAS59589
RangeAS59589
Statusactive
Registered2020-03-16T14:47:55Z
Last changed2025-07-20T11:05:44Z
Abuse contacthd@ka-2.pro
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2020-03-16
StatusAllocated
Delegated rangeAS59589

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

Contacts
RoleNameEmail
registrant lir-ru-ka2-1-MNT
registrant LLC KA-2
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role hd@ka-2.pro

Source: https://rdap.db.ripe.net/autnum/59589. 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 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