Please don't read this file with IE, it won't work, use Firefox or Chrome Stats for 10242019 run at 23:56:01Z run on vm-lnx-hce-heap1a.ncep.noaa.gov We sent this many CAP messages (1 per segment): 731 We received this many responses to our CAP messages: 731 We received this many unintelligible responses to our CAP messages: 0 HCE had this many retries in connecting to FEMA: 1 Total failures to connect to IPAWS (message lost): 0 ipaws_return_code | status | count -------------------+------------------------------------------------+------- 200 | Ack | 685 202 | alert-signature-is-valid +| 685 | +| | | 209 | message-references-expired-alert | 46 221 | invalid-CAPEXCHANGE-message | 46 300 | Ack | 685 301 | non-IPAWS-alert | 46 401 | message-not-disseminated-as-NWEM | 685 501 | message-not-disseminated-as-EAS | 685 601 | message-not-disseminated-as-CMAS | 685 602 | invalid-value-in-element-responseType | 44 606 | invalid-value-in-element-eventcode | 55 608 | marine-zone-SAME-geocode-not-disseminated-CMAS | 27 610 | lacks-parameters-to-generate-CMAM-text | 55 615 | signer-not-authorized-for-event-code-CMAS | 57 619 | signer-not-authorized-for-geocode_CMAS | 27 620 | referenced-alert-never-disseminated to CMAS | 62 800 | Ack | 685 802 | public-blockchannel-disregarded | 685 (18 rows) (remember, for some reason, 705 really counts against the 3xx range) The Latency is the delta between the time we create the cap message and the time we get the response back from IPAWS.H:M:S.ms Average_Daily_Transmission_Latency 00:00:06.929107