mjl574
Member
- Nov 6, 2012
- 14
- 0
- 1
As frustrating as it is, the issue is with the vendor that provides the cloud service, not Verizon, and definitely not the NRB. Should the issue have been fixed weeks ago? Heck yeah! But blaming Verizon would be like blaming your ISP because Netflix stopped working due to an issue on their end. All the other websites you visit in my analogy are working, so it's obviously not the fault of your ISP. I am a customer myself, and I'm pissed, too. If you want somebody to blame, blame Syncronoss. You'll see in the cloud app that they are the company (not) providing the service otherwise known as Verizon Cloud.Continuing this thread going ... as today it's the 27th, another deadline passed that Verizon promised the broken Cloud will be repaired and all data restored.
Well... Verizon is fully placing the blame on the Vendor... this after nearly FIVE weeks of the Cloud being down. The supervisors and AD's have absolutely NO answer and the NRB is not answering any questions.
This incredulous fiasco is one of the most disastrous blunders for the many folks who need the data on the Cloud that we've backed up directly to the VZ Cloud. I for one have taken the approach that if the data is ever recovered, it's going directly to Google's Cloud. Verizon will never again have anything of importance stored on their servers or in their possession. I will only use their phone for contact, nothing more.
Verizon is also keeping this whole Cloud fiasco very quiet and I'm surprised no media has written anything about this blundering problem.
Nearly five weeks folks... what a cluster you-know-what!
