Hello - i have a recently new rig with multiple nodes.
All nodes are over 1 month old. All nodes have completed the vetting status.
Yet for days - over a week, all US vetting status has been:
us1.storj.io:7777 (Vetting result pending > 513/100 Audits)
I dont see why? atleast to my knowledge the nodes live up to the requirement for vetting. (over 1 month old, and 100 audits) - this is not a single case - its ALL nodes.
Anyone know something i dont?
Thanks in advance! 
Us1 Need 1000 audits now
Thank you! noted
20 charrs
I have nodes that haven’t been vetted in 3 months (single node in subnet), on US1. It’s also vetted after about 700, not 1000 audits (as reported by the node’s API).
I’ve seen nodes become vetted with anywhere between 700 and 800 audits (on US1).
How long they were vetting?
For about 2 months.
padded for 20 chars.
Perhaps this is how it works now. Vetting requires at least 504 hours. Ideally, it should take a month. But, as far as I understand, the number of audits is constantly changing, so these requirements can fluctuate or shift. Perhaps the number of required audits on US1 needs to be adjusted again.
I asked the team to check.
Please provide NodeIDs for both cases
I can confirm that. Recently spun up some nodes, most of them are vetted by now, all of them stopped getting audits from US1 at some point, latest one is still stuck at 0
Hello @das_ike,
Welcome to the forum!
When the node was created and when vetted and what amount of audits then and now?
Please also post the NodeID.
this is the youngest node, online about a week now, obvioulsy not vetted yet, but collecting, everywhere but from US1:
1DZDgnD6s9atjmYKfqmtTUXmABnX8fgNx6hFafmG9HEUyTtJ5n
ap1 (35% Vetted > 29/100 Audits) joined 2026-07-02
eu1 (35% Vetted > 72/100 Audits) joined 2026-07-02
us1 (0% Vetted > 0/100 Audits) joined 2026-07-02
one of my “older” nodes, 124JtNgZoJwdr2hYsKNxhCYYuao8x12mMhn3WWY2EbRLQvP7vud, recently got vetted on EU1/AP1:
ap1 (OK) vetted 2026-07-05
eu1 (OK) vetted 2026-07-07
us1 (95% Vetted > 93/100 Audits) joined 2026-06-14
I just went through the logs on all of them, they all have seen the last audit from US1 on 2026-07-04
I can provide those nodeIDs aswell, in case you need them.
Edit: I do see traffic coming from US1 sattelite to all of my nodes, that works…just no audits.
The vetting checks are different now:
yes, i am aware of that. observation is just that US1 has not been doing anything vetting-vise for a week now
i checked this on multiple nodes, same result everywhere:
docker logs storagenode | grep “GET_AUDIT” | grep “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S” | tail -n 1
2026-07-04T05:46:09Z INFO piecestore downloaded {“process”: “storagenode”, “piece_id”: “Y7BBWWTIGQUCHUC5ARNACEQGZUGWC2YOL2SUG2BU3LXWD2CJN4YQ”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET_AUDIT”, “offset”: 98304, “size”: 256, “remote_address”: “xxxx”}
2026-07-04T15:34:34Z INFO piecestore downloaded {“process”: “storagenode”, “piece_id”: “E2AFDPSRP4VNHFQPJZQUBE7XWHUEU557SYYIZLFLTW5SUO3WQNLA”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET_AUDIT”, “offset”: 1050368, “size”: 256, “remote_address”: “xxxx”}
2026-07-04T14:01:23Z INFO piecestore downloaded {“process”: “storagenode”, “piece_id”: “Y5F4YSOLCWCRVHAKHL7N46EZ5NGBQAMPZMQ3H5O3LBZEBKCPA4SQ”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET_AUDIT”, “offset”: 108032, “size”: 256, “remote_address”: “xxxx”}
2026-07-04T13:26:49Z INFO piecestore downloaded {“process”: “storagenode”, “piece_id”: “H433XJIKQGPB5A5O3U7CWVW5WXOP2IGB5LORWHNUN3NP2PLR4GFA”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET_AUDIT”, “offset”: 1558016, “size”: 256, “remote_address”: “xxxx”}
2026-07-04T15:22:48Z INFO piecestore downloaded {“process”: “storagenode”, “piece_id”: “FVIXUYS5LWTUMYQPQBNMMA6V4M25BI3WUPEQMVVY747QZDFA2BPQ”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET_AUDIT”, “offset”: 126720, “size”: 256, “remote_address”: “xxxx”}
2026-07-04T13:28:20Z INFO piecestore downloaded {“process”: “storagenode”, “piece_id”: “FH5PJOJEDPIMFNTDGFQBGIDRR6NBAEQXL5SBATZOY4MGIWUJQUWQ”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET_AUDIT”, “offset”: 284928, “size”: 256, “remote_address”: “xxxx”}
2026-07-04T15:35:41Z INFO piecestore downloaded {“process”: “storagenode”, “piece_id”: “WT4BW52BDLU6XFMW2KD7A6J6FJ7LEEMBBVZGJH3Q73FHY4CHWS3A”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET_AUDIT”, “offset”: 9472, “size”: 256, “remote_address”: “xxxx”}
2026-07-04T07:49:50Z INFO piecestore downloaded {“process”: “storagenode”, “piece_id”: “5VCMFPZBJKWNCSE4IHX5ELMVDXWXO5FDG6KPSN5BX5CINFYI4IUQ”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET_AUDIT”, “offset”: 105728, “size”: 256, “remote_address”: “xxxxx”}
@Alexey just noticed something, probaply just a coincidende…
the status tracker https://status.storj.io/ shows issues on the US sattelite the exact same day the audits stopped coming…not that something silently died there…
also seems to be having issues since July 1st.
It’s likely uses the old DB, so the data is stalled. I would ask the team to do not forget to migrate it too.
Too early to make any assumptions. Your nodes are too young.
The number of audits you can see on the storagenode API or via metrics. Since audits are coming, they are accounted.