Skip to content
senn-techsenn-tech
Back to blog
Infrastructure
Servers, Proxmox and network2026-11-16· By Franz Senn

UniFi Network 11 moves the database, wipes the statistics and has no way back

UniFi Network 11.0.97 has carried the Official label since October 23, 2026 and is being rolled out in stages. The upgrade moves the database to PostgreSQL and clears the statistics history. The release notes name no way back to 10.x. On November 15, 2026 the official register for UniFi OS Server did not list version 11 yet.

UniFi Network 11 is the major version of Ubiquiti’s UniFi Network Application. It moves the application database to PostgreSQL, replaces the statistics engine, switches every site to the zone-based firewall and requires UniFi OS 6.0 or newer. Existing statistics history is deleted during the upgrade. The release notes describe no way back to 10.x, so a console backup belongs before the upgrade.

Logo of Ubiquiti
UniFi comes from Ubiquiti. The version details in this post come from the release pages and the vendor download register, retrieved November 15, 2026. Our estate figures come from our own read-only measurement on the same day. (Quelle: Simple Icons, file ubiquiti.svg (repo CC0, no separate licence or guideline listed for this icon), trademark: Ubiquiti Inc.)

Status of this post

This post rests on two measurements from November 15, 2026: the release pages and the official Ubiquiti download register as retrieved that day, and a read-only probe of our production controller in which we changed nothing. An independent specialist site (qfeeds) supplies the mechanics of the new external lists. Whatever we did not test stands at the end under "What we are not claiming".

Approved, but delivered in waves

The release pages label 11.0.97 Official, published October 23, 2026, with a note that it is delivered in stages. Before it sits 11.0.83 from October 12, labeled Release Candidate. After it sits 11.0.102 from November 13, again a Release Candidate. In between are 11.0.94 from October 21 and 11.0.99 from October 30, the latter with "Improved PostgreSQL migration reliability". After the measurement day 11.0.103 followed on November 17; its notes repeat that the PostgreSQL migration clears the statistics history and moves sites to the zone-based firewall. By the release page, 11.0.97 is the approved build. On the measurement day the newest build, 11.0.102, was a candidate; we did not check the label of 11.0.103. None of these lines says which device runs which version by now.

VersionDate (feed, GMT)Per the notesRequirement
11.0.83Oct 12, 2026same headline changes, upgrade up to 20 minutesUniFi OS 6.0+
11.0.94Oct 21, 2026fix: upgrade could rarely failUniFi OS 6.0+
11.0.97Oct 23, 2026database to PostgreSQL, history cleared, zone firewallUniFi OS 6.0+
11.0.99Oct 30, 2026more reliable PostgreSQL migrationUniFi OS 6.0+
11.0.102Nov 13, 2026fix: upgrade to 11 could rarely failUniFi OS 6.0+
11.0.103Nov 17, 2026firewall destinations in the External zoneUniFi OS 6.0+

Source: release feed of the UniFi Network Application, retrieved November 19, 2026. The middle column is our shortened summary of the vendor text; labels such as Official or Release Candidate appear on the release pages only.

A release delivered in waves cannot be worked off along a date in a calendar, because the day of acceptance sits outside our control. We can prepare the state; Ubiquiti sets the moment.

What the release notes do to an existing installation

Ubiquiti presented Network 11 in its blog on October 12, 2026. By our retrieval of November 19, 2026 the article has no line on PostgreSQL, the statistics history or a way back; those details appear only in the release notes.

Four notes from 11.0.97 concern an existing setup directly. The application database moves to PostgreSQL. Existing statistics history is cleared and starts fresh. Every site switches automatically to the zone-based firewall. And two platforms fall away: USG gateway support is gone, with Network 10.6 named as the last version carrying it, and the plain Network Application Server is gone too, replaced by UniFi OS Server. Anyone running the application on their own Linux box faces a platform change, announced in advance. A home-lab test by Virtualization Howto from October 14, 2026 describes the route: take a .unf backup of the Network 10 configuration and restore it on the new UniFi OS Server with Restore From Backup. The new server had a different IP address there, the devices needed a new inform address, and firewall rules may need an added object. That is a single report from a home lab; we did not rebuild the route. Why a forced change becomes a planning question, we wrote down once on the VMware path: OpenVDDK as a stand-in for the locked VDDK.

From Network 10.6 to Network 11, per the release notesNetwork 10.6.xstate before the upgradeUpgrade to 11.0.97up to 20 minutes per thenotesApplication databaseMongo moved to PostgreSQLStatisticshistory cleared, countersrestartZone-based firewallall sites migratedautomaticallyUSG and self-builtserversupport removed
Every step comes from the notes for 11.0.97. Marked are the three that do not reverse themselves: the upgrade itself, the empty history and the firewall switch. (Quelle: Release notes UniFi Network Application 11.0.97, October 23, 2026)

The notes put the upgrade at up to 20 minutes. On a gateway that carries all traffic, that is a maintenance window.

Is there a way back to 10.x?

The release notes for 11.0.97 describe no way back to 10.x. With Network 10.2 Ubiquiti did advertise "One-click rollback for updates" on March 12, 2026, under the heading "built-in firmware safety nets", but that page lists no devices, and the notes for 11.0.97 attach no promise of it to the database migration. What remains is the backup before the upgrade, plus two field reports in the auto-update section below.

The backup menu depends on version and platform. LazyAdmin names Settings, Management, General. Unihosted writes that the Network Application dropped its backup function with 10.1.84 and points to Settings, Control Plane, Backups. Virtualization Howto downloaded the .unf backup under Settings, System, Backups. We checked none of the three; the menu of your own version decides.

Our controller has not received any of it

Our production controller ran UniFi OS Server 5.1.42 with UniFi Network Application 10.6.109 on November 15, 2026, so it sat before version 11.

Our read-only probe of November 15 shows for the production controller: UniFi OS Server 5.1.42, image uosserver:c9603dec9010, service running since November 13, 2026, and the UniFi Network Application at version 10.6.109 according to our inventory of November 2, 2026. The official download register names the same on the same day: build 5.1.42 from September 10, 2026 and network application 10.6.109 from October 23, 2026. No UniFi OS build with a 6 in front, no network package with 11.

That fits a sentence in the notes for 11.0.94 from October 21, which require UniFi OS 6.0 and add that this level is available neither in GA nor as RC. Upstream has not yet delivered the precondition for our way of running it. We stand on the most recently published self-hosted line.

One limit on that: whether our controller already shows version 11 cannot be read from its logs. The file updater-service.log is 2.3 kilobytes and holds lines of the type "Updater service listening", no offer date. A missing entry there is not proof of a missing offer.

External lists: the download runs through the gateway

New is the option of importing domain or IP lists from an external source instead of maintaining entries by hand. The notes confirm the feature and leave out the details. The list vendor qfeeds documents the mechanics in its knowledge base, current as of November 15: refresh every 24 hours, one list either IPv4 or IPv6, at most 100,000 entries per list and 500,000 per gateway, fetched by the gateway itself. Two traps: if the source answers with HTTP 429, the list stays unchanged. And a source that publishes its list under a URL path instead of the hostname is not supported.

Three consequences for us. The gateway needs outbound HTTPS to the list sources, a rule at the perimeter and not one inside the network. Freshness is set by the refresh interval, not by the quality of the list; a list allowed to be 24 hours old is not a real-time block. And a source throttling with 429 delivers a list that looks fresh and is not. Anyone using such lists against IoT devices starts with network segmentation: One coffee machine, one terabyte and a VLAN. The interval is selectable: a LazyAdmin test names 24, 48 or 72 hours, Borncity says the same and warns that large lists can exceed gateway limits. A YouTube review adds a button for an immediate reload, which we did not confirm.

Live Flows needs a gateway we never adopted

Live Flows requires UniFi OS 6.0.10 or newer and one of the gateways named in the notes.

The notes list the devices carrying Live Flows: UDM-Pro, UDM-SE, UDM-Pro-Max, UDW, EFG, EF-Core, UDM-Beast, UCG-Fiber, UCG-Max, UXG-Max, UXG-Fiber, UXG-Pro and UXG-Enterprise. The UXG variants run only with an enterprise key, Official Hosting or UniFi OS Server. The UXG-Lite is missing from that list, as of November 15.

Our estate holds no UniFi gateway. Measured on the same day: two controller instances, one productive and one in the homelab. The productive one manages 51 devices, all of them access points, no gateway and no switch adopted, plus five sites and zero open alerts. Live Flows, external lists, the forced switch to the zone-based firewall and the end of USG support pass our estate by. Our real share of the upgrade is the database move, the empty statistics and the firewall dialog on first opening the interface.

Auto-update is on, the roster does not know UniFi

On the production controller Auto-Update sits on under Control Plane, Updates, recorded in our inventory of November 2, 2026. UniFi appears in none of our update rosters, neither the weekly fleet run nor the CVE review. The release page for 11.0.102 carries two user reports. One UDM Pro Max, restored from a 10.6.111 backup, crash-looped with "Phase 0 refused: this build cannot migrate from legacy Mongo dataset at 10.6.111" and exit code 1, and migrated cleanly only with 11.0.102. Another user could not downgrade, 11.0.99 was the only offer, and only a second gateway on 10.x saved him.

Those are individual forum reports. They show what a forced schema migration without a downgrade means on a production device: the controller dialog happens whether we are ready or not. Anyone building an update roster for network services finds the frame in patch management for mid-sized firms and in our IT operations service.

PostgreSQL 14 inside the UniFi container

A second finding of the probe: inside the UniFi OS server container runs rootless postgresql@14 in version 14.24, with no listener on the host. PostgreSQL 14 lost support on November 12, 2026 according to the project version table; 14.25 from the same day is the final minor release, so the container sits one minor behind. The fleet census is in PostgreSQL 14 ends today: 25 instances, 21 seen. UniFi Network 11 brings its own PostgreSQL track for the statistics. That is the second reason to run this upgrade deliberately.

What we are not claiming

None of the new features is tested by us in our own operation. We adopted no gateway, imported no list, opened no flow. The reload button comes from one review and stays unconfirmed. The broken client alert is the author’s individual test; our controller shows zero open alerts and we have no view into it. We name no date for when 11.x arrives with us, because updater-service.log does not yield one. The two field reports from the release page stay individual cases.

More from this topic area in the hub Servers, Proxmox and network.

Further Reading

Questions?
Is UniFi Network 11.0.97 actually released?+

Yes, with limited reach. The release page labels 11.0.97 Official, published October 23, 2026, with a note about a gradual rollout. Builds 11.0.83 from October 12 and 11.0.102 from November 13 run as release candidates. Approved and delivered everywhere are two different things.

Can you roll UniFi Network 11 back to 10.x?+

Not according to the release notes for 11.0.97, which describe no way back. On the release page for 11.0.102 one user reports he could not downgrade and was saved only by a second gateway still on 10.x. That is a single report. Keep a console backup taken on 10.x before the upgrade; the backup menu differs by version and platform.

Does UniFi Network 11 run on a self-hosted controller?+

Not on ours yet. The notes for 11.0.97 require UniFi OS 6.0 or newer and drop the Network Application Server in favor of UniFi OS Server. On November 15, 2026 the official download register for UniFi OS Server listed build 5.1.42 from September 10, 2026 as the newest build, and 10.6.109 from October 23, 2026 as the newest network application. Version 11 was not listed there.

Does UniFi Network 11 delete the statistics history?+

Yes, by the wording of the release notes. They name a new statistics engine and state that existing statistics history is cleared and starts fresh. On top of that come the move of the application database to PostgreSQL and the automatic switch of every site to the zone-based firewall. Anyone who needs reports over earlier periods loses them with this step.