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