Hi all,
I’ve been experiencing a consistent issue with connecting to the æternity testnet using the Superhero wallet. The connection process is taking a long time, showing “connecting to node,” and then eventually shows a failed to connect error after a significant delay. This has been slowing down development and testing of our web app.
Is anyone else facing this issue? Any advice or troubleshooting tips would be greatly appreciated. Thanks in advance for your help!
Where are you located geographically, and can you please run ping testnet.aeternity.io and share the reports?
Recently, the AE node has been upgraded. The superhero wallet should also need an upgrade.
wallet now connects. i think this had to be an issue with the weak internet connectivity. thank you! 
We’re currently still encountering a few technical challenges within our team. Some team members are experiencing difficulty connecting their wallets, which is hindering their ability to interact seamlessly with our web application. Additionally, we’re facing delays in receiving responses from the smart contract, impacting the speed and efficiency of the web app. Moreover, the “connecting to node” process on the wallet is taking longer than expected, leading to delays in executing front-end requests.
Hey, sorry to hear that, than you for reporting !
Do you mean connecting the wallet to the dApp so it pops up, or connecting the wallet to the networks (slow connection issue)?
Could people with slow responses also share their pings to the nodes, please?
$ ping mainnet.aeternity.io
and
$ping testnet.aeternity.io
thank you !
I summon @dincho.chain to share an idea what could be wrong with our deployment ?
Our monitoring doesn’t show any anomalies to both gateways testing from multiple continents.
Perhaps you can try to traceroute it, or better tcptraceroute (port 443).
In general your issues looks weird as you’re able to ping an address in the same network segment (mainnnet .22) but not the testnet (.75) while both gateways are terminated in AWS cloudfront
