Since the evening of July 15 (KST), my public share gonidash.shares.zrok.io (token mo5dzangs8k7) has been unreachable from Asian networks. Requests from Korea (and via a Tokyo VPN exit) return either: "share not found! are you running zrok share for this share?" or "503 Service Temporarily Unavailable" Meanwhile the same URL loads perfectly from a US network the entire time, and status.zrok.io shows no incidents. Details: - Agent: zrok2 on Windows, backend proxy -> http://127.0.0.1:8000, headless - Console (myzrok) is reachable from the affected network and shows the share as active — only *.shares.zrok.io fails - Share was re-created after a reboot on July 16 06:25 KST; the problem existed before the reboot, so it is not agent-side - Rebooting, cache clearing, and different devices/networks in Korea were tested; all fail the same way This looks like an APAC frontend node with a stale share registry or an unhealthy instance. Could you take a look?
Bro, I’m having the exact same issue. It happened a few times this afternoon (Taiwan time), and I thought it was just my other polling script causing zrok connection errors.
But by tonight, it’s just non-stop 502, 503, and "public domain not found" errors. I’m guessing there’s an issue with the Asia node. Really hope they find the root cause and get it fixed soon!
Wow, I thought it was just an issue with my connection.
I'm also in Taiwan, and I kept restarting my system, but it still didn't work.
It wasn't until I came here that I realized we were all having the same issue.
Same issue in Australia today - I've been rewriting all my scripts and checking server logs for the last hour trying to figure out what had broken!
Still happening in the Philippines.
Thank you all for the reports. https://status.zrok.io has been updating, and the team is investigating the issue.
Hi Everyone,
Service in the Asia region should now be functional again. We identified some bad shares causing some cascading issues throughout the system. We temporarily redirected our Asia traffic over to Europe to restore service in that region & will work on getting that endpoint online as soon as possible.
Thank you for reporting the issue, we'll keep improving our alerting but users are always the first to know.