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

AS8242 ·

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

Warning: AS8242 (INTELWAY-AS) announces 16 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS8242
HolderINTELWAY-AS Digital Solutions LLC
AllocationRIPE NCC, Russia (RU), allocated 2011-03-23
Prefixes (IPv4 / IPv6)16 / 0
RPKI valid0% (0 / 16)
Upstreams and peers12

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 16 announced prefixes have no ROA (RPKI not found): 31.42.32.0/20, 31.42.32.0/22, 31.42.32.0/24, 31.42.33.0/24, 31.42.34.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 AS8242 and a max length equal to the prefix length:

    31.42.32.0/20 AS8242 max-length /20
    31.42.32.0/22 AS8242 max-length /22
    31.42.32.0/24 AS8242 max-length /24
    31.42.33.0/24 AS8242 max-length /24
    31.42.34.0/24 AS8242 max-length /24
    31.42.35.0/24 AS8242 max-length /24
    31.42.36.0/22 AS8242 max-length /22
    31.42.37.0/24 AS8242 max-length /24
    31.42.38.0/24 AS8242 max-length /24
    31.42.39.0/24 AS8242 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS8242 announces 16 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 10 of 16 announced prefixes have no ROA (RPKI not found): 31.42.32.0/20, 31.42.32.0/22, 31.42.32.0/24, 31.42.33.0/24, 31.42.34.0/24 (+5).
  • Info: The RPKI state of 6 prefixes was not looked up (no ROA of AS8242 covers them; only the first 10 are checked).
  • Pass: Every announced prefix has an IRR route object.
  • Info: 12 upstreams and peers, 2 downstream networks seen.
HolderINTELWAY-AS Digital Solutions LLC
IPv4 prefixes16
IPv6 prefixes0
RPKI10 not found · 6 not looked up
Downstream networks2
Routes to fix
PrefixRPKI
31.42.32.0/20 No ROA
31.42.32.0/22 No ROA
31.42.32.0/24 No ROA
31.42.33.0/24 No ROA
31.42.34.0/24 No ROA
31.42.35.0/24 No ROA
31.42.36.0/22 No ROA
31.42.37.0/24 No ROA
31.42.38.0/24 No ROA
31.42.39.0/24 No ROA

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.
NameINTELWAY-AS
HandleAS8242
RangeAS8242
Statusactive
Registered2011-03-23T08:20:22Z
Last changed2025-10-29T13:35:03Z
Abuse contactabuse@intelway.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2011-03-23
StatusAllocated
Delegated rangeAS8242

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

Contacts
RoleNameEmail
registrant Digital Solutions LLC
registrant RIPE-DB-MNT
registrant RIPE-NCC-END-MNT
abuse Intelway NOC abuse@intelway.ru

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