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