Shop Applications News About Contact Book a meeting Connectivity guide Search GMTS CONNECT ↗ VesselNow ↗ GMount Network Status Login

← Back to news

Firmware day: how to update Peplink and UniFi safely (and when to wait)

Share LinkedIn
Firmware day: how to update Peplink and UniFi safely (and when to wait)
White outdoor wireless access point mounted on a brick wall with cables running into it
Photo: Mbrickn, “Outdoors Wireless Access Point”, CC BY 4.0, via Wikimedia Commons. Resized from the original.

Two notices landed in the same week. Peplink posted Router Firmware 8.6.2 Beta 1 on 19 November. Ubiquiti promoted UniFi Network Application 11.0.103 to an official release.

Neither is a drama. But it’s a good moment to explain how we handle updates on the routers, switches and access points we look after, because “click update and hope” is how a quiet Tuesday becomes a long night.

Stable vs beta: why we keep customers on 8.6.1 for now

Peplink 8.6.1 is the current production firmware, generally available since 30 September 2026. We covered it in detail in Peplink firmware 8.6.1: the fixes, and who should leave 8.5.4, including the security fixes that make it the build we take for supported hardware.

8.6.2 Beta 1 is a beta. Early forum feedback is positive, but betas exist so people can test on non-critical kit and report problems. That’s what we do: one unit on the bench or our own network, not a customer’s vessel or yard.

Our rule is simple:

  • Production sites stay on GA firmware. For Peplink today, that’s 8.6.1.
  • Betas go on test units. We read the release notes, watch the forum, and wait.
  • The exception: a beta that fixes a specific, serious problem a customer actually has. Even then, we test one unit first and keep the previous build ready.

When 8.6.2 goes GA, we’ll read the release notes, check the supported hardware list and plan the rollout. Not before.

UniFi Network 11.0.103: who needs it

Ubiquiti’s release notes for 11.0.103 describe a gradual rollout and fixes for problems some sites hit after upgrading from 10.6, including VPN servers, firewall and port-forwarding rules, and SD-WAN tunnels dropping after the upgrade. Two things to know first:

  • It needs UniFi OS 6.0 or later. If your console isn’t there yet, that’s step one.
  • Upgrading from 10.x clears statistics history. If you rely on those graphs, export what you need first.

If you upgraded to 10.6 and your VPN, firewall or port forwards started misbehaving, 11.0.103 is worth planning. If everything’s stable and you’re not on 10.6, there’s no rush. Let the gradual rollout do its job.

Pre-update checklist

Before we touch any router, switch or access point, we run through this:

Before you update
1. Check the hardware. Is your exact model and hardware revision on the supported list in the release notes? If not, stop.
2. Read the release notes properly. Known issues matter more than new features.
3. Back up the config. Export it and save it somewhere that isn’t the device.
4. Pick a maintenance window. Out of hours for a business. Alongside for a boat. Never mid-passage on the only link.
5. Make sure you can get back in. Know how you’ll reach the device remotely if the update goes wrong, through InControl, a second WAN or someone on site.
6. Tell people. A two-line heads-up saves a lot of “is the internet down?” calls.

For Peplink fleets we push updates from InControl, one site or a small group first, then the rest once we’re happy.

Rollback plan, and what to test afterwards

Every update needs a way back. Keep the previous firmware file and your config backup handy. On Peplink, check the router can boot back to its previous image. On UniFi, know which version you’re on before you start.

After the update, don’t just check the lights are green:

  • Every WAN link is up. Fibre, cellular and Starlink all showing healthy.
  • Failover still works. Unplug the primary and watch it switch.
  • Tunnels and VPNs reconnect. SpeedFusion, site-to-site and remote access.
  • Wi-Fi clients get an address on every network: guest, crew or staff, and operations.
  • Critical apps work. Phones, EFTPOS, cameras, vessel monitoring.
  • Alerts still arrive. Check InControl or UniFi notifications are reaching the right people.

If anything fails and you can’t fix it quickly, roll back. A working network on last month’s firmware beats a broken one on this week’s.

Look after the kit you’ve got

There’s one more reason to keep firmware current: replacing hardware is getting dearer. IoT Portal reports Teltonika raised prices by up to 20% from 1 November 2026, after Peplink adjusted prices on selected models from 1 June, with memory chip costs driving rises across the industry.

Well-maintained routers on supported firmware last longer, stay secure and don’t need replacing in a panic.

When to call us

If you’d rather not think about any of this, that’s fine. It’s our job. We can:

  • Run updates for you in a planned window, with backups and testing done
  • Keep an eye on your Peplink devices in InControl and flag what needs attention
  • Tell you plainly when a release matters for your setup, and when it doesn’t

Talk to the team

Want us to take firmware off your list? Get in touch or book a time. See managed networks, Peplink SD-WAN and onboard networks for boats.

We’re a certified supplier and installer, and we can support you or your preferred installer onboard and ashore.

Sources

← Back to news

Talk to GMTS ← Back to news