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

AS24588 · 

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

Warning: AS24588 (NETPROVODOV-AS) announces 20 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS24588
HolderNETPROVODOV-AS JSC "ER-Telecom Holding"
AllocationRIPE NCC, Russia (RU), allocated 2002-01-09
Prefixes (IPv4 / IPv6)20 / 0
RPKI valid0% (0 / 20)
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 20 announced prefixes have no ROA (RPKI not found): 46.52.151.0/24, 46.52.206.0/24, 79.122.240.0/22, 81.17.0.0/20, 82.147.96.0/22 (+5).

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

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

    46.52.151.0/24 AS24588 max-length /24
46.52.206.0/24 AS24588 max-length /24
79.122.240.0/22 AS24588 max-length /22
81.17.0.0/20 AS24588 max-length /20
82.147.96.0/22 AS24588 max-length /22
82.147.100.0/23 AS24588 max-length /23
82.147.102.0/23 AS24588 max-length /23
82.147.102.0/24 AS24588 max-length /24
82.147.104.0/24 AS24588 max-length /24
82.147.106.0/23 AS24588 max-length /23

    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: AS24588 announces 20 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 10 of 20 announced prefixes have no ROA (RPKI not found): 46.52.151.0/24, 46.52.206.0/24, 79.122.240.0/22, 81.17.0.0/20, 82.147.96.0/22 (+5).
  • Info: The RPKI state of 10 prefixes was not looked up (no ROA of AS24588 covers them; only the first 10 are checked).
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS9049): an outage there takes the whole network off the internet.
HolderNETPROVODOV-AS JSC "ER-Telecom Holding"
IPv4 prefixes20
IPv6 prefixes0
RPKI10 not found · 10 not looked up
Downstream networks0
Routes to fix
PrefixRPKI
46.52.151.0/24 No ROA
46.52.206.0/24 No ROA
79.122.240.0/22 No ROA
81.17.0.0/20 No ROA
82.147.96.0/22 No ROA
82.147.100.0/23 No ROA
82.147.102.0/23 No ROA
82.147.102.0/24 No ROA
82.147.104.0/24 No ROA
82.147.106.0/23 No ROA

Upstreams and peers seen to the left 1

AS9049 ER-Telecom

Announced prefixes 20

46.52.151.0/24 46.52.206.0/24 79.122.240.0/22 81.17.0.0/20 82.147.96.0/22 82.147.100.0/23 82.147.102.0/23 82.147.102.0/24 82.147.104.0/24 82.147.106.0/23 82.147.108.0/22 82.147.112.0/22 82.147.117.0/24 82.147.119.0/24 82.147.120.0/21 94.28.8.0/22 94.28.12.0/23 94.28.14.0/23 94.28.38.0/24 94.28.39.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.
NameNETPROVODOV-AS
HandleAS24588
RangeAS24588
Statusactive
Registered2002-01-09T16:20:57Z
Last changed2021-06-17T04:33:03Z
Abuse contactabuse@domru.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2002-01-09
StatusAllocated
Delegated rangeAS24588

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

Contacts
RoleNameEmail
registrant JSC "ER-Telecom Holding"
registrant RAID-MNT
registrant RIPE-NCC-END-MNT
abuse ER-Telecom ISP Contact Role abuse@domru.ru

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