Cna you provide the actual WMS GetFeatureInfo request (hide the second half of the instance ID), so that we can understand the problem?

https://services.sentinel-hub.com/ogc/wms/d026c463-d9fa-430d-a56a-?version=1.1.1&service=WMS&request=GetFeatureInfo&srs=EPSG:4326&query_layers=FALSECOLOR&bbox=5.1168898882241605,61.18561468142283,5.11690988822416,61.18563468142283&width=101&height=101&time=2020-3-26&X=50&Y=50
https://services.sentinel-hub.com/ogc/wms/d026c463-d9fa-430d-a56a-?version=1.1.1&service=WMS&request=GetFeatureInfo&srs=EPSG:4326&query_layers=FALSECOLOR&bbox=5.239810302044441,61.16641402825769,5.239830302044441,61.1664340282577&width=101&height=101&time=2020-3-26&X=50&Y=50

Both result in 2020-03-22 11:14:10

Hi,
unless I am mistaken, your GetFeatureInfo requests use Sentinel-2 L1C dataset. On Playground link you are displaying Sentinel-1 dataset. It is therefore somehow expected that the dates will be different…

Another thing I notice is that your TIME parameter is 2020-3-26, not “FROM/TO” as described in the specifications:
https://www.sentinel-hub.com/develop/documentation/api/ogc_api/wms-parameters

When defining time in this way, the service will choose the “best scene” (based on PRIORITY settings) from “start of time” to the defined date.

I hope this helps?
Best,
 

Emberassing detail that I completely overlooked. Super! Thanks a lot.