Cxckers
> People drank the 6 inches (150 mm) deep river of whiskey that is said to have flowed as far as the Coombe. None of the fatalities suffered during the fire were due to smoke inhalation, burns, or any other form of direct contact with the fire itself; all of them were attributed to alcohol poisoning.
No one was killed as a result of the fire. They all died from drinking to much of the river of whiskey. Wow
But you are right, no service is bulletproof
This is the case with all forms of gambling. I think that they know that the money is from others less fortunate. However, human nature seems to make us believe that somehow, we will be the lucky one.
Their statement yesterday:
Yesterday we unfortunately experienced technical difficulties which meant that Proton services were offline intermittently throughout the late afternoon and evening European time. During this period, incoming email, outgoing email, and push notifications were also temporarily delayed. As of 2:45AM Geneva time, all emails and notifications are caught up, but we are continuing to monitor the situation in case of further faults.
We can confirm that no data and no emails were lost. Due to our redundant infrastructure, emails that were not immediately delivered were queued and automatically redelivered. We are still investigating the issue, but what we can share so far is that the technical difficulties were caused by a software update that was conducted over the weekend which adversely impacted the performance of certain systems. Unfortunately, this issue only appeared under under high loads which we were not able to fully simulate in testing. Furthermore, because this was a major software and operating system upgrade, there was no way to roll back the software update.
This result of this was an extended period of intermittent outages and performance issues while we tried to work around the issue. We have now put a number of safeguards in place, and will continue to improve the reliability of our infrastructure to guard against this type of issue in the future. We apologize deeply for this issue and thank you again for your understanding. Our engineering team is currently conducting a root cause analysis and for transparency, we will be sharing results on the Proton blog after our investigation is complete.