My experience with GreenCloud
I currently use GreenCloud VPS for multiple public Linux VPS nodes, including Clanker and ScopeCreep.
These are not idle test machines. I use them for Docker services, monitoring, web applications, DN42 routing, WireGuard, DNS, small Internet-protocol servers, and networking experiments.
GreenCloud has been a good fit for the kind of inexpensive Linux infrastructure I run: enough resources to do useful work, cheap enough that keeping multiple locations online is practical, and support that has responded quickly when I have hit provider-side network problems.
What I run on them
- Docker and Docker Compose workloads
- ASP.NET Core / .NET applications
- Mission Control monitoring and telemetry
- Random Steam Game and Random GitHub
- Gopher, Gemini, QOTD, Finger, and other small services
- WireGuard tunnels
- BIRD and DN42 BGP routing
- IPv4 and IPv6 networking experiments
- Authoritative DNS and HTTPS services
Support experience
I have had a couple of network problems worth mentioning. I think those incidents are more useful in a review than pretending nothing has ever gone wrong, because they show what support does when the infrastructure is actually broken.
IPv6 provisioning issue
After enabling IPv6 on one VPS, Neighbor Discovery to the supplied gateway worked and outbound packets left the VM, but nothing came back. Packet captures indicated that the problem was upstream of the guest.
I opened a ticket at 07:30. Support replied at 07:32, investigated the VPS, and at 07:48 asked me to retry after making a change. I confirmed IPv6 was working at 07:54.
About 24 minutes from opening the ticket to confirmed working IPv6.
Unsolicited IPv6 multicast traffic
On another VPS I noticed inbound bandwidth increasing even though my applications were not receiving that amount of traffic.
A packet capture showed unsolicited ICMPv6 / MLDv2 multicast listener reports from another device on the provider-side network. During a 300-second capture I measured roughly 72,007 frames, about 107 MB, or approximately 2.85 Mbps of sustained inbound traffic from that conversation.
I opened a support ticket at 01:16. GreenCloud replied at 01:19 and began investigating the provider-side source.
The unwanted multicast traffic stopped after they investigated the issue, so the underlying problem was fixed. The bandwidth that had already been recorded in the control panel was not removed afterward.
The initial technical response came in roughly three minutes, and the unwanted traffic was subsequently stopped.
What I like and what to know
What I like
- Cheap enough for hobby and small-service infrastructure
- KVM VPSes work well for normal Linux workloads
- IPv6 is available
- Multiple locations make multi-node experiments practical
- Support has responded quickly when I have reported problems
- No special platform required for normal Docker and networking work
Things to know
- I have encountered provider-side IPv6/networking issues
- These are inexpensive VPSes, not managed enterprise infrastructure
- I monitor CPU, memory, bandwidth, and service health myself
- I still keep backups and plan around the possibility of a VPS failing
- Plans, locations, and pricing can change
Who I think GreenCloud fits
GreenCloud makes the most sense to me if you are comfortable administering your own Linux server and want inexpensive compute for small applications, personal infrastructure, Docker workloads, networking experiments, or geographically separate nodes.
Want the VPS without doing all the server work?
If you need help setting up or operating the server, I also do deployment and self-hosting work: Linux VPS setup, Docker, HTTPS, monitoring, backups, application deployment, and related infrastructure.
Development & deployment helpThe GreenCloud VPS button is an affiliate link. I may earn a commission if you purchase through it.
Early impressions · Currently evaluating
Servitro — Frankfurt, Germany
I only recently brought this VPS online, so this is not a full review yet. I’m using it as Wurstcase, a European node for DN42, Yggdrasil, WireGuard, and other networking/infrastructure experiments.
What immediately surprised me was the network latency. Initial IPv6
latency from my connection in Pennsylvania to Frankfurt has been
around 90–95 ms, which is better than I expected for
a transatlantic VPS. My first two ordinary Windows ping runs to
wurstcase.kgivler.com averaged 92 and 94 ms.
Those eight ICMP replies are a very small sample, not a serious network benchmark. The lack of packet loss in those samples and the latency are simply a very encouraging first impression for a low-cost European VPS.
More testing to come: I’ll expand this section after I’ve had enough time to evaluate uptime, routing, sustained performance, and support.
First IPv6 ping samples
- First run: 90 ms minimum, 96 ms maximum, 92 ms average; 0% packet loss.
- Second run: 89 ms minimum, 103 ms maximum, 94 ms average; 0% packet loss.
The Servitro button is an affiliate link. I may earn a commission if you purchase through it.
For VPS Providers
Want me to review your VPS?
I'm open to reviewing other VPS providers, especially inexpensive KVM VPSes, IPv6 deployments, unusual locations, interesting network configurations, and services aimed at self-hosters or developers.
Providing free or discounted service does not guarantee a positive review. If a provider supplies the service being reviewed, I will disclose that.
Contact me