Subscribe to this blog to be notified of changes in systems status.

Intermittent DonorCentral Accessibility Issues

Thursday, June 8, 7:20 a.m. CT: Our mock deployment was successful. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime.
  • Sunday, June 11 (the day after the scheduled June maintenance window) from 7 a.m. - 11 p.m. CT
Wednesday, June 7, 7:36 a.m. CT: Our mock deployment was successful. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime.
  • Sunday, June 11 (the day after the scheduled June maintenance window) from 7 a.m. - 11 p.m. CT
Tuesday, June 6, 8:01 a.m. CT: Our mock deployment was successful. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime.
  • Sunday, June 11 (the day after the scheduled June maintenance window) from 7 a.m. - 11 p.m. CT
Monday, June 5, 7:37 a.m. CT: Our mock deployment was successful. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window) from 7 a.m. - 11 p.m. CT
Thursday, June 1, 8:47 a.m. CT: We plan to continue our test (mock) deployment, today, to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window) from 7 a.m. - 11 p.m. CT
Wednesday, May 31, 7:38 a.m. CT: We plan to continue our test (mock) deployment, today, to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window) from 7 a.m. - 11 p.m. CT
Tuesday, May 30, 9:00 a.m. CT: We plan to continue our test (mock) deployment, today, to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window) from 7 a.m. - 11 p.m. CT
Thursday, May 25, 8:08 a.m. CT: We plan to continue our test (mock) deployment, next week, to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window) from 7 a.m. - 11 p.m. CT
Wednesday, May 24, 8:32 a.m. CT: We plan to run through a test (mock) deployment, this week, to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window) from 7 a.m. - 11 p.m. CT
Tuesday, May 23, 8:38 a.m. CT: We plan to run through a test (mock) deployment, this week, to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window) from 7 a.m. - 11 p.m. CT
Monday, May 22, 8:44 a.m. CT: We plan to run through a test (mock) deployment, this week, to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window)
Friday, May 19, 10:25 a.m. CT: We plan to run through a test (mock) deployment, next week, to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window)
Thursday, May 18, 12:05 p.m. CT: We plan to run through a test (mock) deployment, next week, to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window)
Wednesday, May 17, 11:25 a.m. CT: We plan to run through a test (mock) deployment, next week, to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window)
Tuesday, May 16, 8:11 a.m. CT: We are setting up to run through a test (mock) deployment to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window)
Monday, May 15, 8:03 a.m. CT: We are setting up to run through a test (mock) deployment to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window)
Friday, May 12, 5:43 a.m. CT: We are setting up to run through a test (mock) deployment to ensure our plan includes all details. We are currently targeting the following date for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11 (the day after the scheduled June maintenance window)
Thursday, May 11, 8:06 a.m. CT: We are continuing to finalize deployment plans, including a target deployment date. We apologize for the delays in deploying the upgraded database. We wanted to ensure we covered all edge cases with regression testing and also accounted for edge cases in our deployment plan. We will now go through a test (mock) deployment to ensure our plan includes all details. We are currently targeting the following dates for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11
  • Saturday, June 17
Wednesday, May 10, 7:09 a.m. CT: We are continuing to finalize deployment plans, including a target deployment date. We apologize for the delays in deploying the upgraded database. We wanted to ensure we covered all edge cases with regression testing and also accounted for edge cases in our deployment plan. We will now go through a test (mock) deployment to ensure our plan includes all details. We are currently targeting the following dates for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Sunday, June 11
  • Saturday, June 17
Tuesday, May 9, 7:06 a.m. CT: We are continuing to finalize deployment plans, including a target deployment date. We apologize for the delays in deploying the upgraded database. We wanted to ensure we covered all edge cases with regression testing and also accounted for edge cases in our deployment plan. We will now go through a test (mock) deployment to ensure our plan includes all details. We are currently targeting the following dates for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Saturday, June 3
  • Saturday June 10
  • Saturday, June 17
Monday, May 8, 8:07 a.m. CT: We are continuing to finalize deployment plans, including a target deployment date. We apologize for the delays in deploying the upgraded database. We wanted to ensure we covered all edge cases with regression testing and also accounted for edge cases in our deployment plan. We will now go through a test (mock) deployment to ensure our plan includes all details. We are currently targeting the following dates for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Saturday, June 3
  • Saturday June 10
  • Saturday, June 17
Friday, May 5, 2:43 p.m. CT: We are continuing to finalize deployment plans, including a target deployment date. We apologize for the delays in deploying the upgraded database. We wanted to ensure we covered all edge cases with regression testing and also accounted for edge cases in our deployment plan. We will now go through a test (mock) deployment to ensure our plan includes all details. We are currently targeting the following dates for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Saturday, June 3
  • Saturday June 10
  • Saturday, June 17
Friday, May 5, 7:25 a.m. CT: We are continuing to finalize deployment plans, including a target deployment date. We apologize for the delays in deploying the upgraded database. We wanted to ensure we covered all edge cases with regression testing and also accounted for edge cases in our deployment plan. We will now go through a test (mock) deployment to ensure our plan includes all details. We are currently targeting the following dates for deployment (note the dates could change based on results from our test deployment in our test environment). The deployment to production will require downtime. We're creating an email that will include the specific details. 
  • Saturday, June 3
  • Saturday June 10
  • Saturday, June 17
Thursday, May 4, 7:41 a.m. CT: We are continuing to finalize deployment plans, including a target deployment date. I'll be able to communicate our target deployment date by EOD tomorrow.

Wednesday, May 3, 6:16 a.m. CT: We are continuing to finalize deployment plans, including a target deployment date. I'll be able to communicate our target deployment date later this week.

Tuesday, May 2, 9:09 a.m. CT: We are continuing to regression test DonorCentral v2 and v4 and have not discovered any issues with the upgraded database version. We are also close to finalizing deployment plans. I'll be able to communicate, our target deployment date, later this week.

Monday, May 1, 7:51 a.m. CT: We are continuing to regression test DonorCentral v2 and v4 and have not discovered any issues with the upgraded database version. We are also close to finalizing deployment plans. I'll be able to communicate, our target deployment date, later this week.

Friday, April 27, 10:17 a.m. CT: We are continuing to test real-time sync with the upgraded database, regression test on both DonorCentral v2 and DonorCentral v4 and finalize our deployment plan. So far our testing has been successful and we have not discovered any issues with the upgraded database. We are NOT deploying on Saturday, April 29 and are still trying to identify the next opportunity to deploy.

Thursday, April 26, 4:02 p.m. CT: We are continuing to test real-time sync with the upgraded database, regression test on both DonorCentral v2 and DonorCentral v4 and finalize our deployment plan. So far our testing has been successful and we have not discovered any issues with the upgraded database. We are NOT deploying on Saturday, April 29 and are still trying to identify the next opportunity to deploy. We want to complete testing on the remaining edge cases and also run through a mock outage so we can test that process. I'll share our target deployment date later this week.

Wednesday, April 26, 4:10 p.m. CT: We are continuing to test real-time sync with the upgraded database, regression test on both DonorCentral v2 and DonorCentral v4 and finalize our deployment plan. So far our testing has been successful and we have not discovered any issues with the upgraded database. We are NOT deploying on Saturday, April 29 and are still trying to identify the next opportunity to deploy. We want to complete testing on the remaining edge cases and also run through a mock outage so we can test that process. I'll share our target deployment date later this week.

Wednesday, April 26, 7:34 a.m. CT: We are continuing to test real-time sync with the upgraded database, regression test on both DonorCentral v2 and DonorCentral v4 and finalize our deployment plan. So far our testing has been successful and we have not discovered any issues with the upgraded database. We are NOT deploying on Saturday, April 29 and are still trying to identify the next opportunity to deploy. We want to complete testing on the remaining edge cases and also run through a mock outage so we can test that process. I'll share our target deployment date later this week.%u200B

Tuesday, April 25, 5:20 p.m. CT: We are NOT deploying on Saturday, April 29 and are still trying to identify the next opportunity to deploy. We want to complete testing on the remaining edge cases and also run through a mock outage so we can test that process. I'll share our target deployment date later this week.

Tuesday, April 25, 7:04 a.m. CT: We are continuing to test real-time sync with the upgraded database, regression test on both DonorCentral v2 and DonorCentral v4 and finalize our deployment plan. So far our testing has been successful and we have not discovered any issues with the upgraded database. We're considering pushing back the deployment date so we can complete regression testing on some additional edge cases. We'll be able to share details, including the target deployment date, this week.

Monday, April 24, 6:51 p.m. CT: We are continuing to test real-time sync with the upgraded database, regression test on both DonorCentral v2 and DonorCentral v4 and finalize our deployment plan. So far our testing has been successful and we have not discovered any issues with the upgraded database. We're considering pushing back the deployment date so we can complete regression testing on some additional edge cases. We'll be able to share details, including the target deployment date, this week.

Monday, April 24, 9:31 a.m. CT: We are continuing to test real-time sync with the upgraded database, regression test on both DonorCentral v2 and DonorCentral v4 and finalize our deployment plan. So far our testing has been successful and we have not discovered any issues with the upgraded database. We're creating an email that will include the specific details.

Friday, April 21, 5:23 p.m. CT: We are continuing to test real-time sync with the upgraded database, regression test on both DonorCentral v2 and DonorCentral v4 and finalize our deployment plan. We're creating an email that will include the specific details.

Friday, April 21, 8:16 a.m. CT: We are continuing to test real-time sync with the upgraded database, regression test on both DonorCentral v2 and DonorCentral v4 and finalize our deployment plan. We're creating an email that will include the specific details.

Thursday, April 20, 5:19 p.m. CT: We are continuing to test real-time sync with the upgraded database, regression test on both DonorCentral v2 and DonorCentral v4 and finalize our deployment plan. We're creating an email that will include the specific details.

Thursday, April 20, 7:49 a.m. CT: The nightly uploads are continuing to process successfully. We are also testing real-time sync with the upgraded database, performing regression testing on both DonorCentral v2 and DonorCentral v4 and finalizing our deployment plan.

Wednesday, April 19, 5:47 p.m. CT: We are continuing to test real-time sync with the upgraded database version and everything is going well. We are also performing regression testing on both DonorCentral v2 and DonorCentral v4, while we finalize our deployment plan.

Wednesday, April 19, 9:05 a.m. CT: We are continuing to test the upgraded database and we are now targeting Saturday, April 29 as the date we will deploy the upgraded database. We want to continue our testing for an extra week to be sure the issue is resolved. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Tuesday, April 18, 8:56 p.m. CT: We are continuing to test the upgraded database and we are now targeting Saturday, April 29 as the date we will deploy the upgraded database. We want to continue our testing for an extra week to be sure the issue is resolved. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Tuesday, April 18, 11:18 a.m. CT: The nightly uploads are continuing to run without issues. We are continuing to test the upgraded database and we are now targeting Saturday, April 29 as the date we will deploy the upgraded database. We want to continue our testing for an extra week to be sure the issue is resolved. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Monday, April 17, 5:48 p.m. CT: We are continuing to test the upgraded database and we are now targeting Saturday, April 29 as the date we will deploy the upgraded database. We want to continue our testing for an extra week to be sure the issue is resolved. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Monday, April 17, 10:57 a.m. CT: We are continuing to test the upgraded database and we are now targeting Saturday, April 29 as the date we will deploy the upgraded database. We want to continue our testing for an extra week to be sure the issue is resolved. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Saturday, April 15, 7:57 a.m. CT: We are continuing to test the upgraded database and we are still targeting Saturday, April 22 as the date we will deploy the upgraded database. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Friday, April 14, 7:21 a.m. CT: We are continuing to test the upgraded database and we are still targeting Saturday, April 22 as the date we will deploy the upgraded database. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Thursday, April 13, 3:44 p.m. CT: We are continuing to test the upgraded database and we are still targeting Saturday, April 22 as the date we will deploy the upgraded database. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Thursday, April 13, 9:41 a.m. CT: The nightly uploads successfully ran last night into this morning. We are continuing to test the upgraded database and we are still targeting Saturday, April 22 as the date we will deploy the upgraded database. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Wednesday, April 12, 4:09 p.m. CT: We are continuing to test the upgraded database and we are still targeting Saturday, April 22 as the date we will deploy the upgraded database. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Wednesday, April 12, 9:48 a.m. CT: The nightly uploads successfully ran last night into this morning. We are continuing to test the upgraded database and we are still targeting Saturday, April 22 as the date we will deploy the upgraded database. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Tuesday, April 11, 2:35 p.m. CT: We are continuing to test the upgraded database and we are still targeting Saturday, April 22 as the date we will deploy the upgraded database. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Tuesday, April 11, 8:54 a.m. CT: The nightly uploads successfully ran last night into this morning. We'll continue to monitor each day to ensure the nightly uploads are continuing to function correctly. We are also continuing to test the upgraded database and we are still targeting Saturday, April 22 as the date we will deploy the upgraded database. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Monday, April 10, 4:17 p.m. CT: We have turned on the nightly uploads, which means we do not need to manually uploading data on Monday, Wednesday and Friday. The first time the nightly upload will run is tonight - the night of April 10/morning of April 11. We are also continuing to test the upgraded database and we are still targeting Saturday, April 22 as the date we will deploy the upgraded database. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.

Monday, April 10, 7:03 a.m. CT: We have successfully completed the process of manually updating all customer data. We are also turning on the nightly uploads later today, which means we do not need to manually uploading data on Monday, Wednesday and Friday. The first time the nightly upload will run is tonight - the night of April 10/morning of April 11.

Friday, April 7, 7:11 p.m. CT: As a reminder we will be manually uploading customer data Monday, April 10 from 5 a.m. - 7 a.m. CT. We are also targeting Monday, April 10 as the date when we turn on the nightly uploads. This means the first time the nightly upload will run is the night of April 10/morning of April 11.

Friday, April 7, 8:23 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Monday, April 10 from 5 a.m. - 7 a.m. CT. We are also targeting Monday, April 10 as the date when we turn on the nightly uploads. This means the first time the nightly upload will run is the night of April 10/morning of April 11.

Thursday, April 6, 4:16 p.m. CT: As a reminder we will be manually uploading customer data Friday, April 7 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete. We are also far enough along with testing the upgraded database that we can communicate some target dates (note that the dates could change):
  • We are targeting Saturday, April 22 as the date we will deploy the upgraded database. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.
  • We are targeting Monday, April 10 as the date when we turn on the nightly uploads. This means the first time the nightly upload will run is the night of April 10/morning of April 11. Note that this date could change.
Thursday, April 6, 9:25 a.m. CT: As a reminder we will be manually uploading customer data Friday, April 7 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete. We are also far enough along with testing the upgraded database that we can communicate some target dates (note that the dates could change):
  • We are targeting Saturday, April 22 as the date we will deploy the upgraded database. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.
  • We are targeting Monday, April 10 as the date when we turn on the nightly uploads. This means the first time the nightly upload will run is the night of April 10/morning of April 11. Note that this date could change.
Wednesday, April 5, 5:09 p.m. CT: As a reminder we will be manually uploading customer data Friday, April 7 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete. We are also far enough along with testing the upgraded database that we can communicate some target dates (note that the dates could change):
  • We are targeting Saturday, April 22 as the date we will deploy the upgraded database. This deployment will require downtime. We're creating an email that will include the specific details. Note that this date could change.
  • We are targeting Monday, April 10 as the date when we turn on the nightly uploads. This means the first time the nightly upload will run is the night of April 10/morning of April 11. Note that this date could change.
Wednesday, April 5, 7:41 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Friday, April 7 from 5 a.m. - 7 a.m. CT.

Tuesday, April 4, 4:29 p.m. CT: As a reminder we will be manually uploading customer data Wednesday, April 5 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Tuesday, April 4, 9:37 a.m. CT: We are continuing to perform initial testing. As a reminder we will be manually uploading customer data Wednesday, April 5 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Monday, April 3, 6:28 p.m. CT: We are continuing to load data to the new database in our test environment and perform initial testing. As a reminder we will be manually uploading customer data Wednesday, April 5 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Monday, April 3, 8:17 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Wednesday, April 5 from 5 a.m. - 7 a.m. CT.

Friday, March 31, 2:15 p.m. CT: We are starting to load data into the new database in our test environment. We also plan to begin testing next week. I'll be able to provide our target deployment date after we test for a couple days. As a reminder we will be manually uploading customer data Monday, April 3 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Friday, March 31, 7:12 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Monday, April 3 from 5 a.m. - 7 a.m. CT.

Thursday, March 30, 7:27 p.m. CT: We have completed the new database setup in our test environment and are now finalizing details to load the data and start testing. As a reminder we will be manually uploading customer data Friday, March 31 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Thursday, March 30, 8:39 a.m. CT: We are continuing the process to optimize the new database cluster. As a reminder we will be manually uploading customer data Friday, March 31 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Wednesday, March 29, 4:05 p.m. CT: As a reminder we will be manually uploading customer data Friday, March 31 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Wednesday, March 29, 7:37 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Friday, March 31 from 5 a.m. - 7 a.m. CT.

Tuesday, March 28, 6:07 p.m. CT: We've completed the setup of the high-availability database cluster. We'll now move forward with optimizing the database cluster. As a reminder we will be manually uploading customer data Wednesday, March 29 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Tuesday, March 28, 10:06 a.m. CT: As a reminder we will be manually uploading customer data Wednesday, March 29 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Monday, March 27, 5:12 p.m. CT: We are continuing the process to setup the new database. Once the database setup is complete we will load a snapshot of the data and start regression testing. We will also attempt to reproduce the issue on the new database. Once we start regression testing we will be able to focus in on a target deployment date.

Monday, March 27, 7:11 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Wednesday, March 29 from 5 a.m. - 7 a.m. CT.

Friday, March 24, 4:02 p.m. CT: As a reminder we will be manually uploading customer data Monday, March 27 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Friday, March 24, 7:38 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Monday, March 27 from 5 a.m. - 7 a.m. CT.

Thursday, March 23, 5:03 p.m. CT: As a reminder we will be manually uploading customer data Friday, March 24 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Thursday, March 23, 8:54 a.m. CT: We have completed the process to setup the new server and the monitoring software to confirm the server is optimized. We are now focused on setting up the high-availability cluster. As a reminder we will be manually uploading customer data Friday, March 24 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Wednesday, March 22, 4:53 p.m. CT: We have successfully reproduced the issue in our test environment and are now performing a review of the logs. We are also continuing to stand-up the new server and database. As a reminder we will be manually uploading customer data Friday, March 24 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Wednesday, March 22, 7:41 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Friday, March 24 from 5 a.m. - 7 a.m. CT.

Tuesday, March 21, 3:33 p.m. CT: As a reminder we will be manually uploading customer data Wednesday, March 22 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Tuesday, March 21, 9:44 a.m. CT: We are continuing to setup the new database in our test environment and have now also setup monitoring app to help inform some next steps. As a reminder we will be manually uploading customer data Wednesday, March 22 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Monday, March 20, 4:51 p.m. CT: We are currently setting up the upgraded database in our test environment and will soon setup real-time sync to attempt to reproduce the issue on this new upgraded database. I'll continue to provide details as we continue to work through this process. We're also close to finalizing our deployment date target and will share that target date soon.

Monday, March 20, 7:08 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Wednesday, March 22 from 5 a.m. - 7 a.m. CT.

Friday, March 17, 11:18 a.m. CT: As a reminder we will be manually uploading customer data Monday, March 20 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Friday, March 17, 7:04 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Monday, March 20 from 5 a.m. - 7 a.m. CT.

Thursday, March 16, 2:36 p.m. CT:  We are close to finalizing our plan to upgrade the current database version and are targeting early next week to finalize the go-forward plan details. As a reminder we will be manually uploading customer data Friday, March 17 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Thursday, March 16, 9:12 a.m. CT: As a reminder we will be manually uploading customer data Friday, March 17 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Wednesday, March 15, 2:35 p.m. CT: We are continuing to finalize our plan to deploy the upgraded database. We are also continuing to test real-time sync and the nightly uploads in our test environment. We want to turn on nightly uploads in production, but we want to be confident doing so won't inadvertantly result in an issue. So we are being cautious and performing the necessary testing before we make any decision around nightly uploads. As a reminder we will be manually uploading customer data Friday, March 17 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Wednesday, March 15, 7:28 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Friday, March 17 from 5 a.m. - 7 a.m. CT.

Tuesday, March 14, 3:40 p.m. CT: As a reminder we will be manually uploading customer data Wednesday, March 15 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Tuesday, March 14, 10:40 a.m. CT: As a reminder we will be manually uploading customer data Wednesday, March 15 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Monday, March 13, 5:28 p.m. CT: We are still finalizing details of upgrading the DonorCentral database. I apologize for the time it's taken to get to this point. I assure you that we're moving quickly, while also making sure to get the details right. As a reminder we will be manually uploading customer data Wednesday, March 15 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Monday, March 13, 7:24 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Wednesday, March 15 from 5 a.m. - 7 a.m. CT.

Friday, March 10, 1:27 p.m. CT: As a reminder we will be manually uploading customer data Monday, March 13 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Friday, March 10, 7:07 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Monday, March 13 from 5 a.m. - 7 a.m. CT.

Thursday, March 9, 3:52 p.m. CT: As a reminder we will be manually uploading customer data Friday, March 10 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete. We are also meeting with our database partner, SAP, on Friday, March 10 to finalize the details of our go-forward plan. We have also been testing in an environment, separate from production, to help inform test cases we plan on using on the upgraded database.

Thursday, March 9, 10:12 a.m. CT: As a reminder we will be manually uploading customer data Friday, March 10 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Wednesday, March 8, 4:06 p.m. CT: As a reminder we will be manually uploading customer data Friday, March 10 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete. We are meeting with our database partner, SAP, on Friday, March 10 to finalize the details of our go-forward plan. We have also been testing in an environment, separate from production, to help inform test cases we plan on using on the upgraded database.

Wednesday, March 8, 7:07 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Friday, March 10 from 5 a.m. - 7 a.m. CT.

Tuesday, March 7, 4:54 p.m. CT: As a reminder we will be manually uploading customer data Wednesday, March 8 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Tuesday, March 7, 11:40 a.m. CT: As a reminder we will be manually uploading customer data Wednesday, March 8 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete. We are also discussing if we should turn on the nightly uploads while keeping real-time sync off until we deploy the permanent fix. I'll have more details in the coming days on next steps with the nightly uploads.

Monday, March 6, 5:48 p.m. CT: As a reminder we will be manually uploading customer data Wednesday, March 8 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete. We are also continuing down the path to upgrade the DonorCentral DB version. We are finalizing details and I should have an update on the target deployment date very soon.

Monday, March 6, 7:17 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Wednesday, March 8 from 5 a.m. - 7 a.m. CT.

Friday, March 3, 3:52 p.m. CT: As a reminder we will be manually uploading customer data Monday, March 6 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Friday, March 3, 8:56 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Monday, March 6 from 5 a.m. - 7 a.m. CT.

Thursday, March 2, 4:51 p.m. CT: As a reminder we will be manually uploading customer data Friday, March 3 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Thursday, March 2, 11:25 a.m. CT: We are continuing to finalize details of the upgrade process and deployment plan with our database partner, SAP. As a reminder we will be manually uploading customer data Friday, March 3 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Wednesday, March 1, 5:35 p.m. CT: As a reminder we will be manually uploading customer data Friday, March 3 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Wednesday, March 1, 8:15 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Friday, March 3 from 5 a.m. - 7 a.m. CT.

Tuesday, February 28, 5:57 p.m. CT: As a reminder we will be manually uploading customer data Wednesday, March 1 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Tuesday, February 28, 10:52 a.m. CT: We are meeting with our database partner, SAP, to finalize the details for the upgrade process and deployment plan. I'll continute to share details, including the target deployment date, as they are available. As a reminder we will be manually uploading customer data Wednesday, March 1 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Monday, February 27, 5:24 p.m. CT: We are continuing to finalize details of our deployment plan, including the target date. We're also continuing to move in the direction of upgrading the DonorCentral database to resolve the issue, which forced us to temporarily turn off real-time sync and nightly uploads. I'll continue to provide updates and will share details of next steps as they are available.

Monday, February 27, 8:30 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Wednesday, March 1 from 5 a.m. - 7 a.m. CT.

Friday, February 24, 4:16 p.m. CT: As a reminder we will be manually uploading customer data Monday, February 27 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete. We are also continuing down the path to upgrade our database version and fix the issue. I'll continue to provide updates on our progress to implement the fix.

Friday, February 24, 7:08 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Monday, February 27 from 5 a.m. - 7 a.m. CT. We are also continuing down the path to upgrade our database version and fix the issue. I'll continue to provide updates on our progress to implement the fix.

Thursday February 23, 3:07 p.m. CT: As a reminder we will be manually uploading customer data Friday, February 24 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Thursday, February 23, 11:31 a.m. CT: We are continuing to run at a couple paralell items as we move towards upgrading the DonorCentral database. We are performing manual testing, in staging, to confirm other issues do not exist and we are also continuing to ready the the components needed to upgrade the DonorCentral database. We are also close to finalizing the target deployment date.

Wednesday, February 22, 4:26 p.m. CT: As a reminder we will be manually uploading customer data Friday, February 24 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete. We are also continuing down the path to upgrade the database version, which will fix the issue. I'll share the target deployment date when the details are finalized.

Wednesday, February 22, 7:18 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Friday, February 24 from 5 a.m. - 7 a.m. CT.

Tuesday, February 21, 3:31 p.m. CT: As a reminder we will be manually uploading customer data tomorrow, February 22 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete. We are also continuing on our path to upgrade the database version. Based on our analysis we're confident this effort will fix the issue. I'll continue to provide details on our progress. I'll also provide a target deployment date when we finalize that detail.

Tuesday, February 21, 7:38 a.m. CT: We have successfully completed the process of manually updating all customer data. We'll continue this process on Wednesday, February 22 from 5 a.m. - 7 a.m. CT. We are also continuing down the path to upgrade our database version and fix the issue. I'll continue to provide updates on our progress to implement the fix.

Monday, February 20, 7:29 p.m. CT: As a reminder we will be manually uploading customer data tomorrow, February 21 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down during this time so we can perform the proper validation. I'll update this post when the upload is complete.

Friday, February 17, 3:35 p.m. CT: We are continuing with our efforts to upgrade the database version and fix the issue. I'll continue to provide updates on our progress. As a reminder we'll update all customer data on Tuesday, February 21 from 5 a.m. - 7 a.m. CT. DonorCentral will be taken down while we update all customer data.

Friday, February 17, 7:28 a.m. CT: We have successfully completed the process to manually update all customer data. We'll continue this process on Tuesday, February 21 from 5 a.m. - 7 a.m. CT. We have also started the process to upgrade our database version and fix the issue. I'll continue to provide updates on our progress to implement the fix.

Thursday, February 16, 4:37 p.m. CT: We are ready to manually update all customer data starting tomorrow (Friday, February 17) from 5 a.m. - 7 a.m. CT. DonorCentral will be down during this manual update process. I'll update this Community blog when the update is complete.

Thursday, February 16, 9:41 a.m. CTEarlier this week, we communicated to you that due to recent product outages, real-time sync and nightly data uploads from FIMS to DonorCentral will remain off until we can identify and fix the root cause of this issue. We have been working with SAP, our database partner, since Monday to analyze and determine a path forward, and are finalizing the details of our resolution plan which includes upgrading the database version. As implementing the resolution will take additional time, we will be manually updating the data in DonorCentral three times per week as follows:
  • Friday, February 17: 5am-7am CT
  • Next week (week of 2/20): Tuesday, Wednesday and Friday from 5am-7am CT
  • Starting week of 2/27: Monday, Wednesday and Friday from 5am-7am CT
We will continue to keep you updated on the progress toward the permanent resolution. Thank you for your patience in this matter. We apologize for any inconvenience this may cause.

Wednesday, February 15, 5:53 p.m. CT: We have completed our analysis and are now finalizing details of our resolution plan. As we make arrangements to implement the resolution plan we are going to start manually updating data in DonorCentral for all customers. Details of our plan to manually update data in DonorCentral are below:
  • We will manually update data three times per week - Monday, Wednesday, Friday
  • The update will occur from 5 - 7 a.m. CT
  • We will need to take down DonorCentral for each update during the two hour window so we can run the proper validation and ensure we didn't inadvertantly introduce another issue
  • I will use this Community blog as the primary communication tool to notify you when the data update is complete
  • We will also send a formal email with these details, tomorrow
Wednesday, February 15, 10:37 a.m. CT: Our database partner, SAP, went through their initial review and helped confirm why the issue occurred. We are still investigating to determine the root cause and a resolution path. We're also putting together a plan to get DonorCentral data updated. I'll continue to provide two updates each business day.

Tuesday, February 14, 4:00 p.m. CT: we are still actively working with our database partner, SAP, to identify a root cause and resolution path. I'll provide the next update tomorrow morning.

Tuesday, February 14, 10:25 a.m. CT: we are actively working with our database partner, SAP, to identify a root cause and resolution path. I'll continue to provide updates two times each business day.

Monday, February 13, 6:47 p.m. CT: we successfully deployed a fix and DonorCentral accessibility is now restored. All data is updated as of 4:05 p.m. CT. Real-time sync and the nightly uploads are temporarily turned off as we continue to investigate the root cause. We will continue to monitor the situation and apologize for any inconvenience this may cause. We are also sending a formal email with additional details.

Monday, February 13, 4:42 p.m. CT: Earlier, we communicated to you that due to a system-wide outage, DonorCentral is currently unavailable. We are still actively investigating the issue, and working to restore service as soon as possible. We will continue keep you updated, and we apologize for any inconvenience this may cause.

Monday, February 13, 2:27 p.m. CT: we are actively working on a fix for the issue. We apologize for any inconvenience this may cause and will provide an update by tomorrow morning.

Monday, February 13, 10:51 a.m. CT: some users might experience intermittent accessibility issues with DonorCentral. We are actively investigating the issue. We apologize for any inconvenience this may cause and will provide an update with next steps.
Posted by Collin Gravalin on Feb 13, 2017 11:55 AM America/New_York

Leave a Comment

Log in to post a comment.