Our users are able to connect now. Having to flushdns on some, but can confirm connections from western Europe and eastern US.

Thank you for the resolution.

I'm also considering TntDrive https://tntdrive.com/

But, I really don't want to have to migrate over 500 users.

I can't log in to Twitter while on my work network, but perhaps someone can send a message there?

https://twitter.com/msp360

It's become very obvious this is not a simple DNS propagation issue and there's a much larger problem going on.

Please give information on what is going on when we can expect to have access to the product we've paid for again.

It's been 3 days since this thread was started. Can we please get an update of some substance?

I definitely understand the migration issues, but a workaround that can be used right now is in understanding what's been updated for the A record. That would be a viable short term option until the DNS propagates. I'm playing around with my host file, using the historical A record entries and able to get further down the path in that I'm no longer getting the for sale page, but now getting to a 403 when it gets to the cloudberrylab.com portion of the activation (specifically, http://www.cloudberrylab.com/payment/ActivateLicense). Below are the host file entries I'm using. Are there newer ip addresses that could be used in order to complete this workaround?

50.19.243.6 cloudberrylab.com
52.70.87.11 foris.cloudberrylab.com

Do you have an ETA? I have several users that are dead in the water.

So, looks like it might be the low road and the domain was allowed to expire. If it's helpful to others, I see the A record for cloudberrylab.com was changed around 9/24 to 91.195.240.13, which would correspond with the expiration of the domain registration in whois. Before that, the A record history has it pointing to 50.19.243.6 and was there for several years until the expiration. So, the A change was likely the registrar updating it to the current "For Sale" location. I'm starting to mess with host entries and Route53 to point all requests to that ip (hoping it's not toast too). Hope this helps someone.

For anyone reading this, I see the activation is trying to hit foris.cloudberrylab.com . It's incredibly disheartening to see the response is a webpage saying the domain is for sale. It seems that they're finally trying to sunset references to Cloudberry in preference to MSP360 and the forwarding at the DNS is incorrect. If we could get an answer as to what the actual destination is supposed to be, this could be solved right now with an entry into the local host file or and entry into Route53.

David, it's becoming obvious right now every user of the Cloudberry Drive product is down. Can you please provide us with some information (particularly pertaining to entries we can put into our DNS for forwarding) to use so we can create workarounds so that we can use the product?

I think handling our DNS as a workaround would be applicable for the time being here. But, would need the destination information if you can provide. Is that a possibility?

We still have this problem with our machines with the Pro version. Can you post the url and ip address info so that we can implement a workaround with Route53 or host files in the meantime?