If your cloud provider tells you they are shutting you down on date X, you want to fight as hard as you can until X and then shutdown gracefully to have a chance to explain to your users why your system is going down. If you wait until you get shutdown, you have no way of pushing a graceful shutdown anymore.
Oracle has no interest in running afoul of the US government at all. Their internal culture in many ways views them like that of a quasi-government institute. So in thus case they probably are feeling responsible to actually be the ones enforcing the law.
I imagine shutting down ByteDance is not like flipping a switch. They have a mountain of infrastructure and “shutting down” could mean nuking the data or otherwise getting it out of their cloud entirely. If it has to be done by a certain date you’d need to start nuking things well in advance to be absolutely certain you’re in compliance by the deadline. I’m surprised the shutdown happened as late as it did if this wasn’t a completely staged crisis.
That’s a trivial problem to solve though. Just push an update to the app that shows the „we were banned“ message if a specific API endpoint isn’t reachable anymore (and general internet connectivity is still there of course). Then you can operate as normal until your servers are forcefully shut down.
