It’s very hard for people to review logs if they look like a scrabble board and run in reverse chronological order. I suspect you copied the console line entries. Formatting them with </> would make them marginally more readable. What would be useful would be to click on the console line for each JR and copy the JSON and paste, formatted with </>.
But glancing through it, I can see you’ve got the last entry at 20:25:42 showing the DevAddr which looks to be assigned to 8680000130765278 on it’s JA but the payload field is reporting the other serial number. As it’s the payload formatter decoding, sight of this would be appropriate.
It’s not clear what a downlink would have a payload that includes power info & the serial number - usually they have settings information in them.
The Frame Counter would be useful too.
Overall, Ockham’s Razor comes to mind - Sherlock Holmes would put it another way - is there any chance that devices & serial numbers have got mixed up?
As @kersing says, this is an informal support forum, even if we can definitively prove an issue with the last release (have you looked at the commits for it to see if the Join Server / Network Server have been changed?), it is not the way to submit bug reports. Either use your TTI support contract or lodge this on GitHub.