[Bug] testnet-beta clients takes minutes to connect

[onetrickwolf]

🐛 Bug Report

testnet-beta clients seem to takes minutes to connect, sometimes greater than ten minutes before it will start syncing

log sample:

"2024-05-31T16:42:12.282Z","""node""","2024-05-31T16:42:10.988109Z WARN snarkos_node_router: Unable to connect to '34.168.118.156:4130' - '34.168.118.156:4130' disconnected before sending ""Message::ChallengeResponse"""
"2024-05-31T16:41:56.752Z","""node""","2024-05-31T16:41:55.260288Z DEBUG snarkos_node_router::handshake: Connecting to 34.17.53.129:4130..."
"2024-05-31T16:41:56.742Z","""node""","2024-05-31T16:41:55.358703Z WARN snarkos_node_router: Unable to connect to '34.17.53.129:4130' - '34.17.53.129:4130' disconnected before sending ""Message::ChallengeResponse"""
"2024-05-31T16:41:56.554Z","""node""","2024-05-31T16:41:55.161640Z DEBUG snarkos_node_router::heartbeat: No connected peers"
"2024-05-31T16:41:48.224Z","""node""","2024-05-31T16:41:45.841743Z DEBUG snarkos_node_router::heartbeat: No connected peers"
"2024-05-31T16:41:47.774Z","""node""","2024-05-31T16:41:45.939828Z DEBUG snarkos_node_router::handshake: Connecting to 34.17.53.129:4130..."
"2024-05-31T16:41:47.394Z","""node""","2024-05-31T16:41:46.037661Z WARN snarkos_node_router: Unable to connect to '34.17.53.129:4130' - '34.17.53.129:4130' disconnected before sending ""Message::ChallengeResponse"""
"2024-05-31T16:41:31.935Z","""node""","2024-05-31T16:41:30.418541Z WARN snarkos_node_router: Unable to connect to '34.168.118.156:4130' - '34.168.118.156:4130' disconnected before sending ""Message::ChallengeResponse"""
"2024-05-31T16:41:31.768Z","""node""","2024-05-31T16:41:30.224314Z DEBUG snarkos_node_router::handshake: Connecting to 34.168.118.156:4130..."

Steps to Reproduce

spin up a client with with the --network 1 flag e.g. snarkos start --network 1 --allow-external-peers --nocdn --nodisplay --client

Expected Behavior

Would expect it to connect much faster

Your Environment

• Latest mainnet: 85bd2b3
• 1.78
• Ubuntu

[onetrickwolf]

@vicsn for more context I have experienced this pretty much since testnet-beta went up when trying to stand up some clients for an explorer. I have not seen this in local devnets on the same branch.