Tony Cook
EF2
I had no problems on a solid connection. When chasing in questionable data coverage the strategy should be to reduce the number of products you're pulling to get a better success rate and less of a 'log jam' when you do lose coverage.
When chasing, I just have BR1, SRV1, and MAYBE ET or VIL, but not both, and usually not either.
That's a good point. I probably tend to run too much, but I don't stream, so that is going to save some bandwidth. My connection was pretty solid during the times I was having problems with GR3. I guess my specific question is- was anyone chasing using KNQA and getting BR and SRV products during the times I mentioned (17:47:33Z - 20:32:39Z).
If others were getting these specific products with KNQA, then it was something with my connection. Otherwise, it sounds like the problem was not just with the NWS servers since I was using AllisonHouse. This is a behavior I have not seen before, and it sounds like the problem was widespread. It would be valuable to know exactly where the bottleneck is.
TonyC