Polygon block timestamps mismtach

when running the following query, one can see that earlier block heights have a later timestamp value than blocks that come after
cross referencing against polygonscan shows that the values are indeed incorrect. scope of problem is unknown

{
  ethereum(network: matic) {
    blocks(height:{between:[18279190, 18279192]}) {
      height
      timestamp{
        iso8601
      }
    }
  }
}

Seems like the problem is genuine. I have raised this issue forward to the technical team.

This issue is caused by reorg needs to check data and reindex it.

It’s on the backlog.