GC6271 currently only has 1 find in our database. I will make sure it gets refreshed and corrected right away.
Sometimes, we do get some weird responses from the API to Geocaching.com. Since it's very very rare, it's very hard to track down what's actually happening, without logging almost endless of data. Usually it's related to connection issues are similar. It's something that we should handle better. These issues are more likely to happen to geocaches with a lot (many thousand logs) than others.
We actually have similar issues with users sometimes. It can happen that the response from the API looks like someone suddenly only has 0 or 30 finds, when they actually have many thousands. Again, this is most likely to happen to those which have many thousand finds.
These things usually corrects themselves quite fast, in that way it's unlikely that anyone notices it. But right now we are in a stage where we have long work queues and are quite behind on retrieving/updating data. The reason for this is that we have been going through a lot of infrastructure and core code changes lately. Our system works a lot with priorities though, so the most relevant data is what is fixed first. We will soon catch up and try to deliver a more smooth service again.
Regardless, this is something we are always trying to improve. As soon as we find something that seems like we can correct or make better, or more stable, we do so.