SAFENET

SAFENET Notification

  • Monthly System Maintenance that was scheduled this past Saturday did not occur. It has been rescheduled for Saturday September 20. It will begin at 7am (MDT) and last approximately four hours. During this time frame, there will be a disruption in service and applications will be unavailable. If you are not able to access the application after the completion of the maintenance, please direct your issues to the following email: BLM_HQ_590@blm.gov

SAFENET

Wildland Fire Safety & Health Reporting Network

SAFENET Event Information
Create Agency Response

SAFENET ID:
20250910-0004        [Corrective Actions]
Event Start Date:
09/07/2025 0800
Event Stop Date:
09/07/2025 1930 
Incident Name:
DRC Phone Outage 9/7
Fire Number:
 
State:
Colorado
Jurisdiction:
USFS
Local Unit:
Durango Dispatch - San Juan Headquarters
Incident Type:
Wildland
Incident Activity:
Support
Stage of Incident:
Extended Attack
Position Title:
Assistant Center Manager 
Task:
Dispatch 
Management Level:
3
Resources Involved:
 
Contributing Factors
Contributing Factors:
Communications
Human Factors:
 
Other Factors:
 
Narrative
Describe in detail what happened including the concern or potential issue, the environment (weather, terrain, fire behavior, etc), and the resulting health issue.
We were notified that a famAUTH update would be occurring causing an outage from 0800-1200 on 9/7. In Initial Attack, we followed the direction to log in before 0800 and were mostly able to stay logged in throughout the day. We did run into some issues as internet became unstable as we did not want to refresh the wildCAD page as that would kick us out.

At 0900 all phones went down in Initial Attack and Expanded Dispatch. This outage lasted an hour. Phones being down is a safety hazard as resources cannot always contact us by radio.

The famAUTH outage ended up lasting the entire day, into the evening. Our night Dispatcher was unable to log into wildCAD-e upon initially arriving for his shift.

We had multiple active fires going on during this time including the Type 3 Stoner Mesa Fire CO-SJF-000763.
Immediate Action Taken
Reporting Individual : please describe actions you took to correct or mitigate the unsafe/unhealthful event.
All Initial Attack Dispatchers logged into WildCAD-E before the scheduled FamAUTH outage in the morning. We were careful all day to not refresh those pages even when running into internet issues.

Our Expanded Dispatchers logged into IROC, but it has a shorter period for staying logged in. They had to go through the workaround process. We feel that process should have been disseminated the day before the outage so folks could be prepared and trouble shoot ahead of time.

When the hour-long phone outage occurred we put out a radio announcement with an employee's government cell phone number to call while DRC phones were down. We put out an email to the RMA Dispatch Centers and our large FMO/DO group. We called each of USFS, BLM, BIA, & NPS Duty Officers individually using the government cell phones as well as notifying RMACC, the State, Aviation resources, and county dispatch centers. We normally send out an informational text through wildCAD, but were unable to do so due to the issues with famAUTH. We were also unable to access our wildCAD phone directory during that time, but luckily have such phone numbers in multiple places.

Ultimately, now that all of our Fire Dispatch tracking, ordering, and planning applications are tied together through famAUTH, planning such large updates in the middle of the day in the middle of fire season is a safety risk.


Agency Response

20250910-0004-CA001

Return to Top