You reported similar behavior, yes, but that doesn't necessarily mean it's the same cause. What I'm saying is that this is the first time I've heard about this particular cause of price spikes from our developers. That doesn't mean it hasn't been around for a long time, I'm just saying I'm not sure how long it's been around since this is the first I've heard of this cause (again, cause, not the behavior). We've had other issues in the past that have caused similar spikes (like the bid>ask issue that has been discussed here before). Probably the behavior you saw 3 years ago was from the bid>ask issue.