Thanks for posting! Are you by any chance coming from behind a multi-IP NAT? We’ve seen some issues with that before, since we have separate nonce pools per-datacenter, and use IP stickiness to ensure the same client usually hits the same nonce pool. In theory clients should be implementing automatic retry on badNonce errors - not sure if dehydrated does.
I’ll also check to see if we’re seeing elevated nonce-related errors.
Update: Looks like dehydrated doesn’t handle retries, which exacerbates any nonce-related issues: https://github.com/lukas2511/dehydrated/issues/547