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

AS50809 · 

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

Warning: AS50809 (CMS-AS) announces 7 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS50809
HolderCMS-AS Centr Mezhdugorodnoy Svyazi LLC
AllocationRIPE NCC, Russia (RU), allocated 2019-02-27
Prefixes (IPv4 / IPv6)7 / 0
RPKI valid29% (2 / 7)
Upstreams and peers1
Peering policyOpen

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    5 of 7 announced prefixes have no ROA (RPKI not found): 45.87.216.0/24, 45.87.217.0/24, 45.87.218.0/24, 45.136.100.0/24, 92.119.131.0/24.

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS50809 and a max length equal to the prefix length:

    45.87.216.0/24 AS50809 max-length /24
45.87.217.0/24 AS50809 max-length /24
45.87.218.0/24 AS50809 max-length /24
45.136.100.0/24 AS50809 max-length /24
92.119.131.0/24 AS50809 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  4. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS50809 announces 7 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 5 of 7 announced prefixes have no ROA (RPKI not found): 45.87.216.0/24, 45.87.217.0/24, 45.87.218.0/24, 45.136.100.0/24, 92.119.131.0/24.
  • Info: 2 of 7 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS8359): an outage there takes the whole network off the internet.
HolderCMS-AS Centr Mezhdugorodnoy Svyazi LLC
IPv4 prefixes7
IPv6 prefixes0
RPKI2 valid · 5 not found
Downstream networks0
Routes to fix
PrefixRPKI
45.87.216.0/24 No ROA
45.87.217.0/24 No ROA
45.87.218.0/24 No ROA
45.136.100.0/24 No ROA
92.119.131.0/24 No ROA

Upstreams and peers seen to the left 1

AS8359 Mobile TeleSystems PJSC

Announced prefixes 7

45.87.216.0/24 45.87.217.0/24 45.87.218.0/24 45.136.100.0/24 77.83.73.0/24 92.119.131.0/24 213.226.100.0/24

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.
NameCMS-AS
HandleAS50809
RangeAS50809
Statusactive
Registered2019-02-27T10:27:15Z
Last changed2025-12-30T08:16:18Z
Abuse contactcms23042010@mail.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2019-02-27
StatusAllocated
Delegated rangeAS50809

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

Contacts
RoleNameEmail
registrant IP-RIPE
registrant Centr Mezhdugorodnoy Svyazi LLC
registrant RIPE-NCC-END-MNT
abuse Centr Mezhdugorodnoy Svyazi cms23042010@mail.ru

Source: https://rdap.db.ripe.net/autnum/50809. 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 No IRR as-set is listed.
  • Pass: AS50809 is in PeeringDB as Centr Mezhdugorodnoy Svyazi.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkCentr Mezhdugorodnoy Svyazi
AS numberAS50809
Type, Not Disclosed
Prefixes (IPv4 / IPv6)0 / 0
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup