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

AS29182 ·

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

Warning: AS29182 (RU-JSCIOT JSC IOT) announces 183 IPv4 and 17 IPv6 prefixes. 2 warnings

AS pageAS29182
HolderRU-JSCIOT JSC IOT
AllocationRIPE NCC, Russia (RU), allocated 2003-06-23
Prefixes (IPv4 / IPv6)183 / 17
RPKI valid95% (189 / 200)
Upstreams and peers23
Peering policyOpen

What to fix

  1. Warning

    10 of 200 announced prefixes have no ROA (RPKI not found): 77.246.144.0/21, 193.150.0.0/23, 2a0e:dfc7:d8f3::/48, 2a0e:fb47::/32, 2a0f:3103::/32 (+5).

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

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

    77.246.144.0/21 AS29182 max-length /21
    193.150.0.0/23 AS29182 max-length /23
    2a0e:dfc7:d8f3::/48 AS29182 max-length /48
    2a0e:fb47::/32 AS29182 max-length /32
    2a0f:3103::/32 AS29182 max-length /32
    2a0f:8443::/32 AS29182 max-length /32
    2a06:dc40::/29 AS29182 max-length /29
    2a11:2087::/32 AS29182 max-length /32
    2a11:5186::/32 AS29182 max-length /32
    2a11:7687::/32 AS29182 max-length /32

    Open in RPKI / ROA validator Guide

  2. 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 10 of 200 announced prefixes have no ROA (RPKI not found): 77.246.144.0/21, 193.150.0.0/23, 2a0e:dfc7:d8f3::/48, 2a0e:fb47::/32, 2a0f:3103::/32 (+5).
  • Pass: AS29182 announces 183 IPv4 and 17 IPv6 prefixes.
  • Warning: 10 of 200 announced prefixes have no ROA (RPKI not found): 77.246.144.0/21, 193.150.0.0/23, 2a0e:dfc7:d8f3::/48, 2a0e:fb47::/32, 2a0f:3103::/32 (+5).
  • Info: 189 of 200 announced prefixes are RPKI valid.
  • Info: The RPKI state of 1 prefixes was not looked up (no ROA of AS29182 covers them; only the first 10 are checked).
  • Pass: Every announced prefix has an IRR route object.
  • Info: 23 upstreams and peers, 3 downstream networks seen.
HolderRU-JSCIOT JSC IOT
IPv4 prefixes183
IPv6 prefixes17
RPKI189 valid · 10 not found · 1 not looked up
Downstream networks3
Routes to fix

Announced prefixes 200

5.35.96.0/23 5.35.98.0/23 31.135.8.0/23 31.135.11.0/24 31.135.12.0/23 31.135.14.0/23 37.46.128.0/23 37.46.130.0/23 37.46.132.0/23 37.46.134.0/23 37.230.112.0/23 37.230.114.0/23 37.230.116.0/23 37.230.118.0/23 45.10.216.0/22 45.66.12.0/22 45.141.208.0/22 45.150.8.0/22 62.109.0.0/20 62.109.0.0/21 62.109.8.0/21 62.109.16.0/21 62.109.24.0/22 62.109.28.0/22 62.181.44.0/24 62.181.53.0/24 62.181.54.0/23 77.246.144.0/21 77.246.156.0/22 77.246.156.0/23 77.246.158.0/23 78.24.216.0/21 79.143.72.0/23 79.174.12.0/23 79.174.14.0/23 80.87.192.0/23 80.87.194.0/23 80.87.196.0/23 80.87.198.0/23 80.87.200.0/23 80.87.202.0/24 80.87.203.0/24 82.146.32.0/21 82.146.32.0/23 82.146.34.0/23 82.146.36.0/23 82.146.38.0/23 82.146.40.0/21 82.146.48.0/23 82.146.50.0/23 82.146.52.0/23 82.146.54.0/23 82.146.56.0/21 82.202.160.0/23 82.202.162.0/23 82.202.165.0/24 82.202.166.0/23 82.202.168.0/23 82.202.170.0/23 82.202.172.0/23 82.202.174.0/23 83.136.232.0/23 83.136.235.0/24 83.220.168.0/23 83.220.170.0/23 83.220.172.0/23 83.220.174.0/23 85.198.72.0/23 85.198.74.0/23 85.198.116.0/23 85.198.118.0/23 86.110.194.0/24 86.110.208.0/23 86.110.212.0/24 86.110.215.0/24 86.110.220.0/24 89.169.28.0/23 89.169.30.0/23 89.169.40.0/23 89.169.42.0/23 91.107.120.0/21 91.132.188.0/22 91.228.224.0/23 91.240.84.0/23 91.240.86.0/23 92.63.96.0/21 92.63.104.0/22 92.63.108.0/22 92.63.108.0/24 92.63.109.0/24 92.63.110.0/23 92.63.192.0/23 92.63.194.0/23 92.118.88.0/22 94.250.248.0/23 94.250.250.0/23 94.250.252.0/23 94.250.254.0/23 108.59.251.0/24 108.171.32.0/24

Showing the first 100.

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.
NameRU-JSCIOT
HandleAS29182
RangeAS29182
Statusactive
Registered2003-06-23T14:25:12Z
Last changed2025-12-29T04:59:10Z
Abuse contactabuse@aoiot.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2003-06-23
StatusAllocated
Delegated rangeAS29182

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

Contacts
RoleNameEmail
registrant mnt-ru-jsciot-1
registrant JSC IOT
registrant RIPE-NCC-END-MNT
abuse IOT Network Operations abuse@aoiot.ru

Source: https://rdap.db.ripe.net/autnum/29182. 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 public NOC, policy or technical contact.
  • Pass: AS29182 is in PeeringDB as JSC IOT.
  • Info: Peering policy: Open.
  • Info: Present at 9 internet exchanges with 17 ports (1.6T in total).
  • Warning: No public NOC, policy or technical contact.
NetworkJSC IOT (JSC «IOT»)
AS numberAS29182
TypeContent, Europe
Websitehttps://aoiot.ru/
IRR as-setAS-THEFIRST
Prefixes (IPv4 / IPv6)200 / 50
Traffic100-200Gbps, Mostly Outbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2025-08-12
Contacts
Abuseabuse@abusehost.ru

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup