You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When querying https://testnet-insight.dashevo.org/insight-api/blocks?limit=1, we are sometimes getting a payload with no blocks. This is breaking for us. Such as the one below
Perhaps related is the fact that https://testnet-insight.dashevo.org/insight-api/status often returns a payload where the blocks value is a number that is far behind.
We got this response on Wed, 24 Nov 2021 09:53:38 GMT, a time where the actual tip of the DASH testnet was 618900.
We were only able to reproduce this through programmatic calls. On the browser we always get the right response.
Are we somehow getting answers from a node that is stuck?
The text was updated successfully, but these errors were encountered:
When querying
https://testnet-insight.dashevo.org/insight-api/blocks?limit=1
, we are sometimes getting a payload with no blocks. This is breaking for us. Such as the one belowPerhaps related is the fact that
https://testnet-insight.dashevo.org/insight-api/status
often returns a payload where theblocks
value is a number that is far behind.We got this response on Wed, 24 Nov 2021 09:53:38 GMT, a time where the actual tip of the DASH testnet was
618900
.We were only able to reproduce this through programmatic calls. On the browser we always get the right response.
Are we somehow getting answers from a node that is stuck?
The text was updated successfully, but these errors were encountered: