Skip to main content

AS205460

RG-SV

--------Beeline--------

Registry

Authoritative registration data

AS number
205460
Name
RG-SV
Organisation
--------Beeline--------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

0

Total announced

9

Announced prefixes

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

Prefixes announced by AS205460
185.218.10.0/24 IPv4 /24 RPKI valid
185.218.11.0/24 IPv4 /24 not checked
185.218.8.0/24 IPv4 /24 RPKI valid
185.218.9.0/24 IPv4 /24 RPKI valid
192.175.1.0/24 IPv4 /24 RPKI valid
194.55.140.0/24 IPv4 /24 not checked
194.55.141.0/24 IPv4 /24 RPKI valid
194.55.142.0/24 IPv4 /24 RPKI valid
194.55.143.0/24 IPv4 /24 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 AS205460
Address families
Eurasia Peering IX: Peering LAN 1,000 Mbps IPv4
GNM-IX 10,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_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 AS205460 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

24 networks seen before AS205460 in AS paths

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS205460 in AS paths

Observed downstreams
Families
AS41109 TELEMEDNET 250 1,224
v4
AS41639 INCOMSV-AS 371 876
v4 v6
AS47923 LANCRAFT-AS 39 45
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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