I don't think so since the files are that small in size.
We have faced the similar trouble.
First, some of video files may contain unusual frames.
If users play such a video using recent version of Google Chrome or Microsoft Edge, a large number of file transmission requests (range requests) are sent from web browser to web server.
Sending file transfer requests continues as long as the video is playing.
This trouble occurs not only with the Moodle, but also with other web sites.
Even if the video file contains unusual frames, it can be played normally on the video player of the PCs.
Therefore, it is difficult to detect the unusual frames before uploading the video.
Even if the Web server prohibits rage requests, transfer requests will overflow after the user's playback position reaches the unusual frame.
A similar bug occurred in the Google Chrome around 20165 or 2016.
Recent versions of the Chrome and the Edge use range requests as standard when downloading media files.
So, I guess that the similar bug has occurred.
First, some of video files may contain unusual frames.
If users play such a video using recent version of Google Chrome or Microsoft Edge, a large number of file transmission requests (range requests) are sent from web browser to web server.
Sending file transfer requests continues as long as the video is playing.
This trouble occurs not only with the Moodle, but also with other web sites.
Even if the video file contains unusual frames, it can be played normally on the video player of the PCs.
Therefore, it is difficult to detect the unusual frames before uploading the video.
Even if the Web server prohibits rage requests, transfer requests will overflow after the user's playback position reaches the unusual frame.
A similar bug occurred in the Google Chrome around 20165 or 2016.
Recent versions of the Chrome and the Edge use range requests as standard when downloading media files.
So, I guess that the similar bug has occurred.