We managed to pinpoint a single router that was behaving not as configured, and because of that the failover in the fibercut took more down then anticipated.
For now the issue in the router is resolved and we will continue to investigate the root case of the issue. After the root case has been determined, we'll do some managed failovers to ensure a fibercut won't effect our network like it did.