WaveSecure experienced a severe server overload on January 14, lasting about 5 hours from 1900 to midnight GMT. We know that many people rely on WaveSecure for the security of their data and the protection of their phone, and we take this issue very seriously. For that, we offer our unreserved apologies for any inconvenience it may have caused. We’ve investigated the issue and are currently compiling a list of to-dos to improve our service.
Just to give a short summary of what happened. Yesterday, we received coverage from several well-read print/social media, including the New York Times and Lifehacker. This was coupled with the fact that we’ve actually quadrupled daily user sign-ups since a month ago, and that meant that we had underestimated the demand we experienced at a high point (which occurred yesterday). We want to assure you that existing user’s data have not been affected by the overload; What was affected was the speed of user activations and log-ins.
The tenCube WaveSecure web team started work on fixing this issue almost immediately when it occurred, and by 12 midnight GMT, had implemented a solution that will ease our load, and WaveSecure has now resumed normal service. Our web team will be monitoring the situation over the weekend to ensure that we are able to adequately address future overload issues. As always, we are extremely happy with the positive feedback we have been getting from some of our users who wrote back to us expressing concern/support on the situation, and are in the process of answering all queries that have been directed to us regarding this issue.
We would like to also thank New York Times and Lifehacker for their coverage yesterday. Cheers and May the Phone be With you!
