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