Insights

When the cloud goes down: why keep crew software on board?

A Microsoft 365 outage that began on 12 November has left mailboxes and collaboration tools unreachable for many users, and as we write it is still not fully resolved. For a yacht, that is the everyday risk of software that lives ashore. EdgeCrew runs on the vessel instead.

13 November 2026  ·  6 min read

Crew software that runs on a server aboard the yacht keeps working when cloud services and shore links fail, because nothing it needs is on the other side of the satellite. Rest hours, watches, rotas, maintenance and stores stay available on the crew's phones over the vessel's own network. That is how we built EdgeCrew, and the Microsoft outage that began on 12 November is a good illustration of why.

What happened on 12 November, and is still happening

At 16:17 UTC on Thursday 12 November (17:17 in Central Europe, 11:17 on the US East Coast), Microsoft opened incident EX1550543: users could not reach their Exchange Online mailboxes. Over the following hours Exchange Online, Outlook, Teams, SharePoint and a range of other Microsoft 365 services were reported as affected. Microsoft paused deployments, moved traffic off the affected infrastructure and restarted servers; recovery came region by region and, by its own account, was not at first sustained. Microsoft said there was no indication of malicious activity. It was a failure of the provider's own infrastructure.

As we write this on Friday 13 November, the incident is still open. Microsoft is rolling out a fix to its Exchange Online servers region by region, and users in many places are still affected, more than a day after it began. You can follow the major cloud services as they recover on our live Cloud Watch page.

None of this is a criticism of Microsoft in particular. Every large cloud platform has outages. The point is structural: when the system you depend on runs in someone else's data centre, its availability is theirs to manage, and there is nothing you can do from your desk, or your bridge, to bring it back.

Why a yacht feels it harder

Ashore, a cloud outage is an inconvenience. Aboard, it compounds with a problem every yacht already has: the link to the shore is itself never guaranteed. Even with Starlink Maritime, VSAT and cellular in a properly designed multi-WAN network, there are ports with congested cellular, anchorages behind terrain, weather, and the occasional hardware fault on a dome or a dish.

A shore-hosted crew platform needs both things to be working at once: the vessel's connection and the provider's servers. The availability you get is roughly the product of the two, and it is always lower than either on its own. When either fails, the crew loses access to the records they need to run the boat.

  • The chief officer cannot check whether tomorrow's watch plan breaches rest rules.
  • The engineer cannot see what maintenance is due or log running hours against the machinery.
  • A crew member cannot record hours of rest, so the records are filled in from memory later.
  • Nobody can look up who joins on Monday, or where the spare impeller is kept.
Yacht crew software walkthrough: hours of rest, rosters, maintenance and crew chat  ·  Watch on YouTube

What on board actually means

EdgeCrew runs on a server installed on the vessel, on the yacht's own network. Crew use it from the EdgeCrew app for iPhone and iPad or from a browser; the app finds the vessel's server on the local network by itself. Every request stays inside the hull: from a phone, over the crew Wi-Fi, to the server in the rack and back. The satellite link is not in that path at all.

So when the shore connection drops, or a cloud provider has a bad day, the crew keep working exactly as before:

  • /HRS Hours of Rest keeps recording hours and checking them against MLC and STCW rest rules, flagging breaches before they happen.
  • /WCH Watches and /ROS Roster keep showing who is on watch and who joins, leaves and travels.
  • /ENG Engineering, /JOB and /INV keep the maintenance plan, open defects and spare parts at hand, including QR and NFC tags on the machinery.
  • /CAL Calendar keeps reminders and crew invitations going.

Faster, and your data stays aboard

Resilience is the headline benefit, but not the only one. A server a few metres away answers in milliseconds rather than after a round trip to a satellite and a data centre on another continent, so the software feels quick on a busy day and does not compete with guest traffic for bandwidth.

It also changes where the data lives. Crew profiles, rest hours and personal details stay on hardware the vessel controls, rather than in a third party's multi-tenant service. For owners and management companies who think carefully about privacy, that is a meaningful difference, and it pairs naturally with a segmented, well-secured onboard network.

The honest trade-offs

Running software on board is not free of responsibility. The server needs clean power, a sensible place in the rack, backups and updates. Those are exactly the things an integrator should handle, and we do: EdgeCrew is installed, backed up and supported as part of the vessel's edge computing and network systems, so the crew get the benefit without inheriting an IT project.

Nor is the cloud the enemy. Email, collaboration with the office and many management tools are rightly shore-based, and a good onboard network keeps them as available as the links allow. The question is simply which systems the vessel must be able to run on its own. For the records that keep the crew rested, the watches covered and the machinery maintained, our answer is: all of them.

A simple test

Ask of every system on board: if the connection to shore went away for a day, would the crew still be able to do this? Where the answer is no, and the task is part of running the vessel safely, the software belongs on board.

If you would like to see EdgeCrew on your vessel, or review which of your systems would survive a day like 12 November, talk to us.

Frequently asked

Does EdgeCrew need an internet connection to work?
No. EdgeCrew runs on a server aboard the vessel and the crew reach it over the yacht's own network, so day-to-day use does not depend on the satellite link or any cloud service.
Can crew use EdgeCrew on their phones?
Yes. There is an EdgeCrew app for iPhone and iPad, which finds the vessel's server on the local network, and EdgeCrew also works in any modern browser. Android is coming.
Where is crew data stored?
On the server installed on the vessel, on hardware the yacht controls, rather than in a shared cloud service. Backups are part of how we install and support it.
Who looks after the onboard server?
We do. EdgeCrew is installed and supported as part of the vessel's edge computing and network systems, including backups and updates. Contact us to discuss a support arrangement.
OceanEdge Systems
Bespoke AV/IT, connectivity and control for superyachts and megayachts — designed, installed and supported worldwide.