Subject: Product Outage/Anomaly: Update #7: DMSP SSMI/S Data Delay This is a multi-part message in MIME format. --Boundary_(ID_vT85HnUM9xRkhL+nY7xnsw) Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7BIT *Update #7: *ESPC has received all backlogged DMSP data, except for the followingfiles were lost*: *F-15 Rev. 93602, and F-15 Rev. 93609 thru 93611. F-16 Rev. 73572, F-16 Rev. 73581 and F-16 Rev. 73589. F-17 Rev. 57851, F-17 Rev. 57857, F-17 Rev. 57859and F-17 Rev. 57864. F-18 Rev. 42585, F-18 Rev. 42588, F-18 Rev. 42589and F-18 Rev. 42609. *Update #6: *FNMOC/Monterey has returned to normal operations. The backlogged data is now being received. * Update #5: * ESPC is still not receiving DMSP data from FNMOC/Monterey * Update #4: *FNMOC/Monterey continues to report a connection outage with no estimated time of return of service. ** * Update #3: *FNMOC/Monterey still reports a connection issue and no estimated time of return of service. * Update #2: *ESPC is still not receiving DMSP data from FNMOC/Monterey due to a disconnection *** Update #1: *ESPC is still not receiving DMSP data from FNMOC/Monterey * Topic:*All DMSP SSMI/S from FNMOC/Monterey. *Date/Time**Issued:*January 22, 2018 0830Z* * *Product(s) or Data Impacted:* EDR, TDR, SDR, and TDUP Data *Date/Time of Initial Impact:*January 20, 2018 0923Z *Date/Time of Expected End:***January 22, 2018 0053Z *Length of Outage:*38.5 hours *Details/Specifics of Change:*ESPC stopped receiving DMSP/SSMI/S data from FNMOC/Monterey. Monterey is currently investigating the issue. *Contact Information for Further Information:* ESPC Operations at ESPCOperations@noaa.gov at 301-817-3880** *Web Site(s) for applicable information:*N/A This message was sent by ESPC.Notification@noaa.gov . You have been sent this and other notifications because you have opted in to receive it.If for any reason, you wish to unsubscribe, please contact ESPC Help Desk at ESPCOperations@noaa.govor (301) 817-3880 . Please note: it maytake up to two business days to process your unsubscribe request. --Boundary_(ID_vT85HnUM9xRkhL+nY7xnsw) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: 8BIT Update #7: ESPC has received all backlogged DMSP data, except for the were lost:
F-15 Rev. 93602, and F-15 Rev. 93609 thru 93611.
F-16 Rev. 73572, F-16 Rev. 73581 and F-16 Rev. 73589.
F-17 Rev. 57851, F-17 Rev. 57857, F-17 Rev. 57859 and F-17 Rev. 57864.
F-18 Rev. 42585, F-18 Rev. 42588, F-18 Rev. 42589 and F-18 Rev. 42609.

Update #6: FNMOC/Monterey has returned to normal operations. The backlogged data is now being received.

Update #5: ESPC is still not receiving DMSP data from FNMOC/Monterey

Update #4: FNMOC/Monterey continues to report a connection outage with no estimated time of return of service.

Update #3: FNMOC/Monterey still reports a connection issue and no estimated time of return of service.

Update #2: ESPC is still not receiving DMSP data from FNMOC/Monterey due to a disconnection

Update #1: ESPC is still not receiving DMSP data from FNMOC/Monterey

Topic: All DMSP SSMI/S from FNMOC/Monterey.

Date/Time Issued: January 22, 2018 0830Z

Product(s) or Data Impacted: TDR, SDR, and TDUP Data

Date/Time of Initial Impact: January 20, 2018 0923Z

Date/Time of Expected End: January 22, 2018 0053Z

Length of Outage: 38.5 hours
Details/Specifics of Change: ESPC stopped receiving DMSP/SSMI/S data from FNMOC/Monterey. the issue.
Contact Information for Further Information: Operations at ESPCOperations@noaa.gov at 301-817-3880
Web Site(s) for applicable information: N/A

This message was sent by target="_blank">ESPC.Notification@noaa.gov. You have been sent this and other notifications because you have opted in to receive it. If for any reason, you wish to unsubscribe, please contact ESPC Help Desk at class="moz-txt-link-abbreviated" href="mailto:ESPCOperations@noaa.gov">ESPCOperations@noaa.govor href="tel:%28301%29%20817-3880" value="+13018173880" target="_blank">(301) 817-3880. Please note: it may take up to two business days to process your unsubscribe request.
--Boundary_(ID_vT85HnUM9xRkhL+nY7xnsw)--