Please don't read this file with IE, it won't work, use Firefox or Chrome Stats for 10252019 run at 23:56:01Z run on vm-lnx-hce-heap1a.ncep.noaa.gov We sent this many CAP messages (1 per segment): 1046 We received this many responses to our CAP messages: 1046 We received this many unintelligible responses to our CAP messages: 0 HCE had this many retries in connecting to FEMA: 0 Total failures to connect to IPAWS (message lost): 0 ipaws_return_code | status | count -------------------+------------------------------------------------+------- 10 | Ack | 6 200 | Ack | 990 202 | alert-signature-is-valid +| 990 | +| | | 209 | message-references-expired-alert | 56 221 | invalid-CAPEXCHANGE-message | 56 300 | Ack | 990 301 | non-IPAWS-alert | 56 401 | message-not-disseminated-as-NWEM | 990 501 | message-not-disseminated-as-EAS | 990 600 | Ack | 28 601 | message-not-disseminated-as-CMAS | 962 602 | invalid-value-in-element-responseType | 53 606 | invalid-value-in-element-eventcode | 62 608 | marine-zone-SAME-geocode-not-disseminated-CMAS | 21 610 | lacks-parameters-to-generate-CMAM-text | 62 615 | signer-not-authorized-for-event-code-CMAS | 68 619 | signer-not-authorized-for-geocode_CMAS | 21 620 | referenced-alert-never-disseminated to CMAS | 74 800 | Ack | 990 802 | public-blockchannel-disregarded | 990 (20 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.044254