Skip to main content

AS8595

WESTCALL-AS

Moscow, Russia

Registry

Authoritative registration data

AS number
8595
Name
WESTCALL-AS
Organisation
Moscow, Russia
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

53

IPv6 prefixes

2

Total announced

55

Announced prefixes

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

Prefixes announced by AS8595
188.246.160.0/19 IPv4 /19 not checked
195.94.224.0/19 IPv4 /19 not checked
81.94.128.0/19 IPv4 /19 not checked
109.74.128.0/20 IPv4 /20 not checked
178.209.96.0/20 IPv4 /20 not checked
195.209.208.0/20 IPv4 /20 not checked
217.173.64.0/20 IPv4 /20 not checked
91.135.144.0/20 IPv4 /20 not checked
188.92.104.0/21 IPv4 /21 not checked
5.101.200.0/21 IPv4 /21 not checked
77.247.184.0/21 IPv4 /21 not checked
78.24.0.0/21 IPv4 /21 not checked
85.249.0.0/21 IPv4 /21 not checked
91.103.208.0/21 IPv4 /21 not checked
92.39.128.0/21 IPv4 /21 not checked
92.42.208.0/21 IPv4 /21 not checked
93.174.224.0/21 IPv4 /21 not checked
93.189.80.0/21 IPv4 /21 not checked
94.199.104.0/21 IPv4 /21 not checked
178.209.112.0/22 IPv4 /22 not checked
178.209.120.0/22 IPv4 /22 not checked
185.71.68.0/22 IPv4 /22 not checked
188.92.244.0/22 IPv4 /22 not checked
195.211.80.0/22 IPv4 /22 not checked
217.172.28.0/22 IPv4 /22 not checked
45.81.200.0/22 IPv4 /22 not checked
5.101.60.0/22 IPv4 /22 not checked
93.189.80.0/22 IPv4 /22 not checked
178.209.118.0/23 IPv4 /23 not checked
178.209.124.0/23 IPv4 /23 not checked
188.246.164.0/23 IPv4 /23 not checked
195.191.88.0/23 IPv4 /23 not checked
31.129.126.0/23 IPv4 /23 not checked
46.34.128.0/23 IPv4 /23 not checked
46.34.132.0/23 IPv4 /23 not checked
62.32.80.0/23 IPv4 /23 not checked
81.94.128.0/23 IPv4 /23 not checked
81.94.136.0/23 IPv4 /23 not checked
82.194.242.0/23 IPv4 /23 not checked
91.230.52.0/23 IPv4 /23 not checked
178.209.116.0/24 IPv4 /24 not checked
178.209.117.0/24 IPv4 /24 not checked
185.13.116.0/24 IPv4 /24 not checked
185.231.56.0/24 IPv4 /24 RPKI not found
188.246.160.0/24 IPv4 /24 not checked
193.233.162.0/24 IPv4 /24 not checked
193.233.163.0/24 IPv4 /24 not checked
195.19.215.0/24 IPv4 /24 not checked
213.79.102.0/24 IPv4 /24 not checked
46.34.135.0/24 IPv4 /24 not checked
62.32.77.0/24 IPv4 /24 not checked
77.108.113.0/24 IPv4 /24 not checked
93.189.84.0/24 IPv4 /24 not checked
2a02:de80::/29 IPv6 /29 not checked
2a11:a940::/29 IPv6 /29 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 AS8595
Address families
MSK-IX Moscow: MSK-IX peering network 20,000 Mbps IPv4
PITER-IX Frankfurt 50,000 Mbps IPv4
PITER-IX Helsinki 50,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 50,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 AS8595 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS8595 in AS paths

Observed upstreams
Families
AS50509 TRANSROUTE 4,659 16,472
v4 v6
AS20764 RASCOM-AS 2,064 7,990
v4 v6
AS3216 SOVAM-AS 1,449 7,215
v4 v6
AS35598 INETCOM 800 2,678
v4
AS62255 BEMYLINK 578 1,922
v4
AS25091 IP-Max 69 500
v4 v6
AS12389 ROSTELECOM-AS 99 123
v4
AS9198 KAZTELECOM-AS 25 79
v4 v6
AS137409 GSLNETWORKS-AS-AP 20 72
v4

No rows match “”.

Showing – of

Observed downstreams

46 networks seen after AS8595 in AS paths

No rows match “”.

Showing – of

Uncertain adjacencies

12 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 34 552
v4 v6
AS49544 i3Dnet 27 172
v4
AS41722 MIRAN-AS 38 113
v4 v6
AS205112 PHILUNET 33 97
v4
AS41327 FIBERTELECOM-AS 28 91
v4 v6
AS36236 NETACTUATE 30 88
v4 v6
AS49434 FBWNETWORKS 29 83
v4
AS28917 Fiord-AS 28 83
v4
AS49673 TRUENETWORK 26 78
v4
AS37721 ORG-VTS1-AFRINIC 23 77
v4
AS28910 INTAL-ASN 1 2
v6
AS199524 GCORE 1 1
v4

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.