Skip to main content

AS8752

ASVT-NETWORK

Russia

Registry

Authoritative registration data

AS number
8752
Name
ASVT-NETWORK
Organisation
Russia
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

1

Total announced

6

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS8752
212.46.0.0/19 IPv4 /19 not checked
46.38.96.0/19 IPv4 /19 RPKI valid
95.182.32.0/19 IPv4 /19 RPKI valid
185.35.168.0/22 IPv4 /22 RPKI valid
212.46.0.0/23 IPv4 /23 not checked
2a03:3200::/32 IPv6 /32 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS8752
Address families
AMS-IX 10,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 40,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 10,000 Mbps IPv4
PITER-IX Helsinki 10,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 40,000 Mbps IPv4 · IPv6
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS8752 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS8752 in AS paths

Observed upstreams
Families
AS57304 RETNRU-AS 373 1,226
v4 v6
AS43298 StormNetworks 275 346
v4
AS48166 FORTEX-AS 42 192
v4
AS6939 HURRICANE 75 183
v4 v6
AS25091 IP-Max 6 47
v4 v6
AS9002 RETN-AS 9 14
v4 v6
AS41327 FIBERTELECOM-AS 2 9
v4 v6
AS61049 EXASCALE 2 8
v4
AS43727 KVANT-TELECOM 1 4
v4
AS9198 KAZTELECOM-AS 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS8752 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

11 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.