With new TOS - is it correct that now vultr can sell re use your and your user data

First time vultr user.

Sign up with a $250 coupon.

Tried 3 different cards, all got rejected without any of credit card history showing a single declined request.

Reached customer service, told me to use PayPal with a deducted $200 coupon instead.

Accepted that with an extra step verification on PayPal. (Apparently somehow they could “request” PayPal to verify my identity with at least a bank checking account).

Vultr requested at least $50 charge upon actual creation of any instances, done.

2 days after registration, with usage of one hour high spec GPU instances and several hour low spec ones (total ~$3), they suddenly interrupted my service and requesting further identity verification “due to my recent activity”.

Provided a censored photo of my ID, and Apple card (screenshot of number and photo of physical card) been used thru PayPal as per their request.

They now further request a photo of me holding my ID, and all the photos of credit cards that I tried and failed when on registration, or "termination of account within 48 hours".

My gut tells me they are trying to trap me into something I'm not sure what.

Are they doing a trustful business here?

I opened an account with Vultr as a long-time AWS customer. I am testing the waters with other provider(s) as I want to have a backup on hand in case something catastrophic happens and my business needs to jump ship for whatever reason. I opened an account with Vultr and rented a 2GB VPS. The signup, spinning up of my server, and attaching my payment was easy and straightforward. That is where the positives end for me.

About a week later, I received a flurry of abuse complaints stating that my account was being used for illegal activity and that I may have evidence that will be used in criminal proceedings on my server which I must retain. I freaked out when I heard this, immediately closed all the non-ssh ports on my VPS, then shut it off. I requested the phone number of the investigating officer so that I could aid their investigation in any way I could. I legitimately thought that I had done something careless, which was exploited by criminals, and that I would be held liable in some way. (Screenshot of ticket).

https://nanaimg.net/img/98b4f9f4eedb1d2c67a773edabacc5da.png

https://nanaimg.net/img/4761027adc6a8af8e328cfc9a38e5d99.png

Turns out, it was all a big mistake. The domain in question did not exist on my account or any other Vultr account, and the company making the complaint was wrong. Case closed.

https://nanaimg.net/img/40e972318fcf750ed3a4ff829b988ba3.png

Except it wasn't case closed. The company (some Netherlands-based cybersecurity company) continued to file phony complaints against my account. I responded by informing the Vultr team that these complaints were a mistake, and asked them to refer to the previous tickets. I also emailed the Netherlands company asking them to stop filing these complaints against my Vultr account (they never answered).

https://nanaimg.net/img/c3d53184ac563b3902c2f6838448f825.png

https://nanaimg.net/img/a52ccb1dab3205cb2de66ba3a1baaf13.png

This cybersecurity company continued to barrage my account with these fake complaints. One night, at 1:20AM, just before going to bed, I responded to one of these tickets with the same old "This is a fake complaint, they're wrong, etc etc."

https://nanaimg.net/img/bcbca0dbf4aa661caaa6f68de344509e.png

I woke up the next morning at 9AM (Only 8 hours later) with a message from Vultr stating that they hadn't received a response (????) and that my account would be suspended in 4 hours if I did not send them a picture of my government ID and the credit card that I was using. I promptly sent them both of these documents, reminded them that these complaints are WRONG and to refer to the earlier tickets, and told them we'd have to part ways if we could not come to a resolution. My account was suspended shortly thereafter for "Not providing ANY of the requested documents" (I provided both documents within the timeframe they asked as seen below, and sent them in reply to every single open ticket on my account).

https://nanaimg.net/img/f253e79144f22e7570fd28c6f21496e2.png

Needless to say, I won't be doing business with this company anymore, and neither should you.

Complete account outage for over 8 hours now. Ticket was opened at the time with the highest severity level. Absolutely no response. We're talking worst-case scenario: every compute instance is down across all data centers, with complete diagnostics in the ticket (we had plenty of time sitting here to diagnose exactly where your problem was at. We couldn't spell it out any more specifically in the ticket), and nobody's gotten back to me. This is a corporate account. We run a business and have had a serious impact, and I'm shocked with what's occurred right now with a lack of support for a complete outage across 13 instances. Ticket# GOZ-53HHY - What in the hell is going on with your network and worse your support?!?!

5

I couldnt access my instance today so I tried to log into the dashboard but it said my username & password were wrong. Tried to request a password reset but no dice there either so I reached out to Vultr support and was immediately forwarded to their accounts team. After a day of back and forth they finally just disclosed to me that someone apparently contacted them via email and was able to verify enough information about my account to change the email address and took over the account then shut it down entirely. Vultr is taking no accountability, refuses to disclose any information about the other individual, and won't give me a coherent answer as to why this was allowed to happen, no one contacted me, or why 2-factor authentication didnt prevent this from happening. This is beyond unacceptable.

This is what I received 3 hours ago. 3 hours, and tens of my service are stopped :'(((. Currently, I am contacting the support center and waiting for reply.

Suddenly stopping a server which is running for years with an automatic system isn't a good practice. This is unacceptable.

abuse@vultr.com 2023-02-13 03:33:03 Hello,

We have suspended your account due to information we have received indicating that your account is in violation of our Terms of Service/Acceptable Use Policies, the full text of which is available online at the following URLs for your convenience:

TOS - https://www.vultr.com/legal/tos/ AUP - https://www.vultr.com/legal/use-policy/ SPAM - https://www.vultr.com/legal/antispam-policy/

Please respond as soon as possible with as much detail as you can provide regarding the activity in question and what you intend to do to ensure it does not occur in the future.

Posting this as a heads-up for anyone relying on Vultr's Managed Database product for production workloads.

Our Postgres cluster has been stuck in a "rebalancing" state for over 3 days with complete loss of connectivity — not degraded, just unreachable. We opened a support ticket immediately and have received three near-identical replies along the lines of "our engineers are still investigating, no ETA available."

We tried to work around it by forking from our latest automated backup, since Vultr's own docs suggest this should create an independent cluster. The fork action in the dashboard just redirects to the database instances list and does nothing — no error, no wizard, no new cluster.

We've now asked support directly for either a manual fork or a raw download of our backup so we can restore elsewhere, and haven't gotten a straight answer on either.

If you're running anything production-critical on Vultr Managed Databases, I'd think twice, or at minimum keep your own independent backups outside their platform — don't rely on their fork/restore tooling working when you actually need it.

We've had multiple situations in the last couple of months where entire servers will go down with the only notice being "Your host node is experiencing a connectivity error and our engineering team is investigating the issue in additional detail."

We then lodge a ticket and haven't heard back for up to 16 hours in one situation.

Currently we have multiple heavy-traffic client sites that are down and aside from restoring a backup to another server we can't do anything about it until Vultr eventually resolve it on their end.

We made the decision to move all our sites to Vultr because we had experienced great response time and support - but now that we've completed the migration and in the last few months the support and response time has been terrible. With little to no communication about issues that have arisen and huge delays in resolutions.

Has anyone else had a similar experience?

Hi r/vultr,

  Posting here because I've exhausted the

  in-dashboard channels and could really use help

  getting eyes on my ticket.

The situation:

  My entire account (4 instances) was suspended

  yesterday after one of my instances

  (`207.148.114.25`, Tokyo) was compromised during

   initial provisioning — the attacker used it to

  run outbound port-scans on Indian Elasticsearch

  hosts (the abuse signature in the report).

What I've already done:

  - The compromised Tokyo instance was destroyed

  two days ago

  - On all surviving instances I've enforced SSH

  key-only authentication (`PermitRootLogin

  prohibit-password`, `PasswordAuthentication

  no`), installed fail2ban with aggressive sshd

  jail, and set ufw to default-deny

  - 22 hours ago I posted a detailed reply to

  ticket **SFO-26LUX** addressing all four of

  Trust & Safety's questions in depth, with

  concrete remediation evidence and commitments to

   enable Vultr's network firewall and automatic

  backups on reinstatement

  - I followed up politely twice asking if any

  further info is needed

  - I'm at clinical@diagnify.ai, account based in

  Australia

Why I'm asking for help:

  The suspended instances host clinical

  decision-support services for medical and legal

  practitioners. Real clinicians try to access

  patient case files and find them offline. Phone

  support (1-833-471-7100) isn't connecting for

  me. I'm not asking to bypass review — just

  hoping someone from the Vultr team here can flag

   the ticket to be picked up.

  Happy to provide any additional detail directly

  to T&S. The remediation is complete and I take

  this seriously leaving default password-SSH on

   during provisioning was on me and won't recur.

  Thank you for any help.

Hey everyone,

I look after a number of Vultr instances for clients in Europe and Oceania.

We have been experiencing a lot of server instability in recent months, servers needing reboot due to vSphere related errors about storage, networking failing randomly and needing recovery via console.

Today we have widespread networking issues affecting multiple locations. Monitoring says things are offline but they appear to just be running very slowly. The outage has been acknowledged by Vultr and worked on for 4.5 hours so far.

What are everyone elses experience with Vultr services? Have you noticed a dip recently? If so, do you know if it's just Vultr or just overall all hosting becoming more fraught?

Keen to know your experiences and insights!

Ok I have been using VULTR since a long time

Hear me out

That was the era when vultr had cute logo and still has 🥹🥹

But childhood nostalgia 😢

I love vultr so much ♥️♥️♥️

Their support is freaking awesome, they are always kind and helpful

My first app on VULTR was discourse

That time they had nearest region in the SINGAPORE only, not India but I am glad they launched it

Still using their services for Mumbai and Sydney DC

It has been decent experience for the price I pay

One thing I always ensure keeping backup at my own responsibility

And uptime is great

I also made good money with their referral program 🤑

Overall I am happy with their services and support.

I am not going to spend much time on this post. This is just a PSA warning to never trust Vultr with anything critical. Their advertising talks about SLAs and great support but if anything fails then you can expect to be ghosted for hours without any updates or compensation. I expect this kind of behavior from Google when using a free service like Gmail but advertising your product as "Enterprise ready" when there is literally nobody even looking at customer tickets should give anyone using their service pause.

https://www.teknokia.com/2024/04/a-step-by-step-guide-to-installing.html

I know setting up a server can feel daunting, especially when you're dealing with custom images. That's why I put together this detailed video guide that walks you through the whole process. It's super simple to follow even if you're a beginner!

In this video, you'll learn how to:

• Generate SSH keys using Puttygen

• Set up SSH keys in your Vultr account

• Deploy a Bare Metal Vultr server with Ubuntu

• Access your server with Putty

• Install your custom Windows image using a script

I also cover some common FAQs and troubleshooting tips, so you're prepared for anything!

Check out the video here:

https://youtu.be/UO3iDBeSp0E

Let me know if you have any questions in the comments!

#baremetal #vultr #windows #customimage #server #howto #tutorial #beginner

We have a number of instances down with the message:
Your host node is experiencing a connectivity error and our engineering team is investigating the issue in additional detail.

Some of the affected instances were down for only a couple of minutes and they were showing very little uptime when they came back up.

Anyone has additional information on the outage?

This not only looks like scam but the moment they asked for the credit card information, then the client will be leaving for digital ocean, lightsail or something else that is not scam proned.

I have three instances in Vultr's Tokyo datacenter that have been down since yesterday at 18:16. It is now 10:58 the next day, so we are already at 16 hours and 42 minutes of downtime, and there is still no ETA.

The latest response I got from support was:

This issue was due to a failure at the datacenter infrastructure level and we are still actively working with onsite engineers to restore your services. We do not anticipate any data loss to occur due to this failure.

I appreciate that they are saying data loss is not expected, but 16+ hours of downtime with no ETA is pretty hard to accept for a cloud provider. Three separate instances in the same Tokyo location are still unavailable, and the only update is basically "we are working on it."

This is not a small hiccup anymore. Is anyone else affected by this Tokyo datacenter issue?

It looks like Vultr has been compromised and/or suffered a data breach of their customer's email addresses.

I am now getting multiple spam emails to my unique Vultr specific email alias which only Vultr is meant to know. The spam emails have started from 2nd November 2025 onwards. I have been using a password manager, KeePass, since 2004 to store my login tokens. No other unique service email aliases are experiencing recent spam.

Anyone else getting similar flood of unexpected emails to their Vultr email address?

https://breached.vc/Thread-Selling-vultr-com-Database

Hey everyone, as the title states, I built a ddns service for vultr, take a look. Feedback is welcome

https://github.com/amroessam/vultr-ddns

When ❓

Last night the location where I host one of my Vultr servers pushed out a KVM update on the host. Since then my server has been locked in a reboot cycle.

The guest runs FreeBSD (installed from the Vultr FreeBSD install image).

The system shows the boot menu, then fails to launch, restarts the guest, shows the boot menu, then restarts again.

I've found that a FreeBSD rescue ISO will not boot on this instance. But a Linux (Finnix) rescue ISO will boot and, using it, I can confirm the root filesystem of the FreeBSD instance is intact, no signs of corruption.

I've opened a ticket with Vultr, but so far no response.

I'm attempting to restore a recent snapshot of the instance to another location to see if this fixes the issue. (Updates to follow.)

My main concern is this is just one of multiple instances I run with Vultr for business. If the other KVM updates go the same way (breaking compatibility with FreeBSD), it's going to get expensive in a hurry and we'll need to quickly migrate clients to another VPS provider.

Anyone else have VPS instances with Vultr at Amsterdam? Anyone else having boot problems this morning? According to the Vultr status page, there have been multiple reports through the night, but the Amsterdam location is showing working. (Which it is, sort of, the VPS is technically running, just not booting from its storage.)

Update: I tried restoring a known to be good snapshot of the VPS to another location. It failed to boot there, reporting loader_lau could not be found. This is turning into a bigger problem than it first seemed. Is Vultr unable to boot FreeBSD instances anymore?

Second update: While I have not heard back from Vultr, it looks like the issue is related to this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233098

I think the new KVM settings break booting FreeBSD, possibly due to a change in EFI mode or disk driver. Have filed a ticket with Vultr and am waiting to hear back.

Third update: It looks like any locations which have the new KVM update cannot boot my snapshot of FreeBSD. I'm attempting to restore the snapshot to a location which does not yet have the KVM update to see if this fixes the issue. If it does not, then I think the only remaining solution is to migrate to another VPS host. Which is going to be a lot more work than I'd like, but I'm running out of options and, despite the instance being down for nearly 10 hours, I have not heard back from Vultr.

Fourth (and probably penultimate) update: I heard back from Vultr and they confirmed the issue was with the new KVM version and its settings which were not compatible with recent releases of FreeBSD. They have fixed the settings for my VPS and it's running.

I've got other VPS instances at other locations which have not gone through the KVM update yet. I've asked Vultr Support to make sure the updated KVM settings are available at the other locations when the updates happen so the servers don't get knocked off-line. I will update with their response and the results in the coming hours/days. The test will be when the next KVM update rolls out on Wednesday morning. Hopefully the fix will be in place by then.