Doing real traffic engineering where shared risk link groups do not exist for the active and standby links is a lot of work and, moreover, is hard to keep working as operators change their networks (for maintenance, for other reasons).
On top of the basic difficulty, there are other issues - layering makes this opaque, the service providers have become completely de-skilled, the business model for MPLS is getting killed by Over-The-Top providers who pretend they can give you equivalent service using multiple links and IPSEC tunnels. And so on.
All of the unexpected shared infra issues I’ve observed have been down at this lower level that never shows up at the IP layer.
I worked at two small ISPs, each with a fiber network spanning a few US states. They had their own databases to track this information, but as far as I know there was no central database. One of them used OSPInsight backed by a self-hosted SQL Server database. I don't know what the other place used.