SchoolData.net incident

Database server issues

Minor Resolved View vendor source →

SchoolData.net experienced a minor incident on April 27, 2017, lasting 11d 1h. The incident has been resolved; the full update timeline is below.

Started
Apr 27, 2017, 08:11 PM UTC
Resolved
May 08, 2017, 10:00 PM UTC
Duration
11d 1h
Detected by Pingoru
Apr 27, 2017, 08:11 PM UTC

Update timeline

  1. investigating Apr 27, 2017, 08:11 PM UTC

    One of our database servers is currently having issues. We are investigating, and have narrowed the issue to background processing ( i.e. Student Data Grid downloads, Risk Indicator updates). These processes have been turned off to allow the application to be accessed and utilized by the majority of users, including those investigating the issue. This does not affect all districts. If you believe your district is being affected and would like to be personally contacted with updates, please email [email protected].

  2. investigating Apr 27, 2017, 11:53 PM UTC

    SchoolData applications will be put into maintenance mode at 5 pm on today 4/27 and will be available again by 8 am on 4/28 while we continue to investigate the server issue. We are sorry for the inconvenience.

  3. investigating Apr 28, 2017, 04:23 PM UTC

    Our applications are now accessible. We continue to have issues with our background processes for some districts though. We are working on a solution to restore service as soon as possible. If you believe your district is affected and would like personal updates or if you have questions, please email [email protected]

  4. investigating Apr 28, 2017, 08:03 PM UTC

    We continue to have issues with one of our database servers which requires us to reboot it. We understand the outages are aggravating, especially for users trying to finish Evaluations and those trying to get data to their end users. We are continuing to investigate and hope to have a permanent resolution soon. We will continue to update this site with new information. Again, this does not affect all districts. If you believe your district is being affected and would like to be personally contacted with updates, please email [email protected]

  5. identified May 01, 2017, 04:28 PM UTC

    We have identified the issue that has been causing database server issues over the past few days to be risk indicator generation. Risk indicators have been disabled for some districts while we work on a resolution. Other functionality and applications are operational. There may be intermittent outages as we apply fixes to risk indicators.

  6. investigating May 03, 2017, 09:38 PM UTC

    We are experiencing issues with one of our database server at this moment which is requiring a reboot. This issue is related to the issue that began last week. We are continuing to work on a resolution.

  7. investigating May 03, 2017, 10:40 PM UTC

    All servers are up at this time. We are monitoring server status and health.

  8. monitoring May 04, 2017, 10:29 PM UTC

    We have deployed fixes to our database servers to address the issues. Risk Indicators are operational again for all districts. We have implemented limits on background database processes and will increase the limits while we monitor server performance and health. These limits will largely go unnoticed by users but may cause a delay with Data Grids and/or Risk Indicators.

  9. resolved May 08, 2017, 10:00 PM UTC

    The fixes we deployed late last week are stable and all applications and processes are operational. Should you need any help or have any questions, please email us at [email protected]