Until the fix is identified, can't one 'march forward' by rolling back recent changes to a known-good state?
Also note, that roll back was a valid strategy back in the day and still can be useful tool in your garage of tools. It can be useful when, for example, dealing with complex legacy systems that were created decades ago, or complex systems developed by outsourced development teams. You'll know when roll back is useful when you see it.
If the business is losing $BIG_BUCKS per minute of downtime, it is most definitely a step forward.