Your Node is Disqualified - EU1

Node Operators
1

Hi,

My node got disqualified due to changes in the IP addresses used by the EU1 satellite.

At the start of July I got an email saying my node was offline. I checked and indeed, QUIC was misconfigured. I tried to fix it but couldn’t figure out why it was happening. After a few days the node’s configuration reported everything was OK again, so I assumed it had resolved itself.

Looking back, I should have dug deeper, but the dashboard on Storj has been a bit unreliable since I started running a node, and that seems to be known on the forum too, so I didn’t think much of it. My online score also stayed at 100% the whole time, so nothing pointed me toward a real problem.

Then this evening I got the email: “Your Storage Node on the EU1 satellite has been disqualified and can no longer host data on the network.” My EU1 online score is still showing 99.91% right now. Nothing in the dashboard shows suspended or at risk, but apparently it was.

I dug into it and found the actual cause: I block some countries on my UniFi gateway, and have for a long time. The IP that eu1.storj.io resolves to must have shifted into one of those blocked ranges at some point, silently cutting off my node’s connectivity to EU1 without me realizing that was the reason.

It’s sad to see this happen after two years running the node. I probably shouldn’t have trusted the dashboard as much as I did, especially since it’s the main thing node operators actually see, and it clearly wasn’t reflecting reality here.

Is there any way to get things sorted for EU1, or is disqualification final once it happens? I understand this is likely by design given how the audit system works, but wanted to ask. If it’s unrecoverable, I’ll just keep running the other satellites, EU1 wasn’t especially active for me anyway.
Any tips on whether I should treat the rest of the node as fine, or if this is worth investigating further?

Any tips on how to prevent this in the future?

Thanks

2

I also had a node DQ’d from the European satellite this morning… however it was only offline for around 2 days and the other satellites show closer to 90% uptime (even after the recent continuous drops).

I think something else may be going on.

3

Unfortunately this breaks the Node T&C (intentionally fail to deliver), so any de-disqualification would be unlikely.

TBH, the only action I see here as making sense from Storj’s perspective is making this rule more explicit in node setup. We already have some advisory on various corner cases and popular setups, this seems to be a good addition.

You can start a new node on the same drive, possibly limiting it to the EU satellite, to again capture the EU satellite traffic.

4

Yes, having clear guidance on what not to block in the firewall would be a nice addition.

I’ve decided not to start a new node for now as my current node uses the space and I dont have any spare hdd. This was an unfortunate situation caused by an error on my side, so I’ll take that as a lesson learned.

What’s still frustrating is that the dashboard never gave me any signal to investigate further. And ironically, it’s doing the opposite now: 12 hours after fixing the actual connectivity issue, the online score suddenly dropped from 99% straight to 0%, instead of recovering. That really does look like a bug in the scoring/reporting logic rather than an accurate reflection of node health.

5

Just guessing, but I suppose, that node cannot speak to sattelite → no new information about online score → last score preserved, node has no way to find that online score changed.
It would be most probably possible to indicate, that last connect to satellite failed, last successfull connect to satellite time and so on, but if it’s worth the effert - hard to say.

6

What is the audit score?

7

100% - I haven’t been home to check on it, but will poke at the logs.

2026-08-04_dq
2026-08-04_dq844×354 22.1 KB

8

Mine would be:

afbeelding
afbeelding1047×432 30.5 KB

9

I ran into a similar issue last year on ap1: Ap1.storj.io Suspension Issues since 11/14/2025

Can you share a couple of the IPs you are seeing at your firewall, I’m curious if they line up with mine.

My issue resolved itself in ~24 hours, and I did not unblock the sactioned country.

10

@Roxor, @Dhend
This is weird. Could you please give me a NodeID?

11

12jxZEfRTL79tmMKkd6b1gfqdEawUuYE9Y3JVm8P6pthb3rAxrY

12

Asked the team to check.
I also saw this PR: https://review.dev.storj.tools/c/storj/storj/+/22617, it might help to fix the issue
Please don’t delete the data yet.

13

Same here. 4 Nodes which are about 4-5 years old. Never had a Problem and now, without any chnages…

14

Hello @Frieseba,
Welcome back!

Please give me your NodeID

15

1gqCCbmM4eJBmeTaJRdHa3m4px1zVks9tkWQUFPWiWxhvzoJ3g

12iLoGsPVK69qY9C5uBUV5xdXV7uubWs3wbNyR7oVCjuxUakytx

16

Shared with team to investigate, please don’t delete data yet.

17

It’s not DQ on EU1

It’s not DQ on EU1.