Earlier quoted context omitted.
I think a communication like this should include that they are investigating the root cause (assuming they aren’t completely sure) and that they will share it, and state where. Maybe im reading to much into it but it bothers me that thats not in the communication.
I think the telecom issue playbook is significantly different than the SaaS playbook. Not sure if that’s just cultural or if there are other drivers - maybe paying customer telecom interfaces are simpler and more closed than typical SaaS?
IME, telecom as an industry is highly focused on the RCA, ICA, and uptime, and has had that embedded culturally for decades. Sharing the information publicly doesn't have much value, in the balance, unless there are a string of incidents where an acute perception problem needs to be addressed. This would more likely result in a marketing and advertising strategy rather than the sharing of technical RCA details. Additionally, one must consider that not all RCA details are fit for public disclosure. _You_ may be interested in deets, but John Q. Public is not interested beyond "Is it fixed yet?". If you want insider perspective, work in/with the industry. It's fascinating stuff.