Cambium Networks Administration: A Practical Continuity Plan for WiFi and Fixed Wireless Operators

Cambium Networks customers have a new issue to add to network planning: vendor continuity.

On September 14, 2026, Cambium Networks Corporation disclosed that Cambium Networks, Ltd., an indirect wholly owned subsidiary, had entered administration in the United Kingdom. The same SEC filing reported that the company had reduced its global workforce by 260 employees, or 53.6% of its workforce, effective September 11. Administrators have been appointed and are attempting to sell company assets and business lines.

For an organization operating Cambium access points, fixed wireless radios, switches, or cnMaestro, that does not mean the installed network suddenly stops working. It does mean the assumptions behind support, replacement hardware, licensing, cloud management, firmware access, and future expansion need to be reviewed.

The right response is not an immediate rip-and-replace project. It is to determine whether the network can still be operated, recovered, repaired, and eventually migrated without depending on services that may change.

What has changed for Cambium Networks customers?

A September 16 company statement reported by industry publications separated the situation into two broad product categories. Cambium said production of its WiFi access points, NSE devices, and cnMatrix switches has been discontinued. The company also said it anticipates that its fixed wireless broadband operation will largely resume after a relatively short pause.

That distinction is important.

An organization running Cambium enterprise WiFi may now face a hardware-availability and lifecycle-planning issue that is very different from a WISP operating PMP, ePMP, PTP, or other fixed-wireless infrastructure.

Cambium also stated that its intention is for cnMaestro Cloud to continue operating at least through October 1, 2026. That wording matters. October 1 has not been announced as a shutdown date; it is the date through which Cambium said it presently intends to maintain the service.

Operators should therefore use the current availability window to improve their recovery position rather than assuming today's cloud access will always be available.

Start with recoverability, not replacement hardware

Before comparing access points or radios, answer a more basic question:

Could another qualified administrator restore this network if a controller, server, access point, radio, or management service failed tomorrow?

That means preserving more than a spreadsheet containing device names. Configuration backups, firmware images, software installers, controller data, administrative credentials, license information, certificates, network diagrams, serial numbers, VLANs, RADIUS settings, SSID definitions, RF parameters, antenna details, switch configurations, link plans, and relevant support documentation should all exist somewhere independent of the equipment being protected.

Cambium's own cnMaestro guidance recommends regular backup and recovery practices for on-premises deployments, including full-disk protection, secure management access, and operational safeguards. A backup file is useful only if someone can successfully restore it, so recovery should be tested against an isolated clone or non-production environment before an outage forces the issue.

Organizations that do not have the internal resources to establish that process can use managed WiFi services to bring an existing network under monitoring, configuration control, documentation, and a defined response process.

Should you move cnMaestro on premises?

For some Cambium environments, self-hosted cnMaestro deserves immediate evaluation.

Cambium released cnMaestro On-Premises 6.0.0 in July 2026, bringing the self-hosted release closer to the feature level of cnMaestro Cloud 6.0.0 at that time. The on-premises platform allows an organization to operate its own management instance rather than relying exclusively on Cambium's hosted interface.

That can reduce an important cloud dependency, but it should not be interpreted as making every Cambium deployment completely vendor-independent.

CBRS is a good example. Cambium documentation describes an architecture in which CBRS equipment communicates with a Cambium Domain Proxy and a Spectrum Access System. The documented on-premises workflow may still require a cloud anchor account and other external dependencies.

Before migrating, document which features require cloud authentication, licensing, domain-proxy connectivity, firmware repositories, subscriptions, certificates, or third-party integrations. Test the actual management and recovery path rather than assuming that “on premises” means “fully independent.”

Cambium WiFi customers should plan a migration, not rush one

For organizations running Cambium enterprise WiFi, the discontinuation of new AP production changes long-term planning even when every installed access point is functioning normally today.

There is no single “Cambium replacement access point.” The right successor depends on the building, device population, application traffic, density, roaming requirements, wired infrastructure, security requirements, management model, and expected service life.

Ubiquiti, RUCKUS, Arista, and other vendors all offer platforms that may be appropriate in different environments. A product comparison based only on maximum PHY rates or manufacturer client counts is not enough to make that decision.

A replacement AP can have better specifications on paper and still perform poorly if its placement, channel plan, power levels, uplinks, PoE budget, or mounting strategy are wrong.

That is why a migration should normally begin with an Enterprise WiFi Design based on the actual users, applications, building materials, and capacity requirements rather than a one-for-one hardware swap.

For an existing building, a Wireless Site Survey can establish what is working today, locate coverage and capacity problems, and provide the RF data needed to decide where existing AP locations can be reused and where the design should change.

The outcome may be a complete migration, but it may also be a phased refresh. WiFi 6 and WiFi 7 upgrade planning should identify the areas where new hardware delivers a measurable benefit rather than replacing the entire network simply because a newer standard exists.

Point-to-point wireless requires engineering, not a radio swap

Cambium's situation also affects organizations using wireless bridges for building-to-building connectivity, campus backhaul, temporary bandwidth, and remote facilities.

Lower-cost platforms from vendors such as Ubiquiti and MikroTik can be practical for many clear-line-of-sight links. Higher-capacity or mission-critical applications may justify licensed microwave, 60 GHz, E-band, or other carrier-grade systems.

The mistake is treating the replacement decision as a simple comparison of advertised distance and throughput.

A point-to-point link has to be designed around path length, Fresnel-zone clearance, mounting height, spectrum conditions, expected interference, antenna gain, rain attenuation, required availability, and the capacity actually needed by the applications behind the link.

For campuses, parking areas, multi-building properties, and similar environments, Cambium Solutions' Outdoor Wireless Coverage service includes directional wireless and point-to-point backhaul planning alongside outdoor WiFi design.

Where a link must be replaced or cut over with minimal downtime, the physical deployment and testing can then be handled as part of a documented Network Installation rather than as an isolated equipment change.

Point-to-multipoint migrations need a different strategy

Point-to-multipoint fixed wireless is more complicated because the infrastructure and subscriber equipment generally belong to the same radio ecosystem.

Changing the access point at a sector can require changes at tens, hundreds, or thousands of subscriber locations.

That makes “which radio should we buy?” the wrong first question. The first questions are how many subscribers have to move, which frequencies and channel widths are available, what performance each subscriber requires, how truck rolls will be scheduled, and how long the old and new networks need to operate side by side.

For many operators, the lowest-risk approach is a parallel migration: engineer the replacement sector, bring it online beside the existing system, migrate subscribers in controlled groups, validate service, and retire the original equipment only after the replacement network is proven.

That approach turns a vendor transition into a capacity and operations project rather than a single high-risk cutover.

Temporary connectivity can reduce migration risk

Some sites cannot wait for a complete redesign, procurement cycle, cabling project, or carrier installation.

A temporary network can provide a bridge while the permanent architecture is being changed.

Cellular bonding, temporary point-to-point backhaul, staged access points, and other short-term options can keep a facility operating while a permanent replacement is surveyed, designed, and deployed. Cambium Solutions' Temporary and Event WiFi service supports temporary building internet as well as short-duration events, including bandwidth sourcing, staged hardware, segmentation, monitoring, and removal.

For a Cambium migration, that can create room to engineer the permanent network correctly instead of making a rushed hardware decision because connectivity is immediately at risk.

What about FIPS-validated Cambium equipment?

Administration does not automatically invalidate an existing cryptographic validation.

As of publication, NIST lists the Cambium PTP 700 Point to Point Wireless Ethernet Bridge under FIPS 140-3 Certificate #5518. The module is listed as active, is a Level 2 hardware module, and has a September 9, 2031 sunset date.

That is different from saying future hardware availability, repair capability, software distribution, licensing, or manufacturer support is guaranteed.

Organizations that require validated cryptography therefore need to evaluate both technical certification and commercial continuity.

Alternatives exist, but the details matter. NIST lists Ceragon IP-20/IP-50 products under active FIPS 140-3 Certificate #5072 as a Level 2 hardware module, with specific hardware and firmware requirements. NIST also lists Aviat's WTM 4000 under Certificate #5107 as a Level 1 software module, which is not equivalent to a Level 2 hardware validation.

For enterprise WiFi, Arista WiFi Access Points are listed under active FIPS 140-3 Certificate #5515 as a Level 2 hardware module. As with any validated system, procurement must match the specific validated hardware, software, and operating configuration rather than relying on a general statement that a product or vendor is “FIPS compliant.”

There is also a separate FIPS deadline approaching. NIST states that FIPS 140-2 modules may continue to be accepted for new systems through September 21, 2026. After that, those validations move to the Historical list and are intended for existing systems rather than new deployments.

That transition is independent of the Cambium Networks administration.

What should operators do now?

The immediate priority is to establish control over the network you already have.

Document the infrastructure, export what can be exported, secure software and configuration data, test administrator access, identify cloud and licensing dependencies, validate spare equipment, and prove that backups can actually be restored. Then separate the estate into equipment that can reasonably continue in service and equipment that needs a migration plan.

For WiFi, use measured RF and capacity data before selecting replacement access points. For outdoor and point-to-point systems, perform path and spectrum analysis before changing radios. For point-to-multipoint infrastructure, include subscriber equipment and field labor in the migration model rather than evaluating only the sector hardware.

And when a migration is required, design the new network around the environment instead of recreating every decision made in the old one.

Cambium Solutions is structured around that process: survey the existing environment, develop a vendor-neutral design, install and validate the replacement, then provide managed support where ongoing operations are needed. The company works across enterprise WiFi, outdoor wireless, temporary connectivity, and multi-location networks rather than tying the project to a single hardware manufacturer.

The important question for a Cambium Networks customer is no longer simply:

“Is the equipment still online?”

It is:

“Can we still administer, recover, repair, expand, and eventually replace this network if a vendor service or supply channel we rely on today is unavailable later?”

If that answer has not been documented and tested, now is the time to do it.

Cambium Solutions can assess an existing Cambium deployment, document its dependencies, complete an RF or wireless site survey, develop a phased migration design, and handle installation and ongoing management where required.

Talk to an Expert today to discuss a continuity plan before support, cloud access, hardware supply, or migration timing becomes urgent.

Sources

• Cambium Networks SEC 8-K filing
• Cambium Networks product and cnMaestro Cloud report
• cnMaestro On-Premises 6.0.0 user guide
• cnMaestro On-Premises best practices
• NIST FIPS 140-3 Certificate 5518: Cambium PTP 700
• NIST FIPS 140-3 Certificate 5515: Arista WiFi Access Points
• NIST FIPS 140-3 Certificate 5072: Ceragon IP-20/IP-50
• NIST FIPS 140-3 Certificate 5107: Aviat WTM 4000