Please don't read this file with IE, it won't work, use Firefox or Chrome Stats for 03112018 run at 23:56:01Z run on vm-lnx-hce-heap1a.ncep.noaa.gov We sent this many CAP messages (1 per segment): 1143 We received this many responses to our CAP messages: 1130 We received this many uninteligible responses to our CAP messages: 0 ipaws_return_code | status | count -------------------+------------------------------------------------+------- 10 | Ack | 1 200 | Ack | 1093 202 | alert-signature-is-valid +| 1093 | +| | | 209 | message-references-expired-alert | 37 221 | invalid-CAPEXCHANGE-message | 37 300 | Ack | 1093 301 | non-IPAWS-alert | 37 401 | message-not-disseminated-as-NWEM | 1093 501 | message-not-disseminated-as-EAS | 1093 600 | Ack | 5 601 | message-not-disseminated-as-CMAS | 1088 602 | invalid-value-in-element-responseType | 88 606 | invalid-value-in-element-eventcode | 73 608 | marine-zone-SAME-geocode-not-disseminated-CMAS | 42 610 | lacks-parameters-to-generate-CMAM-text | 73 615 | signer-not-authorized-for-event-code-CMAS | 73 619 | signer-not-authorized-for-geocode_CMAS | 42 620 | referenced-alert-never-disseminated to CMAS | 112 800 | Ack | 1093 802 | public-blockchannel-disregarded | 1093 (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:08.678359