ASN LANDING PAGE

AS205569

REGSV-AS REGIONSVYAZ OOO

Last updated · Jul 20, 2026

Country

Total prefixes

7

IPv4 prefixes

7

IPv6 prefixes

0

ASN summary

How to read the scale of AS205569

REGSV-AS REGIONSVYAZ OOO currently reports 7 prefixes and 3 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.

What can an ASN page answer?

An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.

How should you read the organization and region fields?

REGSV-AS REGIONSVYAZ OOO is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.

How should you verify the AS205569 result?

The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.

How to verify this ASN result

AS205569 ASN lookupAS205569 BGPAS205569 peersAS205569 prefixesAS205569 upstreamsREGSV-AS REGIONSVYAZ OOO ASN

Upstreams

Detailed data for this ASN is not available right now.

Downstreams

Detailed data for this ASN is not available right now.

Prefix inventory

PrefixNameCountry
109.248.60.0/24AS205569
46.8.50.0/23AS205569
46.8.50.0/24AS205569
46.8.51.0/24AS205569
62.181.62.0/23AS205569
62.181.62.0/24AS205569
62.181.63.0/24AS205569

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS205569 represent?

AS205569 is an autonomous system number. The current source associates it with REGSV-AS REGIONSVYAZ OOO and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.

What are peers, upstreams, and prefixes useful for on the AS205569 page?

They help explain the scale, interconnection depth, and route structure of AS205569. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.

What should you do after reviewing AS205569?

Open a concrete IP page to check how the address maps into AS205569, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.

Related topics