Please don't read this file with IE, it won't work, use Firefox or Chrome Stats for 08232016 run at 23:56:02Z run on vm-lnx-hce-heap1a.ncep.noaa.gov We sent this many CAP messages (1 per segment): 712 We received this many responses to our CAP messages: 711 We received this many uninteligible responses to our CAP messages: 0 ipaws_return_code | status | count -------------------+------------------------------------------------+------- 10 | Ack | 32 102 | server-error | 11 200 | Ack | 707 202 | alert-signature-is-valid +| 707 | +| | | 214 | Geographic-area-outside-authorized-boundary | 1 221 | invalid-CAPEXCHANGE-message | 4 223 | invalid-value-in-element-geocode | 3 300 | Ack | 567 301 | non-IPAWS-alert | 140 304 | invalid-value-in-element-expires | 93 309 | message-references-expired-alert | 139 401 | message-not-disseminated-as-NWEM | 567 501 | message-not-disseminated-as-EAS | 567 600 | Ack | 18 601 | message-not-disseminated-as-CMAS | 549 606 | invalid-value-in-element-eventcode | 76 608 | marine-zone-SAME-geocode-not-disseminated-CMAS | 14 610 | lacks-parameters-to-generate-CMAM-text | 76 615 | signer-not-authorized-for-event-code-CMAS | 77 619 | signer-not-authorized-for-geocode_CMAS | 14 800 | Ack | 567 (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.44909