Please don't read this file with IE, it won't work, use Firefox or Chrome Stats for 09172016 run at 23:56:01Z run on vm-lnx-hce-heap1a.ncep.noaa.gov We sent this many CAP messages (1 per segment): 988 We received this many responses to our CAP messages: 988 We received this many uninteligible responses to our CAP messages: 6 ipaws_return_code | status | count -------------------+------------------------------------------------+------- 10 | Ack | 37 102 | server-error | 9 104 | invalid-element | 2 200 | Ack | 982 202 | alert-signature-is-valid +| 982 | +| | | 300 | Ack | 857 301 | non-IPAWS-alert | 125 304 | invalid-value-in-element-expires | 96 309 | message-references-expired-alert | 125 401 | message-not-disseminated-as-NWEM | 857 501 | message-not-disseminated-as-EAS | 857 600 | Ack | 17 601 | message-not-disseminated-as-CMAS | 840 606 | invalid-value-in-element-eventcode | 134 608 | marine-zone-SAME-geocode-not-disseminated-CMAS | 16 610 | lacks-parameters-to-generate-CMAM-text | 134 615 | signer-not-authorized-for-event-code-CMAS | 134 619 | signer-not-authorized-for-geocode_CMAS | 16 800 | Ack | 853 801 | message-not-disseminated-as-non-EAS-public | 4 818 | referenced-PUBLIC-not-found | 4 (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:03.567123