Hi, re: > One of are clients are complaining about late product generation the > tends to occur daily around 0500 and 17Z. It appears the final file > destined to become these products seem oddly delayed. > > For instance, today for a product for a NEXRAD product for ABC for > timestamp 202005250530, this product was not generated until a product > > ABC_N0Q:NOAAPORT2:CMC:RADAR_US:BIN > > comes in at 20200525054332. I assume that you are referring to NEXRAD Level 2 data since the receipt latencies shown by three CMC machines for NEXRAD Level 3 data are reasonably low for the great majority of the day: https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD3+ldm-data.cmc.ec.gc.ca https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD3+ldm-nexrad2.cmc.ec.gc.ca https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD3+unidata1.cmc.ec.gc.ca re: > This is an ongoing complaint from the client. Is there a delay around > 05Z and 17Z that can explain this? We have been experiencing receipt delays (high latencies) for some of the NEXRAD Level 2 products recently. Latency plots for the two CMC machines that are REQUESTing NEXRAD2 feeds reflect the latencies that we are seeing: randomly chosen real-server back end to the idd.unidata.ucar.edu relay cluster: node3.unidata.ucar.edu - one of the backend machines of the idd.unidata.ucar.edu cluster: https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD2+node3.unidata.ucar.edu ldm-nexrad2.cmc.ec.gc.ca: https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD2+ldm-nexrad2.cmc.ec.gc.ca unidata1.cmc.ec.gc.ca: https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD2+unidata1.cmc.ec.gc.ca It is likely that the delays your user is referring are being caused by high latencies for products from particular NEXRAD radars as is shown in all three of these latency plots. The latencies in question are upstream from us, so we have no way of addressing the problem directly. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: BXN-896443 Department: Support IDD Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.