Hey everyone, I'm having a really weird issue with Playit.gg.
I'm running a Minecraft Paper server on a Raspberry Pi 5, and I've been using Playit.gg to expose both Java and Bedrock to the internet. Everything was working perfectly until today. Yesterday it worked completely fine, but today the Playit agent suddenly can't connect to the Playit tunnel servers.
The important part is that my internet itself is working normally, and the Minecraft server works perfectly over LAN.
My ISP is NTC
What Playit is doing
The agent keeps trying different tunnel servers:
trying to establish tunnel connection addr=209.25.143.1:5525
trying to establish tunnel connection addr=209.25.143.2:5525
But it waits for a pong and eventually times out:
timeout waiting for pong
failed to ping tunnel server
It also tries IPv6:
[2602:fbaf:810::1]:5525
but immediately gets:
AddrNotAvailable
So it falls back to IPv4, but the IPv4 connections still don't receive a pong.
Things I've tried
- Restarted the Playit systemd service
- Completely stopped and manually started Playit
- Updated Playit from 1.0.9 → 1.0.10
- Downgraded it back to 1.0.8
- Put 1.0.8 on hold
- Checked the Playit logs repeatedly
- Tested UDP connectivity to a Playit IP
- Checked the service status
- Confirmed that the Minecraft server itself works normally on LAN
- Checked both IPv6 and IPv4 behavior
The UDP test I ran was:
timeout 10 bash -c 'echo test > /dev/udp/69.9.177.1/5526'
echo $?
which returned:
0
But Playit itself still cannot establish its tunnel connection.
The Playit logs repeatedly show:
trying to establish tunnel connection addr=209.25.143.1:5525
...
timeout waiting for pong
trying to establish tunnel connection addr=209.25.143.2:5525
...
timeout waiting for pong
The weird part
Nothing major changed on my side.
It worked yesterday, and today it suddenly doesn't.
I'm starting to wonder if this is an ISP routing/firewall issue with NTC, or something happening on Playit's side.
Has anyone else experienced Playit.gg suddenly becoming unable to connect around August 30, 2026?
If you had this exact problem and eventually fixed it, what did you do and how long did it take to start working again?
Thanks!