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

AS42087 · 

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

Warning: AS42087 (KANAL7-AS MTS PJSC) announces 23 IPv4 and 4 IPv6 prefixes. 3 warnings

AS pageAS42087
HolderKANAL7-AS MTS PJSC
AllocationRIPE NCC, Russia (RU), allocated 2006-12-15
Prefixes (IPv4 / IPv6)23 / 4
RPKI valid11% (3 / 27)
Upstreams and peers1

What to fix

  1. Warning

    10 of 27 announced prefixes have no ROA (RPKI not found): 85.117.64.0/19, 85.117.64.0/20, 85.117.64.0/24, 85.117.80.0/20, 85.117.82.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 AS42087 and a max length equal to the prefix length:

    85.117.64.0/19 AS42087 max-length /19
85.117.64.0/20 AS42087 max-length /20
85.117.64.0/24 AS42087 max-length /24
85.117.80.0/20 AS42087 max-length /20
85.117.82.0/24 AS42087 max-length /24
85.117.83.0/24 AS42087 max-length /24
85.117.93.0/24 AS42087 max-length /24
85.117.94.0/24 AS42087 max-length /24
91.186.96.0/19 AS42087 max-length /19
91.186.96.0/20 AS42087 max-length /20

    Open in RPKI / ROA validator Guide

  2. Warning

    17 of 27 announced prefixes have no IRR route object: 95.129.144.0/22, 85.117.80.0/20, 2a00:1fa2:baf0::/44, 2a00:1fa2:ba00::/40, 213.128.0.0/20 (+12).

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS42087 in your RIR’s IRR database (or RADB).

    route: 95.129.144.0/22
origin: AS42087

route: 85.117.80.0/20
origin: AS42087

route6: 2a00:1fa2:baf0::/44
origin: AS42087

    Open in ASN & BGP prefix lookup

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 10 of 27 announced prefixes have no ROA (RPKI not found): 85.117.64.0/19, 85.117.64.0/20, 85.117.64.0/24, 85.117.80.0/20, 85.117.82.0/24 (+5).
  • Pass: AS42087 announces 23 IPv4 and 4 IPv6 prefixes.
  • Warning: 10 of 27 announced prefixes have no ROA (RPKI not found): 85.117.64.0/19, 85.117.64.0/20, 85.117.64.0/24, 85.117.80.0/20, 85.117.82.0/24 (+5).
  • Info: 3 of 27 announced prefixes are RPKI valid.
  • Info: The RPKI state of 14 prefixes was not looked up (no ROA of AS42087 covers them; only the first 10 are checked).
  • Warning: 17 of 27 announced prefixes have no IRR route object: 95.129.144.0/22, 85.117.80.0/20, 2a00:1fa2:baf0::/44, 2a00:1fa2:ba00::/40, 213.128.0.0/20 (+12).
  • Info: One upstream or peer seen (AS8359): an outage there takes the whole network off the internet.
HolderKANAL7-AS MTS PJSC
IPv4 prefixes23
IPv6 prefixes4
RPKI3 valid · 10 not found · 14 not looked up
Without IRR route object17
Downstream networks0
Routes to fix
PrefixRPKI
85.117.64.0/19 No ROA
85.117.64.0/20 No ROA
85.117.64.0/24 No ROA
85.117.80.0/20 No ROA
85.117.82.0/24 No ROA
85.117.83.0/24 No ROA
85.117.93.0/24 No ROA
85.117.94.0/24 No ROA
91.186.96.0/19 No ROA
91.186.96.0/20 No ROA

Upstreams and peers seen to the left 1

AS8359 Mobile TeleSystems PJSC

Announced prefixes 27

85.117.64.0/19 85.117.64.0/20 85.117.64.0/24 85.117.80.0/20 85.117.82.0/24 85.117.83.0/24 85.117.93.0/24 85.117.94.0/24 91.186.96.0/19 91.186.96.0/20 91.186.97.0/24 91.186.108.0/23 91.186.108.0/24 91.186.109.0/24 91.186.112.0/20 95.129.144.0/21 95.129.144.0/22 95.129.148.0/22 188.75.212.0/24 213.128.0.0/19 213.128.0.0/20 213.128.16.0/20 213.128.31.0/24 2a00:1fa2:80c0::/48 2a00:1fa2:ba00::/40 2a00:1fa2:baf0::/44 2a00:13fa::/32

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.
NameKANAL7-AS
HandleAS42087
RangeAS42087
Statusactive
Registered2006-12-15T15:46:16Z
Last changed2021-02-11T08:28:02Z
Abuse contactabuse@mtu.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2006-12-15
StatusAllocated
Delegated rangeAS42087

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

Contacts
RoleNameEmail
registrant MTU-NOC
registrant MTS PJSC
registrant RIPE-NCC-END-MNT
registrant SIBELTELECOM-MNT
abuse MTU Abuse-c Bender abuse@mtu.ru

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