iNavi NetRTK outage, 23 to 24 September 2026: what owners saw and what brought it back

What happened

iNavi NetRTK is the mower's network position service. It is the alternative to a physical RTK station. A Mammotion account describes it as ready to use without activation, free for life, and working over Wi-Fi or 4G⁵. In a September thread a Mammotion staff account added that iNavi mode runs over the mower's 4G link, so Wi-Fi coverage across the garden is not needed, only a stable 4G signal, and that it does not use the owner's 4G data, so it keeps working after a data plan has expired⁶.

On the afternoon of 23 September (US Eastern) owners began posting that it had stopped. A LUBA 2X in Florida stopped about 20 feet from the charger with "RTK not ready", and a reboot and a forced app close changed nothing. The same owner's 2024 mower, which uses a physical RTK antenna, was fine¹. In the same thread it was down in Ontario, Minnesota, Colorado, Kansas City, Utah, Ohio, New Jersey, Texas, Oregon and the Mississippi Gulf Coast¹. Others reported the same from eastern Pennsylvania, and a YUKA 1000 owner in New Jersey said it "made the device a brick"⁴.

It was not the same for everyone. An owner in Michigan said theirs worked all day and then went offline that evening¹. A LUBA 3 worked while the same owner's LUBA 2X did not⁴, and in Sweden iNavi was fine¹. An owner in the UK, on a LUBA mini AWD, also had trouble².

How it ended

On the morning of 24 September, iNavi was working again for most. One wrote that it "remained off line until AM today"¹, another that "it's back up this morning. I didn't have to do anything"². It went down again after midnight for one owner, and the mower could not get back to the charger².

What owners tried, and what Mammotion said

• Restarts. Powering the mower down, unplugging the RTK station's power for five minutes and starting everything again reconnected iNavi for one Minnesota owner on the morning of the 24th¹. Most other restarts did nothing while the service was down.
• A factory reset. One owner with a LUBA 2 and a LUBA 2X says that on the 2X "this did get the i-navi working again", but they had to remap the lawn². The owner posted it after others had already reported iNavi recovering, so it is not clear whether the reset or the outage ending did it.
• Switching to a physical RTK station. Several owners who tried this over the internet could not make the app complete the switch while iNavi was down¹⁴. If you keep a station, check that it still works before you need it.
• What support said. One owner was told by Mammotion that it was a known issue and being worked on³. Others said the reply they got was generic, about firmware updates and resets, and wished it had simply said there was an outage¹. The steps a Mammotion support reply listed were: power the device off for an hour and restart it in an open area, switch to a different positioning mode and back to iNavi, and if that fails, back up the map to the cloud, delete it from the device, switch to iNavi and restore it².
• A Mammotion account in the thread. It asked whether iNavi was working normally again, suggested trying a different network connection, and asked for the complete device logs and the device name by private message⁴.

Is it your firmware?

One owner on the older 1.30.29.8 firmware wondered if iNavi had been blocked on their mower because it had not updated². Another owner on the newest firmware had the same trouble the same afternoon², and so did owners in the other threads, so the outage does not look tied to the firmware version.