Concern regarding re-occuring node error Skewed timestamp for edge policy of short_chan_id timestamp too far in the future

[racarr202]

Hello,

I get a lot of the following errors (around 700 since June 9th).
While these errors are spread across many of my node's peers, some peers are definitely over-represented, appearing more frequently than others.

Any idea why this is happening. Should I be concerned and what is the recommended remedy?

I've check my nodes NTP synchronization and it everything looks good at my end.

2025-06-10 08:29:12.279 [ERR] DISC: Skewed timestamp (1901350653) for edge policy of short_chan_id(753758101838102532), timestamp too far in the future: peer=pubkey@IP:port, msg=ChannelUpdate, is_remote=true

[guggero]

That's probably just a weird node on the network sending out incorrect channel announcements. You can just ignore those.