Skip to main content

AS51028

SVOLS-AS

======Uplinks======

Registry

Authoritative registration data

AS number
51028
Name
SVOLS-AS
Organisation
======Uplinks======
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

2

Total announced

6

Announced prefixes

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

Prefixes announced by AS51028
178.216.152.0/21 IPv4 /21 RPKI valid
195.2.206.0/23 IPv4 /23 RPKI valid
91.213.44.0/24 IPv4 /24 RPKI valid
91.239.42.0/24 IPv4 /24 RPKI valid
2a03:5a07::/32 IPv6 /32 RPKI not found
2a03:5a00:e::/48 IPv6 /48 not checked

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 AS51028
Address families
BAIKAL-IX: Peering LAN 40,000 Mbps IPv4
GNM-IX 20,000 Mbps IPv4 · IPv6
Global-IX 40,000 Mbps IPv4 · IPv6
MSK-IX Ekaterinburg 40,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 40,000 Mbps IPv4 · IPv6
MSK-IX Novosibirsk 10,000 Mbps IPv4 · IPv6
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4

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 AS51028 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

28 networks seen before AS51028 in AS paths

No rows match “”.

Showing – of

Observed downstreams

25 networks seen after AS51028 in AS paths

No rows match “”.

Showing – of

Uncertain adjacencies

16 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.