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.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
91.201.109.0/24 ·
Problem: 91.201.109.0/24 is announced by AS201776 (MIRANDA-AS). 1 problem · 1 warning
| Announced as | 91.201.109.0/24 |
|---|---|
| Origin AS | AS201776 MIRANDA-AS |
| Holder | LTC-MNT |
| Allocation | RIPE NCC, Russia (RU), assigned 2007-11-29 |
| Size | 256 addresses |
| Abuse contact | abuse@lugtel.com |
What to fix
-
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
-
Warning
Seen by only 20% of RIPE RIS peers.
Partial visibility points to filtering, a missing IRR route object, or an RPKI problem.
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.
| Route | 91.201.109.0/24 |
|---|---|
| Origin AS | AS201776 MIRANDA-AS Miranda-Media Ltd RPKI invalid |
| IRR route objects | RIPE |
| Visibility (RIS peers) | 64 / 319 |
| First seen | 2024-06-22 |
| Covering prefixes | 91.201.108.0/23, 91.201.108.0/22 |
| ROA prefix | Max length | Origin 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 lookupReverse DNS Reverse DNS is delegated (109.201.91.in-addr.arpa).
- Pass: Reverse DNS is delegated (109.201.91.in-addr.arpa).
| Zone | Nameservers |
|---|---|
| 109.201.91.in-addr.arpa | ns1.miranda-media.net, ns2.miranda-media.net |
Registration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | ELLYA-NET |
|---|---|
| Handle | 91.201.108.0 - 91.201.111.255 |
| Range | 91.201.108.0 – 91.201.111.255 |
| Country | RU |
| Status | active |
| Registered | 2007-11-29T10:54:38Z |
| Last changed | 2025-12-01T12:31:13Z |
| Abuse contact | abuse@lugtel.com |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Russia (RU) |
| Delegated on | 2007-11-29 |
| Status | Assigned |
| Delegated range | 91.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.
| Role | Name | |
|---|---|---|
| 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 lookupPeeringDB 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.
| Network | Miranda-Media Ltd (Miranda) |
|---|---|
| AS number | AS201776 |
| Type | NSP, Regional |
| Website | http://www.miranda-media.ru |
| IRR as-set | AS-MRNDA |
| Prefixes (IPv4 / IPv6) | 600 / 20 |
| Traffic | 500-1000Gbps, Mostly Inbound |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-10-13 |
| NOC | noc@miranda-media.ru |
|---|---|
| Policy | service-b2o@miranda-media.ru |
| Public Relations | sales-b2o@miranda-media.ru |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup