Looking at the graph clearly shows a huge spike of incomming data before each downtime.
To me this looks like a DDoS.

It does beg the question though, why *does* the incoming data spike before the crash?

Hmm also what does the "totally purple not blue" mean? O.o

People on #cemetech keep reporting the site being down a lot, is this supposed DDoS still occurring? Perhaps someone is exploiting a glitch in one of the site projects like OmnomicIRC? Cemetech has had no lag or downtime at all, other than the self-inflicted database load yesterday from me importing all the UnitedTI data.

People on #cemetech keep reporting the site being down a lot, is this supposed DDoS still occurring? Perhaps someone is exploiting a glitch in one of the site projects like OmnomicIRC? Cemetech has had no lag or downtime at all, other than the self-inflicted database load yesterday from me importing all the UnitedTI data.

I don't go on cemetech that often but every time it's always been up for me with no lag or downtime really at all.
Also the anti-spam is blocking out many ip addresses which means I have to type in a captcha

I was getting 3Mbpsish bursts, and the networking on the host was dying. The stack on the client was fine, and it was simply reporting that no packets were going in/out of the server on the card. I moved the site that was getting DoS'd to a new box, and it works fine using an identical config to the current box, even after nightly DoS's since. I'm not sure what your experience with Windows Server is, but it's not exactly easy to drop the entire networking stack requiring a reboot with it. Also, assuming that 2Mbps of any sort of data provides an equal load is incorrect.

That's not even considering the frequent network outages on the datacenters side. It's commonly gone down for 4+ hours at a time, with frequent half-hour or so periods of downtime/high packet loss almost nightly.

Another issue is the frequent disk lag. I've had multiple days when I was unable to open a program or copy a file due to disk I/O taking seconds to respond.

All in all, your service was an unstable lag-infested piece of crap. I didn't really mind until I started trying to sell stuff off of my server, only to find people bashing my stuff after repeated downtimes due to your end.

As far as you posting graphs of my bandwidth usage, I consider that private data that you were out of line posting. You've even made comments to Barrett in the past about posting bandwidth statistics and information in #tcpa. Highly unprofessional.

The anti-spam measure to register is what ajanata was referring to when he said it's purple (not blue).

Anyway, I'm not going to sit here while you unjustifiably trash my service.

First of all--you contacted me once (not 3 times) about your network going down. I replied twice (after looking at graphs and logs that showed no evidence of a problem on our end) with troubleshooting questions/advice, and you never responded.

2.) You're in for a big surprise if you think you're paying a lot of money for a Windows VPS with the amount of RAM that you have.

3.) The fact that rebooting your VPS fixed your networking virtually proves that it was not something on the host side (this is ignoring the fact that no one else had problems).

4.) Even if it were something on the host side (which there is no evidence of), you can not blame the service for you getting DDoS'd. Shutting off your networking is a perfectly acceptable way to deal with a client getting attacked (even though we did no such thing).

5.) It has *never* gone down for "4+ hours." The longest datacenter outage was roughly an hour or an hour and a half, and this was because of a very serious hardware failure. The longest after that? Maybe 10 minutes (half-hour tops), and this only for people going through Level3. And that hasn't happened at all for about 6 or 8 months. It happens. They fixed it. Saying "It's commonly gone down for 4+ hours at a time" is a flat-out lie.

6.) No one else has had the disk lag problems that you've had, with the exception of one stretch of an hour or two. That should be telling. And what was I doing during that time? Troubleshooting. Helping you. Figuring out what was happening. Telling the client who was responsible (who pays way more than you) that he was causing problems for other people. Researching ways to limit disk I/O (which, by the way, would hurt you far more than anyone else).

7.) Ever heard the story of the boy who cried wolf? I can't count the number of times that you've assumed a problem on my end, only to have it be a problem on your end. It makes it very difficult for me to take things you say seriously--but I still do.

Could you please at least say what/who you are?