Subject: Product Outage/Anomaly: Update #3 - SNPP Data Outage/Delay This is a multi-part message in MIME format. --Boundary_(ID_uBE0nvRo2VKTttqNDVq08A) Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: 7BIT *Update #3: *On October 13th, the NOAA IDPS ingest system experienced an issue receiving data from the Data Handling Nodes. As a result, SNPP data was delayed in being sent to, and processed by, the NDE system. For Oct 13th, NDE received and distributed 119780 jobs with 3253 failed due to timeliness issues. These are considered lost. IDPS reports that they still have a backlog of data to be processed, and investigation of the issue continues. * Update #2: *Engineering continues the data recovery process from last night. Various products have been recovered, however there are products still being recovered from 10/13/2016 0550Z - 2102Z. Recovery operations will resume on 10/14/2016 at approximately 1400Z. *Update #1: *IDPS has received all ATMS data. The remaining VCIDS reshipment has been delayed. IDPS is experiencing memory issues. IDPS engineering has been contacted and is coming in. *Topic:* SNPP Data Outage/Delay for all products *** Date/Time Issued:* October 14, 2016 2335Z *Product(s) or Data Impacted:***All SNPP products. * **Date/Time of Initial Impact:*October 13, 2016 0419Z *Date/Time of Expected End:* TBD * **Length of Outage:* TBD *Details/Specifics of Change:*Data is on the ground from the spacecraft but stopped being forwarded to NESDIS IDPS. Issue is currently being investigated. Some data will not be transferred to users because it does not meet their timeliness requirements. * Contact Information for Further Information:* ESPC Operations at ESPCOperations@noaa.gov and 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.gov or (301) 817-3880 . Please note: it may take up to two business days to process your unsubscribe request. --Boundary_(ID_uBE0nvRo2VKTttqNDVq08A) Content-type: text/html; charset=utf-8 Content-transfer-encoding: 8BIT
Update #3:  On October 13th, the NOAA IDPS ingest system experienced an issue receiving data from the Data Handling Nodes.  As a result, SNPP data was delayed in being sent to, and processed by, the NDE system. For Oct 13th, NDE received and distributed 119780 jobs with 3253 failed due to timeliness issues.  These are considered lost. IDPS reports that they still have a backlog of data to be processed, and investigation of the issue continues.

Update #2:
Engineering continues the data recovery process from last night. Various products have been recovered, however there are products still being recovered from 10/13/2016 0550Z - 2102Z.  Recovery operations will resume on 10/14/2016 at approximately 1400Z.

Update #1: IDPS has received all ATMS data. The remaining VCIDS reshipment has been delayed. IDPS is experiencing memory issues. IDPS engineering has been contacted and is coming in.

Topic:  SNPP Data Outage/Delay for all products
 
Date/Time Issued:
October 14, 2016 2335Z  

Product(s) or Data Impacted:
All SNPP products.

Date/Time of Initial Impact:
October 13, 2016 0419Z 

Date/Time of Expected End: TBD

Length of Outage: TBD

Details/Specifics of Change:
Data is on the ground from the spacecraft but stopped being forwarded to NESDIS IDPS. Issue is currently being investigated.

Some data will not be transferred to users because it does not meet their timeliness requirements.

Contact Information for Further Information:
 ESPC Operations at ESPCOperations@noaa.gov and 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.gov or (301) 817-3880. Please note: it may take up to two business days to process your unsubscribe request. 


--Boundary_(ID_uBE0nvRo2VKTttqNDVq08A)--