Thanks for reporting this! The Explore page has been using APIv2 for the last several months. There was a bug in APIv2 causing it to incorrectly handling bounds with zero values, causing more results to be included than should be for these requests. The map tiles were not affected, leading to some of the discrepancies you describe here. We just released what should be a fix for this problem. Hopefully all APIv1 and v2 responses are consistent now, and the map tiles and returned data on explore are also consistent. Please let us know if you spot any more issues like this.