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