We would greatly appreciate it if the DFINITY team could assist in investigating whether there may be an issue with the lhg73 subnet. Thank you very much in advance for your support. @sat Currently, most trading pairs on ICPSwap are experiencing swap failures. Based on our preliminary investigation…

We are in contact with the ICPSwap team helping them debugging their canister. The subnet is not down. Let me give some more context on the subnet metrics you are observing. The increased state size during the stall of the lspz2 subnet yesterday, the increased cycle burn during the same time period…

Some pools from lhg73 are working again on icpswap, but ICP/ckUSDC still appears to be stuck(same subnet)

I tried again, and some swaps are now working normally. I’m a bit curious — could this be related to the following incident? Application Subnet is stalled Incident status: Monitoring A fix has been implemented and we are monitoring the results. Time posted: Feb 28, 18:26 UTC

https://forum.dfinity.org/t/subnet-management-lspz2-application/35322/96 There is an identified issue in the ICOS version. I think we’ll need to stay tuned for more ICOS deployment proposals

a bit weird that some pools from the same subnet are now working again and some do not

Hotfix → [image] fix: More consistent `remaining_canisters` · dfinity/ic@a62fbc6 Use the same source of truth for the iterator and `remaining_canisters`.

Looks like a divide by zero error was introduced due to subnet_schedule.len() differing to state.canister_states().len(), and the division here . I guess this recurs after a restart so the subnet stalls. I’m not clear why this would cause degraded performance on other subnets (rather than just fully…

I think this change was mainly done to make the code more robust and cover some rare edge cases like newly created subnets with no canisters on them, that division has been there for many months and the number_of_canisters value hasn’t been changed, so it’s unlikely to have caused the downtimes. su…

so, what’s up with lhg73? still broken, been hours

I can’t trade either, what’s going on

Could any member of the DFINITY team please help notify the relevant devs? The lhg73 subnet appears to be down — it has been showing 0 Cycles/s for quite some time. [image] https://dashboard.internetcomputer.org/network/subnets/lhg73-sax6z-2zank-6oer2-575lz-zgbxx-ptudx-5korm-fy7we-kh4hl-pqe

Request for DFINITY Team Assistance in Investigating Potential Issues with the lhg73 Subnet

Developers

Arthur2 March 1, 2026, 5:44am 27

Bump @DFINITYTeamMembers @andrewbattat

Topic		Replies	Views
Subnet 'lhg73' MIEPs Suddenly Dropped to 0 - Request for Guidance Developers Functional-Programming	5	159	December 27, 2024
Subnet ‘lhg73’ stalled again within 24 hours. Any insights on this? Developers Functional-Programming	1	71	December 27, 2024
Subnets `mpubz`, `brlsh`, and `pjljw` Incident Retrospective - Friday October 15, 2021 Developers	19	1362	October 20, 2021
Subnet Malfunctioning Developers	19	544	January 16, 2025
Canister return 504, too much traffic on subnet? Developers	29	2119	August 27, 2021

Request for DFINITY Team Assistance in Investigating Potential Issues with the lhg73 Subnet

Related topics