Please don't read this file with IE, it won't work, use Firefox or Chrome
Stats for 08102016 run at 23:56:01Z run on vm-lnx-hce-heap1a.ncep.noaa.gov
 
We sent this many CAP messages (1 per segment): 1068 
We received this many responses to our CAP messages: 1067 
We received this many uninteligible responses to our CAP messages: 13 
 
ipaws_return_code | status | count -------------------+------------------------------------------------+------- 200 | Ack | 963 202 | alert-signature-is-valid | 963 221 | invalid-CAPEXCHANGE-message | 90 223 | invalid-value-in-element-geocode | 6 224 | reference-element-invalid | 9 300 | Ack | 949 301 | non-IPAWS-alert | 14 304 | invalid-value-in-element-expires | 14 309 | message-references-expired-alert | 82 401 | message-not-disseminated-as-NWEM | 949 501 | message-not-disseminated-as-EAS | 949 600 | Ack | 26 601 | message-not-disseminated-as-CMAS | 923 606 | invalid-value-in-element-eventcode | 129 608 | marine-zone-SAME-geocode-not-disseminated-CMAS | 4 610 | lacks-parameters-to-generate-CMAM-text | 129 615 | signer-not-authorized-for-event-code-CMAS | 129 619 | signer-not-authorized-for-geocode_CMAS | 4 800 | Ack | 949 802 | public-blockchannel-disregarded | 949 818 | referenced-PUBLIC-not-found | 7
(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:03.621908