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