> You just don’t know about it precisely because companies are normally not public and honest about it.
If a big company lost a ton of user data, I'd absolutely know about it, whether they have Apple-level secrecy or not.
If a big company lost a ton of user data, I'd absolutely know about it, whether they have Apple-level secrecy or not.
> This incident caused the GitLab.com service to be unavailable for many hours. We also lost some production data that we were eventually unable to recover. Specifically, we lost modifications to database data such as projects, comments, user accounts, issues and snippets, that took place between 17:20 and 00:00 UTC on January 31. Our best estimate is that it affected roughly 5,000 projects, 5,000 comments and 700 new user accounts.
https://about.gitlab.com/blog/2017/02/10/postmortem-of-datab...
Yes, most incidents from most companies don’t result in this kind of data loss, which is why GitLab stood out.
[1] https://github.blog/2010-11-15-today-s-outage/
[2] https://github.blog/2010-07-25-one-million-repositories/
Probably a few hundred TB or so. Maybe nearly a petabyte?
Of course there are people that avoid this, but I've seen very few places where their processes are sufficient to fully protect against it - a lot of people get by more on luck that proper planning. Often these incidents are down to cold hard risk calculations and people know they're taking risks with customer data and have deemed them acceptable.