| OutageID |
SiteID |
Failure Type |
Start Date |
End Date |
Description |
Resolution Description |
| 815 |
std |
Power Failure |
2022-05-19 19:00:00 |
2022-05-13 15:15:00 |
Possible site power outage; UPS battery capacity at 0% |
Power restored; UPS output enabled remotely |
| 810 |
std |
Communication - Other |
2022-04-04 12:00:00 |
2022-04-27 23:15:00 |
Possible satellite hardware communications failure |
Satellite-communication hardware upgraded |
| 730 |
std |
Hardware - PC |
2020-07-09 15:00:00 |
2021-11-18 18:00:00 |
Radar hardware issues; data acquisition has been disabled until the hardware issues are resolved |
PC and radar interface cards replaced |
| 726 |
std |
Power Failure |
2020-06-26 00:00:00 |
2020-07-02 18:00:00 |
Power outage due to site maintenance |
Power restored |
| 707 |
std |
Hardware - Instrument |
2020-03-15 00:00:00 |
2020-04-02 23:32:00 |
Tipping bucket precipitation gauge malfunction; precipitation not being detected |
Heater wires were interfering with tipping mechanism |
| 671 |
std |
Power Failure |
2019-11-25 01:34:00 |
2019-12-05 17:00:00 |
Can't connect to router |
Power restored; UPS batteries are failing |
| 642 |
std |
Communication - Satellite |
2019-07-30 14:58:00 |
2019-08-08 15:00:00 |
Can't connect to satellite modem. |
Site lost power on 2019-07-30 14:58:00 UTC and UPS turned off after battery voltage dropped too low. UPS did not turn back on after batteries were recharged. Remote UPS login was successful on 2019-8-8 15:00:00 UTC, and UPS was manually turned on. |
| 501 |
std |
Communication - Satellite |
2016-08-06 00:00:00 |
2016-08-10 00:00:00 |
Satellite modem unresponsive. Could be a power failure, modem issue, phone line issue, or comms computer issue. |
Modem came back after reboot. |
| 485 |
std |
Communication - Satellite |
2016-04-06 05:00:00 |
2016-04-08 00:00:00 |
Unable to reach radar PC. |
System needed to be rebooted. |
| 456 |
std |
Communication - Satellite |
2015-06-15 12:00:00 |
2015-06-22 23:00:00 |
Modem unresponsive. Could be a power failure, modem issue, phone line issue, or comms computer issue. |
Shasta connection restored. |
| 447 |
std |
Communication - Satellite |
2015-04-16 01:00:00 |
2015-04-28 00:00:00 |
Unable to reach router/PC |
PC was in hung state. Rebooted machine. |
| 445 |
std |
Communication - Satellite |
2015-02-19 02:00:00 |
2015-03-06 22:00:00 |
Unable to reach satellite router. Could be power, satellite and/or PC issue. |
Computer was off. Had to power back on. |
| 411 |
std |
Hardware - Instrument |
2014-10-24 00:00:00 |
2014-11-24 00:00:00 |
Parisvel shut down since comms are intermittent. Need to replace all connection cable and/or parivel unit on next site visit. |
Parsivel will be left running as is for season. |
| 405 |
std |
Communication - Satellite |
2014-10-04 00:00:00 |
2014-10-07 00:00:00 |
Satellite router unresponsive. Could be a power failure, router issue or comms computer issue. |
Satellite system was in a unresponsive state. Power cycle returned normal healthy state. |
| 390 |
std |
Hardware - Instrument |
2014-06-11 00:00:00 |
2014-10-06 00:00:00 |
Parsivel unresponsive. Tried cycling power and it did not reset. Update 7/7/14 Unable to connect to datalogger. Tried rebooting machine. |
Swapped Parsivel. |
| 271 |
std |
Communication - Satellite |
2012-11-09 12:00:00 |
2012-11-28 17:00:00 |
Satellite router unresponsive. Could be a power failure, router issue or comms computer issue. Update 11/19/12. Contact could not talk to Hughes modem locally. Problem with sat system. |
System power cycled. |
| 199 |
std |
Communication - Satellite |
2012-03-13 03:00:00 |
2012-03-13 03:00:00 |
Satellite router unresponsive. Could be a power failure, router issue or comms computer issue. Most likely weather related issue given current storm conditions (3/13/12 - 14z) |
Communications returned. |
| 115 |
std |
Communication - Phone |
2011-07-07 15:00:00 |
2011-07-09 00:00:00 |
Modem unresponsive. Could be a power failure, modem issue, phone line issue, or comms computer issue. |
Computer rebooted. |
| 86 |
std |
Communication - Phone |
2011-04-23 17:00:00 |
2011-04-26 16:00:00 |
Modem unresponsive. Could be a power failure, modem, phone line, or PC issue. |
Contact at Shasta power cycled the PC. Hung modem was the issue due to noisy phone line. |
| 78 |
std |
Communication - Phone |
2011-03-25 23:00:00 |
2011-03-25 16:00:00 |
Modem unresponsive. Could be a power failure, modem, phone line, or PC issue. |
Modem connection restored. Was a hung modem on field machine. |
| 56 |
std |
Hardware - PC |
2011-03-12 18:00:00 |
2011-03-17 18:00:00 |
Hardware PC error. Failure writing to USB device causing POP not to run correctly. Site visit planned for 3/17/11. |
Problem fixed on site by staff. |
| 37 |
std |
Communication - Phone |
2011-02-17 02:00:00 |
2011-02-25 23:00:00 |
Reported phone line problems in the area. Phone repair scheduled for Friday, 2/18/11. Crossed phone line after repair on Sat, 2/19/11. Repair rescheduled for 2/23/11. Phone line still crossed at phone pool (behind d-mark). Will require yet another visit to fix. Scheduled for 2/25/11. |
Problems due to crossed wire and hung modem on PC. Crossed phone was fixed and PC was shut down and powered back on. |
