I do see this:
Note this 31,539,436B video has had most of the content requested multiple times in several requests:
Content-Length: 31539436
Content-Range: bytes 0-31539435/31539436
Content-Length: 180460
Content-Range: bytes 31358976-31539435/31539436
Content-Length: 31506668
Content-Range: bytes 32768-31539435/31539436
Content-Length: 31375596
Content-Range: bytes 163840-31539435/31539436
which match what was requested.
I know this is something we’ve been actively working on improving lately; I’ll ensure the right team is aware.