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