Recently, people have been saying "on-chain data is stuck," which is actually quite common: you click to open, and the front end first pulls data from subgraph/indexer; if they haven't synchronized to the latest block, you'll only get outdated data; if that doesn't work, it goes through RPC, but RPC also has rate limits, and when it's crowded, it times out and retries... what you see is just "waiting" all the time.

In simple terms, it's not that the chain has stopped; everyone is just waiting for the index to catch up, waiting for the node to respond, waiting for the cache to refresh.

When a bridge gets hacked, people are even more eager to "wait for confirmation"; the same goes for when a oracle reports errors earlier—lots of folks in the group are watching for callbacks, waiting for prices to return to normal before taking action.
I personally don't rush to criticize when I see delays now; I first check if the block height is correct, then see if I've been rate-limited on my side... Anyway, the hardest part is just waiting to figure out whether I should click that button.