I see there is something wrong with data from peers, like Segment error , after this any data is getting declined and capacity overflow at peer read (happened to me long time ago).
there is no log config at GUI, can be added later.
I uploaded new logs with level=trace, maybe useful to you https://filebin.net/c98gbt64q5nx9afb
Thanks
Iām testing the some prune nodes and archive nodes at same time (different public IPs) , same data center region.
I observed that the archive node is generating a lot of snapshots while download blocks still in progress, is it logic that archive node creates snapshot when the sync has not finished completely?
In the mean time, I also see several prune nodes have difficulty of PIBD sync, is there a relation with those snapshots of the syncing archive node?
Interesting catch. No, the node should not create any snapshots untill it is synced. So you detected a spam vector. I think you should turn this into a GitGub issue.
Yes. I noticed this too, they are coming from attachement message, not sure if bug or feature yet 
This was discussed at our development channel while ago (November 2025), Telegram: View @grindevelopment