Repeated VPS network outages at Chimehost/Profuse/psychz.net

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Repeated VPS network outages at Chimehost/Profuse/psychz.net

Posted by Titanic_Tomato, 09-08-2012, 09:59 PM
I am sysadmin consultant with a number of VPS hosts on various providers. Six months or so ago, I moved a customer from their previous provider over to Chimehost.

For the first month or two, things were pretty good, but then it appears that Chimehost may have been bought out by Profuse/psychz.net or some other significant changes occurred (both the main website and routes changed about this time).

Since the changes, I have seen ongoing multi-minute network outages on this VPS. Usually it just drops off the internet right at the first hop or two outside of their networks, but we have also have instances where latency and loss were being highly variable.

Our IP is 173.224.217.211. We just had another 14-minute outage here a bit ago.

I am monitoring from Phoenix AZ and Seattle WA and both perspectives have been showing these outages each time.

We had another 30-minute long outage two days ago, on Sept 6th 2012 during the afternoon. When the host came back, uptime was normal and there wasn't any notable activity on the host, except for the complete inactivity in apache logs and via the locally-monitored snmp counters.

The VPS in question is a Xen-based VPS, 4GB RAM and eight cores. This isn't one of the cheapy 256MB RAM services.

Chimehost itself has been largely silent on the issue. When opening tickets, the support response has been fairly slow and completely clueless. They just don't care.

At this point, we are going to have to jump ship to another provider. It's not like things are going to get better. I have to assume the outages seen in the recent past will continue, and that's not tolerable to me or my clients.
Posted by Profuse-Jimmy, 09-08-2012, 10:12 PM
There was a scheduled maintenance planned for today and all clients were notified in advanced.
Posted by Titanic_Tomato, 09-08-2012, 10:43 PM
I have months of nagios outage logs, but I can't post them because Webhostingtalk limits new users to not being able to use CODE blocks. I tried.
Posted by nitro20, 09-09-2012, 07:53 AM
thnx for this informations
Posted by CW Mike, 09-09-2012, 08:30 AM
Sorry you've had issues with them however the site seems to be online at the moment, and it's a nice site.
Posted by Titanic_Tomato, 09-10-2012, 07:03 PM
Our VM is down again at this time.

Traceroutes get to distr.r1-700.psychz.net (216.99.148.234), and then it dies.

There were also a couple of other disruptions this weekend.
Posted by Titanic_Tomato, 09-10-2012, 07:45 PM
We are going on 30 minutes here of downtime and intermittent access.
Code:
user@host-->tcptraceroute 173.224.217.211
Selected device eth0, address 192.168.x.x, port 54615 for outgoing packets
Tracing the path to 173.224.217.211 on TCP port 80 (http), 30 hops max
 1  192.168.x.x  0.201 ms  0.099 ms  0.070 ms
 2  10.198.16.1  7.289 ms  6.106 ms  7.951 ms
 3  x.x.x.x (x.x.x.x)  8.867 ms
    wsip-184-178-205-152.ph.ph.cox.net (184.178.205.152)  8.351 ms  8.683 ms
 4  bellcorc01-te-0-0-0-5.ph.ph.cox.net (70.169.72.186)  14.676 ms
    tucscorc01-te-0-0-0-7.ph.ph.cox.net (70.169.72.156)  11.915 ms  12.601 ms
 5  mcdldsrj01-ae2.0.rd.ph.cox.net (70.169.76.225)  6.070 ms
    chnddsrj01-ae2.0.rd.ph.cox.net (70.169.76.229)  35.201 ms  8.742 ms
 6  langbprj01-ae1.rd.la.cox.net (68.1.1.13)  19.077 ms  20.734 ms  19.821 ms
 7  10gigabitethernet1-3.core1.lax1.he.net (206.223.123.37)  27.658 ms  21.350 ms  21.356 ms
 8  10gigabitethernet1-3.core1.lax2.he.net (72.52.92.122)  19.424 ms  20.529 ms  23.259 ms
 9  profuse-solutions-llc.gigabitethernet4-2.core1.lax1.he.net (66.220.10.122)  21.455 ms  21.919 ms  23.925 ms
10  distr.r1-700.psychz.net (216.99.148.234)  20.905 ms  22.629 ms  21.549 ms
11  * * *
12  * * * 
13  * * * 
14  * * * 
15  * * * 
16  * * * 
17  * * * 
18  * * * 
19  * * * 
20  * * * 
21  * * * 
22  * * * 
23  * * * 
24  * * * 
25  * * * 
26  * * * 
27  * * * 
28  * * * 
29  * * * 
30  * * * 
Destination not reached
Code:
user@host-->tcptraceroute 173.224.217.211
Selected device eth0, address 66.113.x.x, port 59691 for outgoing packets
Tracing the path to 173.224.217.211 on TCP port 80 (http), 30 hops max
 1  x.x.x.x (x.x.x.x)  0.665 ms  0.523 ms  0.593 ms
 2  gi2-4.cr02.tac.opticfusion.net (209.147.112.6)  0.712 ms  0.565 ms  0.431 ms
 3  gi2-7.cr02.sea.opticfusion.net (209.147.112.54)  2.215 ms  1.898 ms  1.901 ms
 4  64.125.186.33  1.890 ms  1.822 ms  1.845 ms
 5  * * *
 6  * * *
 7  te0-0-0-1.mpd21.sfo01.atlas.cogentco.com (154.54.47.189)  20.845 ms  21.089 ms  20.808 ms
 8  te0-3-0-4.mpd21.lax01.atlas.cogentco.com (154.54.45.101)  31.835 ms  31.550 ms  31.357 ms
 9  * * *
10  38.104.211.94  31.404 ms  31.295 ms  31.349 ms
11  distr.r1-700.psychz.net (216.99.148.234)  31.604 ms  31.491 ms  31.336 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
Destination not reached
Posted by Profuse-Jimmy, 09-10-2012, 07:55 PM
You'll need to contact the support desk for further assistance as they do not check these forums.
Posted by Titanic_Tomato, 09-10-2012, 08:03 PM
Attached is a quick grep/sed of a nagios log for this site over the last month or two. That's a lot of down time on our Chimehost VPS.

I definitely made a mistake by going with Chimehost. I'll have to try out another provider and hopefully will have better luck next time.

The following are just tags so other people can google this post and make an informed decision on their VPS selection needs: chimehost sucks, chimehost outage, profuse sucks, profuse outage, psychz sucks, psychz outage,
Posted by Profuse-Jimmy, 09-10-2012, 08:06 PM

Quote:

Originally Posted by Titanic_Tomato

Attached is a quick grep/sed of a nagios log for this site over the last month or two. That's a lot of down time on our Chimehost VPS.

I definitely made a mistake by going with Chimehost. I'll have to try out another provider and hopefully will have better luck next time.

The following are just tags so other people can google this post and make an informed decision on their VPS selection needs: chimehost sucks, chimehost outage, profuse sucks, profuse outage, psychz sucks, psychz outage,

I believe this downtime is isolated to your VPS only as we do not have any reports of outages.

Please contact our support if you need further assistance.