CloudatCon aka CloudatCost
-
@thecreativeone91 said:
@IRJ said:
While this is certainly entertaining why is C@C still wasting their time on ML trying to save face with a few rather than doing serious PR on twitter?
Trying what they can. It's non-recoverable at this point.
They may be able to save some face on twitter, but it should be obvious that ML is done
-
"Backed by Fibernetics", the ISP so bad that even CloudatCost doesn't use them, and they are the same company!!
-
I can't believe that CloudatCost not using Fibernetics for their ISP isn't a bigger deal.
-
@scottalanmiller said:
I can't believe that CloudatCost not using Fibernetics for their ISP isn't a bigger deal.
Funny thing is the ISP isn't even called Fibernetics. It's called NEWT and Worldline.
-
@Danp said:
Wow... my server has finally moved on to the "reimaging" process. Maybe that will be done in another 3.5 hours.
Impressive.... NOT!
Build finally finished. Unfortunately, I have no way to verify how long it actually took. Seems they log deletions, but not creation / imaging requests.
-
I still wonder why they are using TLS 1.0 and RC4 cipher for the SSL on the panel (and other parts of the site). It's old and has known vulnerabilities.
-
Got another build that is still pending after 4 hours.
-
@scottalanmiller said:
@Danp said:
@scottalanmiller How did they respond to your refund request?
They said that the account was suspended and the refund was in motion. We're arguing about other things, but there was no issue there.
Did you get your refund? still no response on mine paypal claim either. I did tweet the president of Fibernetics maybe he'll do something to get us a refund.
-
Just putting it out there that mine has reimaged
-
@nadnerB said:
Just putting it out there that mine has reimaged
Re-imaged? Do you mean built on CloudPro or you manage to re-image the old CloudatCost servers that had had their buttons disabled?
-
Cloud Pro... I didn't test the other one.
-
Not really re-imaging then, just imaging - because it's the first time.
-
Got another build that is still pending after 4 hours.
Just checked, and it's finally in the "reimaging" stage. Not sure how long it's been this way, but so far were at 14+ hours and counting since the initial provisioning request.
Nice alpha test you've got going on here, C@C!
-
@Danp said:
Got another build that is still pending after 4 hours.
Just checked, and it's finally in the "reimaging" stage. Not sure how long it's been this way, but so far were at 14+ hours and counting since the initial provisioning request.
Nice alpha test you've got going on here, C@C!
Don't worry, it is only a backlog and the backlog will be totally cleared out -10 hours ago. So your issues are all in your head.
-
@scottalanmiller said:
Not really re-imaging then, just imaging - because it's the first time.
It's all in the marketing
-
@scottalanmiller said:
@Danp said:
Got another build that is still pending after 4 hours.
Just checked, and it's finally in the "reimaging" stage. Not sure how long it's been this way, but so far were at 14+ hours and counting since the initial provisioning request.
Nice alpha test you've got going on here, C@C!
Don't worry, it is only a backlog and the backlog will be totally cleared out -10 hours ago. So your issues are all in your head.
For a back log that bad, they should have taken some laxatives
-
@Danp said:.
Nice alpha test you've got going on here, C@C!
Maybe you could test ReactOS alpha on C@C. It's the prefect storm. haha.
-
Still no refund as of yet. They've "escalated" it. No further update.
-
My machine came back online. At this point, a bit of down time doesn't matter too much to me since the machine did get migrated over to pro and rebuilt.... This is just a personal toy for now.
-
FWIW, the "backlog" seems to have mostly cleared up (new server sits at "pending" status for under a minute), yet the "reimaging" still seems to take well more than the 1-2 minutes they strive for.
