Node not vetted on US1 after 30+ days all other satellites vetted

Node Operators troubleshooting
,
1

Hi,

My node has been running since March 9, 2026 and is still not vetted on us1 after more than 30 days. All three other satellites vetted the node around March 30-31.

Node ID: 14nx3k4rfAeadnMdPsExiit6JreCQh6FnbEvesRbAvFNhhupqs

Node version: v1.148.3 (up to date)

Vetting status per satellite:

satelite audit success audit total vetted
ap1 596 596 2026-03-30
eu1 3388 3388 2026-03-31
saltlake 412 416 2026-03-31
us1 403 403 Never

All scores on US1 are perfect:

Audit score: 1.0
Suspension score: 1.0
Online score: 1.0
Audit history score: 1.0
Not suspended, not disqualified
Additional info:

Node joined all satellites on: 2026-03-09
403 successful audits on US1 (well above the 100 vetting threshold)
First audit window on US1: 2026-03-12
QUIC status: OK
Disk allocated: 14.4 TB, used: ~274 GB
No errors in logs related to US1
All other satellites vetted the node within ~21 days. US1 has 403 successful audits with zero failures but vettedAt remains null. Could someone please check if there’s an issue with us1 vetting?

Thanks.

2

Hello @PaulRichez,
Welcome to the forum!

The vetting process a little bit changed, the node should pass at least 100 audits but also not less than a month. I shared your info with the team, maybe something should be adjusted.

1 Like
3

To be a little bit more precise: it’s I think 25 days and number of audits is increased and satellite-dependent. I think it’s 1000 for US, bit less for EU and 250 for others. Not sure about exact numbers. Last time for me US as well vetted ~10 days after others. Nothing to worry, just wait

1 Like
4

Thank you both for the quick answers!

@Alexey thanks for sharing with the team, I appreciate it.

@hwm.land that makes sense. I wasn’t aware the audit threshold was satellite-dependent (~1000 for US1 vs ~100-250 for others). That explains everything. I currently have ~407 audits on US1, so at ~8 audits/day I should be vetted around end of June. I’ll just wait.

Good to know this is expected behavior and not a bug. I’ll update this thread once vetted