We just witnessed this same behavior multiple times this week using Premium Verizon CDN - it's not related to app deployments or file size (<1MB).
The edge pops cache a 0 content length payload in specific regions. When navigating to the resource in chrome it downloads the file (content-type is incorrectly set to application/octet-stream) of 0 bytes. The only solution is to purge the profile which forces a re-validation to the origin and the situation is resolved.
This does not seem to be caused by origin timeouts or errors - we have no data logs corresponding to the outage timelines.
We are considering migrating to another CDN provider - there is nothing our app is doing improperly. We are testing shortening our TTL from 10m to 5m to see if the situation improves.
Update - we did find a route config that was responding with 0 byte 200 which the CDN was caching - this was a bug in our routing proxy, not the CDN or the app. Good luck to others!