Please don't read this file with IE, it won't work, use Firefox or Chrome Stats for 03232017 run at 23:56:02Z run on vm-lnx-hce-heap1b.ncep.noaa.gov We sent this many CAP messages (1 per segment): 1370 We received this many responses to our CAP messages: 1368 We received this many uninteligible responses to our CAP messages: 0 ipaws_return_code | status | count -------------------+------------------------------------------------+------- 200 | Ack | 1231 202 | alert-signature-is-valid +| 1231 | +| | | 221 | invalid-CAPEXCHANGE-message | 135 223 | invalid-value-in-element-geocode | 1 224 | reference-element-invalid | 1 300 | Ack | 1230 301 | non-IPAWS-alert | 1 304 | invalid-value-in-element-expires | 1 309 | message-references-expired-alert | 133 401 | message-not-disseminated-as-NWEM | 1230 501 | message-not-disseminated-as-EAS | 1230 600 | Ack | 2 601 | message-not-disseminated-as-CMAS | 1228 606 | invalid-value-in-element-eventcode | 112 608 | marine-zone-SAME-geocode-not-disseminated-CMAS | 63 610 | lacks-parameters-to-generate-CMAM-text | 112 615 | signer-not-authorized-for-event-code-CMAS | 112 619 | signer-not-authorized-for-geocode_CMAS | 63 800 | Ack | 1230 802 | public-blockchannel-disregarded | 1230 (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:05.65649