Respecting @PoltoS and avoiding politics...
In the short-term, it may be prudent to plan for a loss of remote access via web and Z-Way app, cloud backup service, e-mail/notifications and this forum.
As best as I can tell, these services rely on access to find.z-wave.me, service.z-wave.me and forum.z-wave.me. To the credit of the Z-Wave.Me team, DNS has redundancy with name servers in Russia (NS8-L2.NIC.RU and NS4-L2.NIC.RU) and Switzerland (NS2.ALSENET.NET and NS1.ALSENET.NET). The name find.z-wave.me resolves to IP addresses in Russia, Switzerland and Germany, the name service.z-wave.me resolves to an IP address in Switzerland and the name forum.z-wave.me resolves to an IP address in Switzerland. Assuming the Z-Wave.Me team is willing/able to pay for these servers and DNS for z-wave.me is not blocked, a service disruption seems unlikely.
If there is a service disruption, a workaround for remote access involves having a public IP address configured with either SSH port forwarding or a VPN to communicate with z-way-server port 8083. A workaround for e-mail is discussed in this forum article:
https://forum.z-wave.me/viewtopic.php?f=3425&t=23036 (edit /z-way-server/automation/modules/NotificationChannelEmail/index.js and set up your own POST-able mailserver as discussed here:
https://forum.z-wave.me/viewtopic.php?p=65820#p65820). There's a simple workaround for cloud backups - just do a local backup. As for a workaround for this forum, the Z-Wave.Me team maintains a set of repositories on github (
https://github.com/Z-Wave-Me) that should provide an alternate mechanism for communication.
In the long-term, I expect we'll need to be patient and see how the situation unfolds.