hello webjoe. can i have a ticket id of yours? your affirmation that responses taked more than 1 day to arrive is not true. we have specific internal rules with our support staff to not have tickets updated more than 12 hours before a staff answer. tickets response can be delayed if you update the ticket many times, because each time you update a ticket the priority is reset. also opening multiple tickets will slow down response. also keep in mind that we have to investigate your problems before giving a response. also some problems cannot be fixed in 10 minutes if custom rules should be applied to firewalls or things like this. what kind of problems do you have with your vps with us more exactly? i would be happy to help you.
@webjoe: i have checked this ticket with our staff. we have checked your vps status. it is true it was offline for couple minutes, not being accessible via solusvm, because one of the clients having a vps on the same node, was sending ddos from his VPS. we have suspended it and everything went back to normal. from your responses, looks like our firewall blocked some legit traffic. we need to tune the firewalls in order to get best results. there is no perfect firewall who knows to sort out any kind of traffic. we need to know what application do you run on your vps, what ports do you use, port types and some details about your problems, like traceroute from where your vps is inaccessible, latency, etc. Your report is unclear. We can't guess what do you mean with "lagged out". Our test results are looking good. The server is accessible, was accessible and had no downtime, except couple minutes, because a client sending ddos from his vps hosted on the same node. We generally put low priority on tickets like yours, because there are many clients reporting inexistent problems, or problems caused by bad configurations on their side.
PS: Our staff asked you if you are sure that the VPS is down, because your VPS looks Online and accessible from our side. Also we had no alert about your IP in last 24 hours.
@webjoe: If only part of clients are unable to connect to the VPS, most likely it's a problem with route/path to/from the vps to/from the client. That's why we need a traceroute to the vps from an affected client. About the bandwidth, it is UNMETERED. This means we don't METER the bandwidth = Don't count it. That's why there is no traffic shown in the control panel.
@webjoe: If only part of clients are unable to connect to the VPS, most likely it's a problem with route/path to/from the vps to/from the client. That's why we need a traceroute to the vps from an affected client. About the bandwidth, it is UNMETERED. This means we don't METER the bandwidth = Don't count it. That's why there is no traffic shown in the control panel.
Hello, yes I understand that about unmetered. It does in fact show on the panel that I have over 9000 TB of available bandwidth
I was referring to the traffic activity on SolusVM, it has not updated in a week: http://i.imgur.com/19SyP6e.png
I understand this is not a critical issue, just an issue.
Support have come back to me now and said they have "deactivated Intrusion Prevention System" which hopefully will help. They have also blamed the lag issues on network congestion. I am sorry I had to bring this to a public forum but I feel we were being ignored, we moved to you because we were being DDoS'd by a competitor and we had every intention of staying long term. We even took the time and negotiated a fair price for a RAM upgrade. So we will see how things go for the next few days.