Some Nevada state systems remained offline for 28 days following the August ransomware deployment, across more than sixty agencies including motor vehicle services, social services, law enforcement systems and state payroll.
Compare It With The Availability Files
Jaguar Land Rover lost five weeks of production at 25-0902. Saint Paul’s recovery ran for months at 25-1106. United Natural Foods could not invoice at 25-0606.
A commercial outage costs revenue and reaches customers who can, at some cost, go elsewhere. A state payroll outage means public employees are not paid. A social services outage means a benefit application does not progress for a person who applied because they had nothing.
The corpus filed at 25-0819 that municipal and state estates hold the most sensitive records under the thinnest supervision. This file records the availability counterpart: the least substitutable services, with the least resilient funding.
Twenty-Eight Days Is Not A Restore, It Is A Rebuild
Restoring from backup takes hours to days. Four weeks indicates rebuilding systems rather than restoring them — which is the correct decision after a 102-day dwell, per 25-1125, because restoring risks reintroducing the adversary.
That is the eviction-certainty problem this desk filed at 25-0802 for Saint Paul’s network shutdown. Being certain costs weeks, and the cost falls on people who cannot use the service in the meantime.
And None Of It Appears On Any Register
Twenty-eight days of unavailable state services generates no notification, no affected count, and no entry in any breach statistic — the availability gap at 26-0209 and 25-0708.
This file exists because the number was published in an after-action account, per 25-1107. Without that practice, the corpus would record Nevada as an incident with no measured consequence.
Compiled from published reporting of the state’s account, listed below. Which specific services were unavailable for the full 28 days is not established. Corrections: corrections@forensicpost.com.