Skip to main content

AS59504

vpsville-AS

Hosting vpsville.ru

Registry

Authoritative registration data

AS number
59504
Name
vpsville-AS
Organisation
Hosting vpsville.ru
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

52

IPv6 prefixes

13

Total announced

65

Announced prefixes

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

Prefixes announced by AS59504
45.139.184.0/22 IPv4 /22 RPKI not found
185.230.140.0/23 IPv4 /23 not checked
193.38.232.0/23 IPv4 /23 RPKI valid
45.139.186.0/23 IPv4 /23 not checked
95.215.110.0/23 IPv4 /23 RPKI valid
138.16.128.0/24 IPv4 /24 not checked
138.16.129.0/24 IPv4 /24 not checked
138.16.130.0/24 IPv4 /24 not checked
178.130.132.0/24 IPv4 /24 not checked
185.118.64.0/24 IPv4 /24 not checked
185.118.65.0/24 IPv4 /24 RPKI valid
185.118.66.0/24 IPv4 /24 not checked
185.118.67.0/24 IPv4 /24 RPKI valid
185.156.176.0/24 IPv4 /24 RPKI valid
185.156.177.0/24 IPv4 /24 RPKI valid
185.156.178.0/24 IPv4 /24 RPKI valid
185.156.179.0/24 IPv4 /24 not checked
185.177.113.0/24 IPv4 /24 not checked
185.177.115.0/24 IPv4 /24 not checked
185.197.72.0/24 IPv4 /24 RPKI valid
185.197.73.0/24 IPv4 /24 RPKI valid
185.220.32.0/24 IPv4 /24 not checked
185.220.33.0/24 IPv4 /24 RPKI valid
185.220.34.0/24 IPv4 /24 not checked
185.220.35.0/24 IPv4 /24 not checked
185.230.142.0/24 IPv4 /24 not checked
185.246.116.0/24 IPv4 /24 RPKI valid
185.246.117.0/24 IPv4 /24 RPKI valid
185.246.119.0/24 IPv4 /24 RPKI valid
185.254.188.0/24 IPv4 /24 not checked
185.254.189.0/24 IPv4 /24 RPKI valid
185.254.190.0/24 IPv4 /24 not checked
185.42.24.0/24 IPv4 /24 RPKI valid
185.42.26.0/24 IPv4 /24 RPKI valid
185.42.27.0/24 IPv4 /24 not checked
193.150.70.0/24 IPv4 /24 RPKI valid
193.38.234.0/24 IPv4 /24 RPKI valid
194.113.104.0/24 IPv4 /24 not checked
194.113.107.0/24 IPv4 /24 not checked
194.26.210.0/24 IPv4 /24 not checked
194.53.175.0/24 IPv4 /24 RPKI not found
45.142.208.0/24 IPv4 /24 RPKI valid
45.142.209.0/24 IPv4 /24 not checked
45.142.211.0/24 IPv4 /24 RPKI valid
45.151.136.0/24 IPv4 /24 RPKI valid
45.151.137.0/24 IPv4 /24 not checked
80.76.40.0/24 IPv4 /24 not checked
83.171.240.0/24 IPv4 /24 RPKI valid
83.171.241.0/24 IPv4 /24 not checked
83.171.242.0/24 IPv4 /24 not checked
84.54.37.0/24 IPv4 /24 RPKI valid
84.54.39.0/24 IPv4 /24 RPKI valid
2a05:fb41::/32 IPv6 /32 not checked
2a05:fb42::/32 IPv6 /32 not checked
2a0a:4785::/32 IPv6 /32 RPKI valid
2a0c:5241::/32 IPv6 /32 RPKI valid
2a0d:60c0::/32 IPv6 /32 not checked
2a0d:e4c4::/32 IPv6 /32 RPKI not found
2a07:14c0:3000::/36 IPv6 /36 RPKI valid
2a07:14c0:5000::/36 IPv6 /36 RPKI valid
2a07:14c0:6000::/36 IPv6 /36 RPKI valid
2a07:14c0:f000::/36 IPv6 /36 RPKI not found
2a0c:5247:5000::/36 IPv6 /36 RPKI not found
2a07:14c0:1::/48 IPv6 /48 RPKI valid
2a07:14c0::/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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS59504 in AS paths

Observed upstreams
Families
AS35598 INETCOM 148 5,410
v4
AS31500 GNM-AS 231 2,878
v4 v6
AS62255 BEMYLINK 49 1,957
v4
AS202984 team-host 22 779
v4
AS6939 HURRICANE 55 534
v4 v6
AS8732 COMCOR-AS 6 263
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS59504 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 51
v4
AS199524 GCORE 1 45
v4
AS47692 NESSUS 1 20
v6
AS37721 ORG-VTS1-AFRINIC 1 10
v6

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.