All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Macedonia Launch (New Location) Double-Specs, VMs in UK, NL, AL, MK (VPS + VDS)
We have launched our new Macedonia location. For the next 7 days, all VPS and VDS orders in this location come with double resources.
Whatever you order will be automatically doubled in the panel, and the doubled specs stay for the life of the VM. (vCPU, RAM, Disk)
We have also rolled out a number of updates and a redesign of our panel to make ordering and management more straightforward.
Starting at 5 EUR/month
Locations
We currently operate multiple locations:
- Albania (AL)
- Netherlands (NL)
- United Kingdom (London) [IE GEO]
- North Macedonia (Skopje)
The double specs promotion applies only to the new MK (Skopje) location.
Infrastructure (MK location)
The Macedonia location is running on:
- NVMe storage
- AMD EPYC 7302 processors
- Multiple nodes live in this location with ability to expand in this location.
Links (To see Available Plans + Locations)
VPS: https://www.avsisp.com/vps/
VDS: https://www.avsisp.com/vds/
What is included
- IPv4 and /48 IPv6
- 1 Gbps on VPS
- 10 Gbps on VDS
- Unlimited bandwidth
- Automatic provisioning (within 5 minutes)
Optional
- BGP sessions and BYOIP support (5 EUR/month, enabled in panel)
How to find the offer in the panel
After registering, logging in, and adding the required credit:
- Click Order VM in the navigation menu
- Click the MK flag (MK / Skopje)
- Choose the operating system you want
- Select VPS or VDS
- You will see the double-spec plans — select one and proceed with the order process
Ordering process (billing)
- Add credit to your account to cover the plan you want
- Complete the order process
- Ensure you have enough credit at renewal time to avoid suspension or termination
We operate on a prepaid model with no long-term commitments. You can disable or enable auto-renew on any VM. If there is not enough credit at time of renew, VM may be suspended and later terminated / deleted if left suspended for more than 72 hours after due-date. If auto-renew is enabled, renewal will be attempted from available account credit at time of renewal. All services are month-to-month. You can extend for longer period of time easily - simply add enough credit to cover the time, go to the VM in the panel, click extend, and choose the period to extend for. There is no limit to how long a VM can be extended in advance. 1 month, 6months, a year or 5, it's all possible. Simply extend it to your hearts content.
Community bonus
Comment your invoice ID where you added credit during the promotion period, and we will apply extra credit equal to 10% of the amount added before your first order.
Examples:
- Add 10 EUR → get 1 EUR extra
Add 100 EUR → get 10 EUR extra
Existing customers can get this same offer - simply add credit before ordering a MK VPS / VDS and comment the Invoice ID of that credit addition. The 10% will still be given as bonus.
Notes
- Applies only to new orders in the Macedonia (Skopje) location
- No coupon required
- Doubled specs are shown directly in the panel
- Promo valid for 7 days
Questions about routing or setup are welcome. Let us know if you have any issues or questions at all - we're here to help 
Comments
fuck yeah you dirty girl @avsisp
Love you too ya dirty dirty ting
@forest come for new location
had a ticket open about macedonia location launch promo 2 days ago and here it is 👍
From https://www.avsisp.com/transit/routing-policies/:
Does this include any ranges running Tor relays? If so, can it be disabled? Because even a middle relay has to make connections with exit relays. Assuming that Tor middle relays are allowed in this location; I know they aren't allowed in your Albania location due to the heavy bandwidth use, but since Macdedonia specifies unlimited bandwidth, I assume that's not an issue.
GLWS!
looking glass please?
Also, is your lineup DMCA-friendly? I’m planning to use it as a personal VPN and want the peace of mind of knowing my VPS/account won't get yeeted the second a notice comes in.
good boy
Good luck with sale ❤️
We replied to you also with this same offer there in ticket
I was told they prohibit TOR relays and TOR traffic is filtered. Not sure whether new location is the same but I suspect it is.
At present, we actively block all active Tor nodes by IP + Port combo (not IP alone) using the official list maintained by Tor themselves. We do not allow Tor usage / activity at all on our network.
The list is available here: https://onionoo.torproject.org/details?running=true
There is simply too much abuse around Tor for us to allow it. Since blocking Tor, a large portion of issues have simply stopped existing. Clients can always use bridges if they want to be a Tor client, but being Relay or Entry / Exit node will not work on our network.
We do not ban people or block them for getting DMCA notices at all. DMCA notices are kind of moot for us when we know most clients are using the VPS for person VPN, etc. - Tend to get replied to with "File location ON THE SERVER please?" which usually gets no reply from them since it's usually a Bittorrent Bot sending the false reports.
@avsisp
Oh young Jedi - you must send 1500 USD to your account to get 1500 USD on your account. This is the way of the Jedi.
Abuse coming from Tor is from exit nodes, and you could block specifically those.
I can see only two options for the widespread blocking of Tor:
for some reason i dont receive ticket answers via mail, but newsletters arrive fine.
@avsisp Which ASN is in North Macedonia?
Our ASN is AS210464. Upstream is AS213900.
Incorrect.
Tor nodes tend to generate a lot of abuse complaints. They also tend to get the ASN flagged as "Tor" which leads to Reddit blocking and requiring login from all users on all IP ranges on the ASN, Netflix showing "Originals Only", and countless other issues simply for being flagged as "Tor", even to unrelated IPs on the same ASN.
Even when not running as an Exit node, there's countless systems that still report all the IPs to abuse databases automatically and simply comment "Flagged Tor, attempted access", blah.
So no, it isn't only about the bandwidth, while that is actually one thing. Tor users tend to max out the bandwidth in ridiculous ways. Wanna see a "normal" VM usage go from 50TB to 500TB in a month? Allow Tor in a less-common location... You'll see it fly.
Again, users can always use a bridge to access Tor, nothing is stopping them. But not being able to talk to other Relays directly means they can't host a relay or exit node, which stops this kind of mess in the first place.
The amount of user complains we get for blocked Tor (1-2 per month) is nothing compared to the 100s we got when our entire ASN was being flagged for Tor, VPN, etc.
I just wanted to kindly ask if there might be an alternative option available. Instead of the balance bonus, would it be possible to receive a 10 Gbit network upgrade for a Nano or Micro VPS plan?
I completely understand if this is not something you offer, but I thought I would ask just in case
We can't remove specs, as the setup is entirely automated and we have no way to downgrade a VM that has been upgraded (upgrades are possible but downgrades not due to disk resizing restrictions of QEMU). Send us a ticket and we'll work with you directly to upgrade your port if needed. Just send a ticket before your order.
Tor relays do NOT generate valid external abuse notifications, and 99% of hosting providers are apparently able to survive without blocking them. They however consume a lot of bandwidth, and that seems to be the main issue here.
Your ASN being flagged for VPN is completely normal and expected, given that your users do indeed host VPN servers. This can cause issues, but it is what it is.
If they care that much about silly abuse notifications.. might as well ban VPN too.
Relays DO generate abuse complains, but we are not referring to email notifications here. We are referring to listings in databases of abuse (AbuseIPDB, abuse.ch, etc with vague "Tor detected, access attempt" comments). This causes the IPs to be unclean for issue to another client. We keep our IP space clean. We don't want IPs to be given to users that are unusable for their usage. When you operate month-to-month with clients, you can't simply allow a single client to abuse the IP space (intentionally or not) and cause it to be unusable for all other clients. That's not fair to other clients with normal usage intents.
ASN being flagged is a major issue for us and isn't "normal" as you claim. It's only normal where people allow others to run Tor nodes or public VPN servers. We ban both. We only allow personal usage VPN, not public VPN companies to use our services, for the same reason. When you run a business, you're running a public service for the good of all clients, and you have weigh the benefits vs costs of each decision. Allowing Tor to get our ASN flagged hurts 1000s of clients, blocking Tor instead hurts less than 10 clients total.
Normal VPS users aren't complaining. We have had in our entire history only 4 total Tor relays active on our network - even before the block of Tor due to ASN being flagged everywhere.
Again, bandwidth isn't the concern here. The damage to our IPs and ASN is - 100%. Bandwidth usage, of course is ridiculous for Tor nodes - that's not even for debate - but it isn't what caused us to block Tor nodes on our network. If we cared about the bandwidth, we'd block Bittorrent, Youtube, and anything else people are using that eats loads of bandwidth - checked syncthing lately? It eats 10x as much as Tor easily. Our highest bandwidth users are mostly sending traffic to Cloudflare as far as we can tell (general overall usage summaries of NIC and XC connections and so on indicate most traffic going to Cloudflare). Should we block Cloudflare to lower traffic? Doesn't really make sense. We don't pay for how many TB you use. We pay for pipe sizes. That is, we pay for how large our IXP connections are (where 80% of traffic hits), our XC to direct peers (how large the cable and our connections[NIC/Port,optics] on each side are), and how much upstream transit we get (for example in MK, that would be Cogent's costs, which are again, based on port sizes).
We do ban public VPN, thanks. Private VPN = it's your traffic, not sold to others. Therefore, you're responsible for your usage. But as mentioned before, it depends on the abuse notifications. If you're doing massive port scanning of the internet and getting unauthorized access attempt notifications from 1000s of reputable networks, you will be shutdown - quickly - as I'd hope any self-respecting network operator would. But if you are using Bittorrent on your own local PC and using it through the VM (over PRIVATE VPN as we discussed here), and we get complaints, we can't do much about it - there's no files, links to file, etc on the server for us to check into - even if we did have access to inside of your VM (which we DO NOT). Those types would get replied to asking for a public link showing the file on this IP of the server, which they can't provide. There's no HTTP(s) address to the file on an IP of ours to even check out.
Some common sense does go into these things. Think of "American Freedom of Speech" (what you're thinking in this sense, free for all) vs "European Freedom of Speech" (my rights end where yours begin, there is a limit - our method). We try to balance. That is, some abuse notifications will go in one ear and out the other, as they say. And some will land with us actually checking them out. There's the "noise" that should be ignored, and there's the "legit issues" that should be handled.
@avsisp Yabs, please
Ran a YABS on my VM, here you go:
GL on expansion and with sales.
who it s online reak t it