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

AS44895 ·

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

Warning: AS44895 (ANTENNA-GARANT-AS) announces 25 IPv4 and 1 IPv6 prefixes. 3 warnings

AS pageAS44895
HolderANTENNA-GARANT-AS MTS PJSC
AllocationRIPE NCC, Russia (RU), allocated 2008-03-28
Prefixes (IPv4 / IPv6)25 / 1
RPKI valid4% (1 / 26)
Upstreams and peers1

What to fix

  1. Warning

    10 of 26 announced prefixes have no ROA (RPKI not found): 5.227.100.0/24, 5.227.102.0/24, 89.106.195.0/24, 89.106.199.0/24, 91.203.64.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 AS44895 and a max length equal to the prefix length:

    5.227.100.0/24 AS44895 max-length /24
    5.227.102.0/24 AS44895 max-length /24
    89.106.195.0/24 AS44895 max-length /24
    89.106.199.0/24 AS44895 max-length /24
    91.203.64.0/22 AS44895 max-length /22
    91.203.65.0/24 AS44895 max-length /24
    91.203.66.0/24 AS44895 max-length /24
    109.68.112.0/21 AS44895 max-length /21
    109.68.112.0/23 AS44895 max-length /23
    109.68.114.0/23 AS44895 max-length /23

    Open in RPKI / ROA validator Guide

  2. Warning

    4 of 26 announced prefixes have no IRR route object: 89.106.199.0/24, 89.106.195.0/24, 81.195.172.0/24, 109.94.188.0/23.

    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 AS44895 in your RIR’s IRR database (or RADB).

    route: 89.106.199.0/24
    origin: AS44895
    
    route: 89.106.195.0/24
    origin: AS44895
    
    route: 81.195.172.0/24
    origin: AS44895

    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 26 announced prefixes have no ROA (RPKI not found): 5.227.100.0/24, 5.227.102.0/24, 89.106.195.0/24, 89.106.199.0/24, 91.203.64.0/22 (+5).
  • Pass: AS44895 announces 25 IPv4 and 1 IPv6 prefixes.
  • Warning: 10 of 26 announced prefixes have no ROA (RPKI not found): 5.227.100.0/24, 5.227.102.0/24, 89.106.195.0/24, 89.106.199.0/24, 91.203.64.0/22 (+5).
  • Info: 1 of 26 announced prefixes are RPKI valid.
  • Info: The RPKI state of 15 prefixes was not looked up (no ROA of AS44895 covers them; only the first 10 are checked).
  • Warning: 4 of 26 announced prefixes have no IRR route object: 89.106.199.0/24, 89.106.195.0/24, 81.195.172.0/24, 109.94.188.0/23.
  • Info: One upstream or peer seen (AS8359): an outage there takes the whole network off the internet.
HolderANTENNA-GARANT-AS MTS PJSC
IPv4 prefixes25
IPv6 prefixes1
RPKI1 valid · 10 not found · 15 not looked up
Without IRR route object4
Downstream networks4
Routes to fix

Upstreams and peers seen to the left 1

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.
NameANTENNA-GARANT-AS
HandleAS44895
RangeAS44895
Statusactive
Registered2008-03-28T12:24:29Z
Last changed2020-12-22T09:20:19Z
Abuse contactabuse@mtu.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2008-03-28
StatusAllocated
Delegated rangeAS44895

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

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

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