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

AS34251 ·

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

Warning: AS34251 (IMC-AS LLC IMC) announces 23 IPv4 and 0 IPv6 prefixes. 2 warnings

AS pageAS34251
HolderIMC-AS LLC IMC
AllocationRIPE NCC, Ukraine (UA), allocated 2004-11-26
Prefixes (IPv4 / IPv6)23 / 0
RPKI valid0% (0 / 23)
Upstreams and peers21
Peering policyOpen

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 23 announced prefixes have no ROA (RPKI not found): 46.175.16.0/21, 46.175.16.0/22, 46.175.16.0/24, 46.175.17.0/24, 46.175.18.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 AS34251 and a max length equal to the prefix length:

    46.175.16.0/21 AS34251 max-length /21
    46.175.16.0/22 AS34251 max-length /22
    46.175.16.0/24 AS34251 max-length /24
    46.175.17.0/24 AS34251 max-length /24
    46.175.18.0/24 AS34251 max-length /24
    46.175.19.0/24 AS34251 max-length /24
    46.175.20.0/23 AS34251 max-length /23
    62.182.120.0/21 AS34251 max-length /21
    62.182.122.0/23 AS34251 max-length /23
    62.182.125.0/24 AS34251 max-length /24

    Open in RPKI / ROA validator Guide

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS34251 announces 23 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 10 of 23 announced prefixes have no ROA (RPKI not found): 46.175.16.0/21, 46.175.16.0/22, 46.175.16.0/24, 46.175.17.0/24, 46.175.18.0/24 (+5).
  • Info: The RPKI state of 13 prefixes was not looked up (no ROA of AS34251 covers them; only the first 10 are checked).
  • Pass: Every announced prefix has an IRR route object.
  • Info: 21 upstreams and peers, 8 downstream networks seen.
HolderIMC-AS LLC IMC
IPv4 prefixes23
IPv6 prefixes0
RPKI10 not found · 13 not looked up
Downstream networks8
Routes to fix

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.
NameIMC-AS
HandleAS34251
RangeAS34251
Statusactive
Registered2004-11-26T16:33:35Z
Last changed2023-07-18T12:36:24Z
Abuse contactabuse@imc.org.ua
Allocation
Registry (RIR)RIPE NCC
CountryUkraine (UA)
Delegated on2004-11-26
StatusAllocated
Delegated rangeAS34251

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

Contacts
RoleNameEmail
registrant MNT-IMC
registrant LLC IMC
registrant RIPE-NCC-END-MNT
abuse Industrial Management Consulting Coordination Centre abuse@imc.org.ua

Source: https://rdap.db.ripe.net/autnum/34251. 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 AS34251 is in PeeringDB as IMC.
  • Pass: AS34251 is in PeeringDB as IMC.
  • Info: Peering policy: Open.
  • Info: Present at 4 internet exchanges with 4 ports (40G in total).
NetworkIMC
AS numberAS34251
TypeCable/DSL/ISP, Europe
Websitehttp://www.imc.ua
IRR as-setAS-IMС
Prefixes (IPv4 / IPv6)200 / 200
Traffic20-50Gbps, Not Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-03-04
Contacts
NOCnoc@imc.ua

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup