Figured I would hopefully save others from the annoyances I’ve had with their service. I experienced daily high packet loss to both my VPS and their website, including the control panel (greater than 50%, typically). The control panel was broken and couldn’t tell me the status of my VPS. When I asked for a root cause and fix for the packet loss issue the “senior admin” response to both of these issues is “It’s intermittent and under control”. It’s still happening daily, so not really under control. They never even addressed the control panel issue.
I decided it was best to just give up on it, and requested a refund a few days ago after experiencing the same issue every day for 3 days after my purchase. I’m still waiting for a response to that request, 4 days later.
Heh, you’re not kidding. Their website barely actually loads, and I gave up trying to see who they were using as a datacenter because each page load was taking north of 60 seconds, so uh, that tells me everything I could possibly need to know about their service.
Don’t want to be a devil’s advocate but can you provide something more than “I’m offended”? Let’s say issue ticket(s), status page links, other people complaining, etc?
Try running pings to virpus.com, had the same issue to my VPS public IP:
From Atlanta GA
PING virpus.com (208.67.20.36) 56(84) bytes of data.
64 bytes from virpus.com (208.67.20.36): icmp_seq=1 ttl=53 time=85.4 ms
^C
--- virpus.com ping statistics ---
11 packets transmitted, 1 received, 90.9091% packet loss, time 10116ms
rtt min/avg/max/mdev = 85.416/85.416/85.416/0.000 ms
From San Jose, CA (apparently the DC I was in is in LA)
RP/0/RSP0/CPU0:XXXXXXXXXXXX#ping 208.67.20.36 count 20 verbose
Tue Jun 25 16:01:42.027 UTC
Type escape sequence to abort.
Sending 20, 100-byte ICMP Echos to 208.67.20.36, timeout is 2 seconds:
Request 0 timed out
Request 1 timed out
Request 2 timed out
Request 3 timed out
Request 4 timed out
Request 5 timed out
Reply to request 6 (13 ms)
Request 7 timed out
Reply to request 8 (13 ms)
Request 9 timed out
Reply to request 10 (13 ms)
Reply to request 11 (13 ms)
Reply to request 12 (12 ms)
Reply to request 13 (13 ms)
Request 14 timed out
Request 15 timed out
Request 16 timed out
Reply to request 17 (13 ms)
Reply to request 18 (13 ms)
Request 19 timed out
Success rate is 40 percent (8/20), round-trip min/avg/max = 12/12/13 ms
First I’ve heard of Virpus but thanks for the heads up. More than 50% packet loss does not sound like a working infrastructure, much less one that should be marketed to consumers.
I tend to recommend sticking with more reputable providers, even if it means a couple of dollars extra on a recurring basis. Way too many kiddie hosts popping up, trying to make a quick buck during spring break/summer and then fail to provide adequate services when it actually comes time to provide service.
It may also be a good idea to check LET/WHT before committing into paying longer than month-to-month term with a provider.
They’ve actually been around a long time, I used them 10ish years ago and never really had any trouble. Wanted to do some testing with some stuff and saw they had a pretty decent deal for what I was looking for. Their page was working fine at the time, so didn’t think twice. Lesson learned!
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
[Thread #828 for this sub, first seen 25th Jun 2024, 16:15] [FAQ] [Full list] [Contact] [Source code]
Heh, you’re not kidding. Their website barely actually loads, and I gave up trying to see who they were using as a datacenter because each page load was taking north of 60 seconds, so uh, that tells me everything I could possibly need to know about their service.
Don’t want to be a devil’s advocate but can you provide something more than “I’m offended”? Let’s say issue ticket(s), status page links, other people complaining, etc?
Try running pings to virpus.com, had the same issue to my VPS public IP:
From Atlanta GA
From San Jose, CA (apparently the DC I was in is in LA)
Edited for formatting
Did you ever find the missing packets?
I guess the pigeons they use for L1 got distracted or eaten by cat?
Should have used 2549 for the QoS update.
oh ipoac someday you will shine again
First I’ve heard of Virpus but thanks for the heads up. More than 50% packet loss does not sound like a working infrastructure, much less one that should be marketed to consumers.
I tend to recommend sticking with more reputable providers, even if it means a couple of dollars extra on a recurring basis. Way too many kiddie hosts popping up, trying to make a quick buck during spring break/summer and then fail to provide adequate services when it actually comes time to provide service.
It may also be a good idea to check LET/WHT before committing into paying longer than month-to-month term with a provider.
They’ve actually been around a long time, I used them 10ish years ago and never really had any trouble. Wanted to do some testing with some stuff and saw they had a pretty decent deal for what I was looking for. Their page was working fine at the time, so didn’t think twice. Lesson learned!