Today, on-chain data is "getting stuck" again. My first reaction isn't that someone is dumping, but that the layers of indexers/Subgraph/RPC are clogged again: you see the pot is still boiling, but the waiter (RPC) is being rate-limited, and the dish pass-through (indexing) hasn't even placed the new plate yet, so the frontend can only freeze and spin. To put it simply, the chain isn't broken; it's a data flow queue.

To turn the topic a bit, recent news about tax increases and tightening regulations, then loosening again, has caused everyone's deposit and withdrawal expectations to change, and the traffic surges, making rate limiting more obvious—feels like "the whole network is squeezing into the subway."
My current approach is pretty crude: wait one or two more blocks for key actions, open a few backup RPCs, check if two data sources match up, and avoid getting emotionally affected by that sudden lag.
That's all for now.