Yeah, I think the download speed is now back to normal so maybe increased latencies was the issue.
If you fetch the data one day at the time (like I do, because I download 5sec aggregate bars), you can get around the lack of RTH parameter with the Unix millisecond timestamps that's the alternative way to query the data besides the dates. Calculating the timestamp itself is pretty straightforward, but there's a complication because these timestamps are in UTC timezone, so you need to adjust them to the exchange timezone AND take daylight saving time (e.g. ETD/EST for NYSE/Nasdaq) into account which is a bit of an extra hurdle.
Also I reported an issue that the volume data occasionally comes in exponent representation (e.g. "2.086556e+06" for 2086556, which is a bit silly) if the value is large enough that can mess up the JSON parsing. You don't necessarily see this issue if you use some JSON parsing plugin as the plugin may do the conversion automatically before viewing it to user as it did with your helpdesk person, but that's how the raw data comes in.
There's also some opportunities to reduce the download size overall and improve the download speed. Currently the data seems to come in as gzipped JSON format, but I further compress the data locally to ~30% of this with fairly straightforward custom compression method. If the data storage and internet bandwidth are major items in your bottom line (which I believe they are since it's your whole business), then this could be an opportunity to optimize and further improve customer experience
And also shout-out to your support, who has been very friendly and helpful that I have had a needed for couple of times so far
