Nodes offline since Jan 22 (~04:11 UTC) – ping satellite failed / UDP timeouts

Node Operators troubleshooting
1

Hi,

since Jan 22, 2026 around 04:11 UTC all my storage nodes went offline at the same time.

Nothing was changed on my side.

Symptoms:

- Nodes running locally, ports listening

- Storj dashboard shows all nodes offline

- Logs are full of:

“contact:service ping satellite failed – context deadline exceeded”

- Mainly affects UDP (QUIC)

- TCP works

- Multiple satellites affected

- Restarting nodes/server does not help

Environment:

- Docker nodes on Raspberry Pi

- Public IPv4

- IPv6 disabled (also tested)

- Ports forwarded correctly (verified)

Anyone else seeing similar issues in the last 1–2 days?

Possibly ISP routing / UDP filtering?

Thanks

2

Did your IP change? Are your nodes advertising themselves by the IP, or hostname (and maybe DDNS didn’t update)?

3

no, the IP address remained the same, I don’t use DNS

4

Hello @SlappyTT,
Welcome to the forum!

Usually it happens when either external or internal IP has changed.
Please compare your WAN IP on your router with IP there: Open Port Check Tool - Test Port Forwarding on Your Router
If they don’t match, your ISP put you behind their CGNAT, in that case you have several options:

  1. Ask ISP to give you a public IP, it could be dynamic, but must be public (WAN IP on your router will match the IP on yougetsignal)
  2. Change ISP to one, who offer a public IP
  3. Use a VPN with port forwarding feature, like portmap.io, ngrok, PIA, AirVPN, PureVPN, etc.

If those IP are match, please make sure that you updated your IP in the node’s configuration.
Please also make sure that your local IP of the host with the node is match the IP used in your port-forwarding rule on your router.
If you have a firewall, please make sure that you created two inbound firewall rules to allow the node’s port (28967 by default) for TCP and UDP. Please also make sure that you do not have any outbound firewall rules or they are disabled.

You can check that - open http://your-external-address:28967 in the browser on your smartphone with disabled WiFi. If your node is publicly available, you should see a page with the status.

If everything is checked, then please search for FATAL/Unrecoverable errors in your logs.

5

Hi, thanks for the guidance but the nodes worked for almost a year without any problems I just updated them whenever needed, as far as the web UI is concerned it works, RPI has the same local IP address which is hardcoded in the router as RPI, I have a public IP, port forward but only TCP works. It looks like the UDP connection is offline.
I also solved it with the ISP provider but they haven’t given me the required answer yet.

As for the errors in the log it says that the satellite can’t connect to my nodes… I’m sad about that because I’ve been offline for 3 days after a year… I think there will be a suspension until I solve the problem.

Of course I tested the ports from the outside they are accessible.
STATUS

Offline

QUIC

Misconfigured

I measure the availability of services via hatrixtool, and it is very strange that the bot writes to me in telegram that the servers are online, but in reality the satellites do not see them, so I suspect UDP routing
I think that hatrixtool only monitors TCP ports - which are open even after verification by port check tool

6

Could you please show the screenshot with the WAN IP and IP from yougetsignal?

Did you try to open the address and port of your node from the smartphone using the mobile internet?

7

Ignore UDP. Focus on TCP. You said your ports are open. How did you verify?

Locally?

How? Provide explicit steps how did you veirfy that. Especially, from what network?

Did you do the below? Do and report. Selectively ignoring quesitons does not help clarity.

What is written in your external address in the config file/docker parameter?

1 Like