All they had to do was to share the TXID(s) publicly and let a recipient take care of it. And if you were a recipient, you would have known the TXID and would have done a CPFP yourself, and solved Binance's issue for them. None did, and likely not because they didn't notice a "stuck" withdrawal transaction waiting to be confirmed.
Of course, ... "stuck due to low TX fees" is not truly why they paused. You know that, and I know that. They needed to stem the outflow, and that was a (weak) excuse as to why they were "temporarily" unable to service withdrawal requests.
Anyway, they've now resumed withdrawals, and anyone that requested a withdraw previously that was never delivered now has to withdraw again.
But as always, not your keys, not your coins. Plan accordingly.
All they had to do was to share the TXID(s) publicly and let a recipient take care of it. And if you were a recipient, you would have known the TXID and would have done a CPFP yourself, and solved Binance's issue for them. None did, and likely not because they didn't notice a "stuck" withdrawal transaction waiting to be confirmed.
Of course, ... "stuck due to low TX fees" is not truly why they paused. You know that, and I know that. They needed to stem the outflow, and that was a (weak) excuse as to why they were "temporarily" unable to service withdrawal requests.
Anyway, they've now resumed withdrawals, and anyone that requested a withdraw previously that was never delivered now has to withdraw again.
But as always, not your keys, not your coins. Plan accordingly.