CloudatCost and Pertino
-
Their silence is deafening...
-
There blaming it on rogers. I don't see how they don't have any failover.
-
@thecreativeone91 said:
There blaming it on rogers. I don't see how they don't have any failover.
A minute or two you can blame on a carrier, after that, the fault is not having failover. And after having already learned this lesson, there is no one else to blame at this point.
-
Six hours and even their Twitter feed is dead. They've not just gone offline as a product, they've gone dark as a company.
-
This the last of their Twitter feed. People having been Tweeting at them continuously and they are not responding to anyone.
-
The Twitter feed is pretty entertaining...
-
-
The Twitter people are right. This makes you worry not only that CloudatCost is having problems but it means that Fibernets doesn't have redundancy and is out and, supposedly, that Rogers is out too. Basically a huge chain of dependencies. This doesn't just make you question one company, this makes you question doing business with Canada! It's the entire national infrastructure being called into question here.
-
@scottalanmiller said:
The Twitter feed is pretty entertaining...
The last comment of this is probably the best thing I've ever read!
-
I am not surprised at all...
-
I wouldn't use their servers even in a test environment. Maybe a personal lab, but even that isn't worth the constant frustration.
-
@IRJ said:
I wouldn't use their servers even in a test environment. Maybe a personal lab, but even that isn't worth the constant frustration.
That's what I've decided based on all the down times and having my server not be able to boot. I really want the money back I paid.
-
Yup, at this point, even lab use is becoming a poor choice. Days of outages, no response at all. Zero response to customers. Too much effort even for a lab.
-
@thecreativeone91 said:
@IRJ said:
I wouldn't use their servers even in a test environment. Maybe a personal lab, but even that isn't worth the constant frustration.
That's what I've decided based on all the down times and having my server not be able to boot. I really want the money back I paid.
IT people have good memories and are not lenient on down time. Do this once and it will always be remembered. Do it twice and you will never gain full trust again, do it 3 or more times and its just rather pathetic.
There has been hours of downtime more than 3 times in the past 2-3 months if I am not mistaken?
-
@IRJ said:
They has been hours of downtime more than 3 times in the past 2-3 months if I am not mistaken?
Sounds right.
-
Just received the following via email:
Cloud At Cost System Message: 04/30/2015 05:06 PM We are having an issue accessing some of our network subnets due to a local car crash that caused fiber to be cut. Network Update: Our fiber technicians have confirmed that the target for full restoration is 8 PM EST today. We will provide updates as we get them. -
@Danp said:
Just received the following via email:
Cloud At Cost System Message: 04/30/2015 05:06 PM We are having an issue accessing some of our network subnets due to a local car crash that caused fiber to be cut. Network Update: Our fiber technicians have confirmed that the target for full restoration is 8 PM EST today.We will provide updates as we get them.
There are alot of "uncontrollable" disasters that happen to C@C
-
Cloud At Cost System Message:
04/30/2015 05:06 PM
We are having an issue accessing some of our network subnets due to a local car crash that caused fiber to be cut.Network Update: Our fiber technicians have confirmed that the target for full restoration is 8 PM EST today.
We will provide updates as we get them.To Unsubscribe : If you don't want to receive these messages please change your email preferences here https://members.cloudatcost.com on your profile page.
-
I just got the email too. That's a pretty long time to think up "car crash". Where was the email when the outage started?
-
@scottalanmiller said:
Where was the email when the outage started?
Maybe they host their own email server. That would certainly explain the long delay.
