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

91.201.109.0/24 ·

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

Problem: 91.201.109.0/24 is announced by AS201776 (MIRANDA-AS). 1 problem · 1 warning

Announced as91.201.109.0/24
Origin ASAS201776 MIRANDA-AS
HolderLTC-MNT
AllocationRIPE NCC, Russia (RU), assigned 2007-11-29
Size256 addresses
Abuse contactabuse@lugtel.com

What to fix

  1. Problem

    91.201.109.0/24 from AS201776 is RPKI invalid: no ROA authorises this origin.

    ROAs for this space name AS29031. Networks that filter will drop the route – the usual cause of an outage after moving to a new provider or adding DDoS protection.

    Fix: Create a ROA for AS201776 (keep the old one until the move is finished), or stop announcing the route from this AS.

    prefix: 91.201.109.0/24
    origin: AS201776
    max-length: 24

    Open in RPKI / ROA validator Guide

  2. Warning

    Seen by only 20% of RIPE RIS peers.

    Partial visibility points to filtering, a missing IRR route object, or an RPKI problem.

    Open in ASN & BGP prefix lookup

Checks

Routing and RPKI 91.201.109.0/24 from AS201776 is RPKI invalid: no ROA authorises this origin.
  • Pass: Announced as 91.201.109.0/24 by AS201776.
  • Problem: 91.201.109.0/24 from AS201776 is RPKI invalid: no ROA authorises this origin.
  • Warning: Seen by only 20% of RIPE RIS peers.
Route91.201.109.0/24
Origin ASAS201776 MIRANDA-AS Miranda-Media Ltd RPKI invalid
IRR route objectsRIPE
Visibility (RIS peers)64 / 319
First seen2024-06-22
Covering prefixes91.201.108.0/23, 91.201.108.0/22
ROAs covering this prefix
ROA prefixMax lengthOrigin AS
91.201.109.0/24 /24 AS29031
91.201.108.0/23 /23 AS29031
91.201.108.0/22 /22 AS29031

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is delegated (109.201.91.in-addr.arpa).
  • Pass: Reverse DNS is delegated (109.201.91.in-addr.arpa).
Reverse zones 1
ZoneNameservers
109.201.91.in-addr.arpa ns1.miranda-media.net, ns2.miranda-media.net
Open in DNS lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameELLYA-NET
Handle91.201.108.0 - 91.201.111.255
Range91.201.108.0 – 91.201.111.255
CountryRU
Statusactive
Registered2007-11-29T10:54:38Z
Last changed2025-12-01T12:31:13Z
Abuse contactabuse@lugtel.com
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2007-11-29
StatusAssigned
Delegated range91.201.108.0/22 (91.201.108.0 – 91.201.111.255)

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

Contacts
RoleNameEmail
registrant LTC-MNT
registrant Lugansk Telephone Company LLC
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@lugtel.com

Source: https://rdap.db.ripe.net/ip/91.201.109.0/24. 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 AS201776 is in PeeringDB as Miranda-Media Ltd.
  • Pass: AS201776 is in PeeringDB as Miranda-Media Ltd.
  • Info: Peering policy: Open.
  • Info: Present at 3 internet exchanges with 3 ports (240G in total).

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

NetworkMiranda-Media Ltd (Miranda)
AS numberAS201776
TypeNSP, Regional
Websitehttp://www.miranda-media.ru
IRR as-setAS-MRNDA
Prefixes (IPv4 / IPv6)600 / 20
Traffic500-1000Gbps, Mostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-10-13
Contacts
NOCnoc@miranda-media.ru
Policyservice-b2o@miranda-media.ru
Public Relationssales-b2o@miranda-media.ru

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup