All these 5 notifications have failed to be delivered to the devices because they were offline at the time, and these devices in particular have been offline for a while.
This usually happens if the push token has changed for some reason (migrating to a new device, restoring from backup, deleting and reinstalling your app, etc.), but your server has not been updated to use the new token for this user.
It could also be that these particular devices have died, given to someone else or sold, and so on, in a way that the device identifies by that token no longer exists. These are common occurrences.
When you say "same notification sometimes works", if you are implying that one notification to the same push token fails, but another works, then I would like to see the apns-ids for those 2 push requests to compare.
If the device exhibiting that on/off behavior is one other than the devices you listed here, it is also possible that device is on a less reliable network connection that could be going offline frequently.
Notifications not reaching devices for various reasons is commonplace. The only case that would be out of the ordinary is if these specific devices have received notifications in close proximity to the ones that failed, in which case I would like to see the apns-ids.