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