Hedera’s official status service marked its mainnet upgrade to v0.78.1 completed on 16 October at 17:26 UTC / 18:26 BST. The completion notice turns a scheduled maintenance event into a reported operational outcome.

What the maintenance record confirms

The dated maintenance record shows work starting at 17:00 UTC. At 17:05, the team said the upgraded network was available while verification continued. Completion followed at 17:26. These messages establish the operator’s reported sequence; they do not measure every user’s interruption or transaction experience.

Why the documentation needs a separate date check

The consensus-node documentation retrieved for this report still labels release v0.78’s mainnet update TBA and lists build 0.78.0, while directing readers to the status service for current network versions. NetNapz uses the explicit v0.78.1 incident record for completion timing and does not infer a patch-level feature list from the broader release heading.

Completion is not an all-components guarantee

At the source check, the status dashboard labelled mainnet network uptime operational but individual nodes in partial outage, including IBM’s node 11. The page did not establish that this component condition was caused by the upgrade. NetNapz has not independently measured node health.

NetNapz assessment

Assessment: application operators should distinguish network-wide availability from the condition of a particular node or service. A completed maintenance notice can support resuming operational checks, but it is not a substitute for checking the endpoint an application actually uses.

For HBAR investors, successful software maintenance is infrastructure evidence. It does not quantify new customers, fee revenue or incremental token buying. A version number alone cannot establish an adoption trend or price response.

This consensus-node upgrade also does not establish delivery of the separate Agent Accounts roadmap covered by NetNapz. Product-specific milestones require their own release evidence.

Sources and limits

Official status incident, dashboard and consensus-node documentation checked 16 October 2026 at 23:21 UTC / 17 October at 00:21 BST. Logo source and public-domain notice checked on Wikimedia Commons. Reporting attributes completion to Hedera; NetNapz did not install the software, send a test transaction or audit the implementation.