Park-system phone service disrupted
The Minneapolis Park and Recreation Board said its technology systems were attacked early Nov. 20, 2024. Its Nov. 22 announcement described a systemwide phone outage and an investigation into possible data access.
The board reported no indication that program-registration systems were affected. Residents could use email for administrative matters and were told to call 911 when a police response was needed. The notice does not establish an outage of 911 or emergency dispatch.
Temporary lines and phone restoration
On Dec. 2, the board announced temporary numbers for Customer Service, Park Police and Forestry.
By its Dec. 31 update, all regular numbers had been restored, including recreation-center lines. That is a documented phone-recovery milestone, rather than proof that every consequence of the attack ended that day.
Later administrative effects
A Feb. 5, 2025, board memo attributed delays in testing, configuration and training for a new asset-management system to the cyberattack and an ArcGIS disconnection. Staff sought continued support for the existing system while the replacement was implemented.
The memo’s projected completion date was a forecast. The proposed support extension and the full contract value do not establish the total cost of the cyberattack.
Ransomware and attribution
A later official budget document describes the November 2024 incident as ransomware and discusses lessons for disaster-recovery policies.
The Record reported Nov. 26, 2024 that RansomHub claimed responsibility. That claim does not independently confirm the attacker or the amount and contents of any stolen data. The reviewed board notices do not establish a ransom payment, a final affected-person count or an exact end to all effects.
Later breach investigation
A June 17, 2026, board memo calls the event a data breach and says analysis remained ongoing. It records the use of emergency authority in December 2024 to obtain MNIT/CrowdStrike security support. It does not identify affected personal-data categories or an affected-person count. Continued investigation and security procurement do not establish a continuing outage.
Current assessment
The incident is presumed resolved. The last directly documented operational effects were the project delays described Feb. 5, 2025; the reviewed sources do not establish an exact date when all effects ended. Phone restoration and later forensic work are separate milestones.
