NS 3.16.8 - Uplinks from one gateway stopped being considered by NS

Hello,

I’m running a Chirpstack V3.16.8 Network Server with about 20 gateway on it.
All has been working fine for month, but all of a sudden since the 27th of January, the uplinks of one of the gateway seem not to be seen by the NS.
The stats are however well received :

Checking logs of the NS, I can see that the stats are seen by the NS, but not the uplinks.

Checking directly on the MQTT topic of the gateway (i.e. gateway/24e124fffefbd281/event/+), I do see uplinks coming from the gateway (red ones):

I don’t mind loosing the history of this gateway, but sadly I’m not sure where to start digging to solve this issue.
To be noted that I tried deleting and re-creating the gateway via the AS web interface, but it did not help.

Thank you in advance for any hint !

By the time this issue was validated by a moderator, I noticed that the time reported for uplinks is about 20 minutes late compared to the time reported for stats.

Looking at the last screenshot, the uplink arrived on MQTT at 11h06m22s UTC but the time it contains is 10h44m UTC, which is a good 20 minutes difference.
On the other hand, the stats arrived on MQTT at 11h06m27s UTC and the time it contains is 11h07m17s, which is much closer with less than a minute difference.

Could it be that stats are accepted by the NS but not the uplinks, due to time they contain being too far from reality ?
I didn’t find logs from the NS stating this, it’s like the uplinks are invisible to it, so it’s a blind guess.
I also didn’t find any code related to expired time in the github of the NS, but maybe I’m looking at the wrong place.

Do you think it’s worth aligning the time ?

Thanks again in advance for your inputs :slight_smile: