Okay so since this is how this is going, let's do this.
As I mentioned earlier, this customer
still has not contacted me directly or opened a new support ticket when requested to do so many times. Only way I found this customer was by manually digging through tickets and finding this particular one -- not something I wish to do in the future, as it took far too long. Had the customer contacted me directly with his IP or information that would aid in tracking down his account, we likely could have posted a reply to this sooner. Guess that was his intent.
This particular user has been with Crissic for 13 months. In those 13 months, he has had 22 total tickets, 3 services (2 cancelledbecause it "wasn't good enough" and then he ordered a new one).
Of those 22 tickets, 10 of them are automated tickets relating to null routes due to inbound DDoS attacks towards two of his IPs. One of these tickets is an AUP violation for hosting an IRC server, 4 of them relating to IPv6 (adding IPv6, not working, rDNS), and a few other misc tickets.
The contents of an abuse ticket have this particular bit:
NOTE: DDoS attacks are not permitted on the Crissic infrastructure. Any further reports may result in termination of your service.
Repeated inbound attacks related to your services that could negiatively impact other customers is something we can and have terminated customers for. You have been given far more free passes than other customers have in the past. Inbound DDoS isn't something you can really control, but when it's related to IRC matters, we're far less lenient as it's likely an intentional target relating to the communities you participate in.
Another ticket (you referenced this here) you submitted, and then closed out yourself before a staff was able to respond to it. You closed it out, not us.
The particular ticket you mentioned being set to answered or closed without us replying, you opened and we stated what the issue was (JAX06 was being rebooted due to some issues with it). You then replied saying "thank you", so we set it back to answered without replying. A few minutes later, around when the node was booting back up, you replied stating it was down still. At the time I was entirely too swamped dealing with tickets and getting containers booted up that I flagged the ticket as answered instead of responding. Yes I should have responded, but the issue was resolved shortly thereafter. This was never done in any intentional way to be rude or anything of the likes to you, I was just busy trying to deal with tons of other customers also complaining about the node instability issues at the time.
Since you shared the contents of the support ticket and they are public, we're within our privacy rights to continue dialog in an effort to defend ourselves.
We are not obligated to change your IPs out, we never change customer IPs out. That's just how we operate. Maybe you should evaluate what you allow your "friends" to connect to IRC wise and stay away from skids.
I am sorry if your service was not what you expected, but we have 7000 other customers who are satisfied with their service, and most people do not complain about the way we handle our tickets.
If this is such a big issue, I'd be more than happy to issue a pro-rated refund for the remainder of your service.