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