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