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

85.117.82.0/24 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=85.117.82.0%2F24"
JSON Docs

Warning: 85.117.82.0/24 is announced by AS42087 (KANAL7-AS MTS PJSC). 1 warning

Announced as85.117.82.0/24
Origin ASAS42087 KANAL7-AS MTS PJSC
AllocationRIPE NCC, Russia (RU), allocated 2005-03-18
Size256 addresses

What to fix

  1. Warning

    85.117.82.0/24 from AS42087 is RPKI not found: no ROA covers it.

    Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.

    Fix: Create a ROA for this prefix with origin AS42087 and a max length equal to the prefix length.

    prefix: 85.117.82.0/24
    origin: AS42087
    max-length: 24

    Open in RPKI / ROA validator Guide

Checks

Routing and RPKI 85.117.82.0/24 from AS42087 is RPKI not found: no ROA covers it.
  • Pass: Announced as 85.117.82.0/24 by AS42087.
  • Warning: 85.117.82.0/24 from AS42087 is RPKI not found: no ROA covers it.
  • Pass: Seen by 100% of RIPE RIS peers.
Route85.117.82.0/24
Origin ASAS42087 KANAL7-AS MTS PJSC No ROA
IRR route objectsRIPE
Visibility (RIS peers)318 / 318
First seen2024-02-15
Covering prefixes85.117.80.0/20, 85.117.64.0/19

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is delegated (82.117.85.in-addr.arpa).
  • Pass: Reverse DNS is delegated (82.117.85.in-addr.arpa).
Reverse zones 1
ZoneNameservers
82.117.85.in-addr.arpa dns0.mts.ru, dns1.mts.ru, dns1.mtu.ru, dns2.mts-ws.net
Open in DNS lookup
Registration The registry is limiting how often it can be asked. Please try again in a minute.
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

About the network that announces this space, so not in the fix list.

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup