Subnet Management - lhg73 (Application)

[Lorimer]

Proposal 134623

TLDR: I’ve voted to adopt.

Halt subnet lhg73-sax6z-2zank-6oer2-575lz-zgbxx-ptudx-5korm-fy7we-kh4hl-pqe, for recovery and update ssh readonly access

This proposal has already executed, at 2024-12-27, 18:09:58 UTC (minutes after it was submitted hours ago). As can be seen in the screenshot below, the subnet had stalled and was no longer processing blocks for a handful of minutes prior to this proposal to halt the subnet.

Security hotfix ongoing

Thanks @derlerd-dfinity1. I’ll be interested to learn what the issue was, and why this disproportionately affected the lhg73 subnet (again). It’s one of the largest subnets, particulalry in terms of memory usage, but it’s not the largest. I’m not sure what makes the subnet special/susceptible. But I’d like to understand this.

This is the third recent stall, with this last one arriving since the comment above.