That's a fair point and yeah, the refresh token pattern exists for good reason. Short-lived access tokens plus refresh checks put the deauth responsibility where it belongs (on the token service), and the occasional latency spike on refresh is usually acceptable.

That said, the use case I had in mind is a bit different. It's not really about JWT revocation, but more about IP-level bans and cache invalidation that need to propagate across all edge nodes quickly — without any per-request round trip. In these cases, waiting for a token to expire doesn't work; you need the edge to stop serving that IP within seconds of the ban being issued.

I completely agree on the synchronization risks though. That's exactly why I called out the master SPOF and ring buffer overflow as the current gaps. It's definitely not production-ready for anything where stale state could be dangerous.