Connectivity Intel: Peplink 8.6.0 Bug, Verizon Outage

Short week, but not a quiet one. Here is what mattered between August 31 and September 7.

Peplink Confirms 8.6.0 Bug Breaking RADIUS and SIP Over Tunnels

The most important thread of the week for anyone running Peplink gear is buried on page two of the 8.6.0 GA announcement. Peplink engineering has now confirmed a bug in firmware 8.6.0 involving fragmented UDP packets across SpeedFusion and PepVPN tunnels. The reported trigger is WPA2-Enterprise Wi-Fi clients doing EAP-TLS authentication against a RADIUS server on the far side of a tunnel. The client certificate exchange produces a packet around 1700 bytes, it fragments, and the handshake loops until it fails. Peplink support ticket 26081099 confirmed the behavior, and staff posted on September 3 that a fix is in progress.

The same thread has multiple operators reporting SIP registration and one-way audio failures for remote phones over PepVPN after upgrading core routers to 8.6.0, including one deployment with roughly 2,000 sites seeing a handful of phones fail at 10 to 15 locations. Peplink has asked those users to open tickets so it can confirm whether the SIP case is the same root cause. In every reported case, rolling back to 8.5.4 cleared it.

Practical guidance: if your topology puts RADIUS, SIP, or anything else that produces large UDP datagrams on the other end of a Peplink tunnel, hold on 8.5.4 until the patched build ships. Reminder from last week still applies: 8.5.5 is the maintenance track for units not moving to 8.6.0, and the 8.6.0 release notes require BR1 Pro, BR1 Pro 5G, BR2 Pro, Dome, Transit and B One models to step through 8.5.4 first.

Also from Peplink this week: 5G Dongle and Adapter firmware 2.1.0 Beta 1 posted September 3, a FusionHub licensing thread where AWS instances behind NAT are throwing a “software counterfeiting” error on activation, and a webinar on the 5G Adapter scheduled for September 15 at 11 AM CDT.

Verizon Regional Outage Hits Four States

On Thursday, September 3, Verizon Wireless confirmed a service interruption affecting customers in Arkansas, North Mississippi, Oklahoma and West Tennessee. Downdetector reports climbed past 16,000 in about 90 minutes before Verizon announced restoration mid afternoon Pacific time. Verizon’s guidance for lingering issues was a device restart. Separately, at least one report from Cabot, Arkansas described nearly three days without Verizon voice service leading into the weekend, which suggests the recovery was uneven in some rural pockets.

If you run Verizon as a primary WAN on a single-carrier router in that footprint, this is the kind of event that a dual-SIM or dual-modem design with a second carrier absorbs without a truck roll.

Starlink: European Disruption, All Falcon 9 Starlink Launches Move West

Starlink users in Europe saw a multi-hour disruption early on September 3. Reports on German outage trackers started around 3:43 AM local time and had largely cleared by 11:45 AM. One business user with nine Starlink-connected sites reported two of them offline, and at least one user described the link staying up while DNS resolution failed. Starlink did not post a public incident summary. For customers bonding Starlink with cellular through a Peplink SpeedFusion setup, this is exactly the failure mode that bonding is built for, and worth checking your logs to see whether failover behaved the way you expected.

On the infrastructure side, SpaceX has confirmed that Florida Starlink launches will shift to Starship, making Vandenberg the sole Falcon 9 Starlink launch site. The 80th Starlink mission of 2026 flew from Vandenberg on September 6 with 27 satellites. The constellation stands at roughly 12,900 launched and 11,078 operational. No pricing or plan changes this week. The Global Roam shutdown and the 30 day international cap on Roam Unlimited covered in August remain the operative changes. See the Starlink support site for current plan terms.

Firmware & Security Watch

Teltonika community traffic is still dominated by 7.24.x upgrade fallout. New this week: a RUT956 whose DDNS configuration page disappeared after update, a RUTC50 custom-APN eSIM that stopped working after 7.24.1, an invalid checksum error mid-upgrade, a thread titled “Worried about firmware upgrade to 7.24.3” that drew staff replies, and a 14-reply thread asking Teltonika to ship an updated Tailscale package because the bundled version has known security issues. Teltonika staff also publicly released a modem firmware file for TRB501 units on the RG520N-EB module after a 23-reply thread. Our advice from last week stands: stage 7.24.x on a canary unit before touching production.

Cradlepoint was quiet in the window. The customer forum portal returned a rendering error to our tooling, and the most recent NetCloud OS release notes we could confirm are the July 7.26.61 FR2 build. If you are on NetCloud, check your release channel directly.

Digi forums had one router-adjacent thread in the window, on XBee 3 Cellular registration in Remote Manager. No new DAL firmware or advisories. On the Semtech and Sierra Wireless side, the AirLink forum’s active thread is an RV50X radio connectivity issue that reached 11 replies on September 4. No ALEOS release in the window. Semtech still carries the CISA KEV entry for CVE-2018-4063 on legacy ALEOS, so if you still have an ES450 or similar in the field, that is a replacement conversation, not a patch conversation.

Inseego published no product news this week. The company presents at the Lake Street growth conference on September 10. Its August Q2 results noted the refreshed MiFi PRO M4 family is now live at all three Tier 1 carriers, and the unlocked M4000 remains the model to look at for multi-carrier deployments.

One broader item worth a read: researchers at Nanyang Technological University used a multi-agent AI system to find 84 previously unknown vulnerabilities across seven 4G and 5G core implementations, 81 of which received CVEs. The headline flaw, CVE-2026-8233, is a PFCP session hijack validated against two commercial 5G cores. This is carrier-side, not something you patch on a router, but it is a preview of how fast vulnerability discovery is about to move for everything in the telecom stack, edge devices included.

RouterCVE Report Card

Our tracked brands held steady on the RouterCVE report card this week. Peplink, Cradlepoint, Digi and Inseego remain A+ with zero CVEs in the last 30 days. Teltonika is A with 2, trend Getting Worse. Semtech is A minus with 2, also trending worse, and remains the only tracked 5Gstore brand with a CISA KEV entry. Katalyst remains NR, too new to rate. Starlink is A+ with one CVE in the 30 day window.

Versus the numbers we published last week, the 30 day counts on the legacy and consumer side moved: Cisco dropped from 43 to 31, GL.iNet from 21 to 5, and TP-Link rose from 12 to 14. Ubiquiti (22), TRENDnet (18) and Palo Alto Networks (12) were unchanged. Netgear logged 10. No grade changes and no new manufacturers were added this week.

Spectrum & Industry

Two FCC comment deadlines land Tuesday, September 8. First, comments are due on the Third Further Notice of Proposed Rulemaking that would bar authorization of any device incorporating a component from a Covered List entity, impose term limits on equipment authorizations, require bills of materials with every application, and push all devices in Covered List sectors from SDoC to full certification. Reply comments were extended to September 28. Second, reply comments are due on bidding procedures for the Upper C-Band auction, 160 MHz across 3.98 to 4.14 GHz, now scheduled to begin in April 2027. Details on both are on the FCC site.

Also on the regulatory calendar: comments on the space launch spectrum notice are due September 14, the FCC’s mobile and fixed services working group meets September 15, and the next Open Meeting is September 30. The router Covered List scope question we flagged last week, whether the NIST IR 8425A consumer router definition reaches industrial cellular gateways, is still unanswered.

Carrier news was mostly corporate. Activist investor Elliott has built a stake in Deutsche Telekom and is publicly pushing it to drop any full merger with T-Mobile US in favor of buybacks, which follows July reporting that T-Mobile’s own executives no longer support the idea. T-Mobile also named former Shell CFO Jessica Uhl as its next finance chief. AT&T’s Internet Air increase of 5 dollars per month for pre-October 2025 plans takes effect September 28.

On the satellite-versus-tower question, two new analyst reports presented at a WIA webinar on September 1 landed on the same conclusion: direct-to-device satellite is a supplement for terrestrial coverage, not a replacement, because people spend more than 90 percent of their time indoors or in vehicles and satellites cannot acquire enough spectrum to compete on capacity. SpaceX’s 65 MHz purchase from EchoStar is less than a quarter of what each of the big three carriers holds. The three carriers’ joint venture to pool spectrum for dead zone coverage remains their answer to a Starlink Mobile MVNO.

One note on sourcing: Reddit remains inaccessible to our research tooling, so social chatter from r/Peplink, r/Starlink, r/tmobileisp and related communities was not captured this week. The AT&T community forum returned stale cached content and could not be surveyed. Verizon’s forum was retired in August.

5Gstore Take

Three things to act on.

First, check your Peplink tunnel dependencies before you touch 8.6.0. If you have RADIUS, SIP, or any large-datagram UDP service on the far side of a SpeedFusion or PepVPN tunnel, stay on 8.5.4 until Peplink posts the fix. If you already upgraded and phones or Wi-Fi auth got flaky, you are not imagining it, and rolling back is a supported path.

Second, the Verizon and Starlink events on the same day are a useful stress test. Pull your failover logs from September 3. If a single-carrier or single-path site went dark, that is the business case for a second SIM, a second carrier, or a bonded satellite plus cellular design.

Third, if you or your customers still have Covered List exposure in the supply chain, the September 8 FCC comment deadline is the last chance to weigh in before the component-level prohibition moves forward. The direction of travel is clear even if the final rule is not.

Not sure which firmware track your fleet is on, or whether a dual-carrier design makes sense for your sites? Get in touch and we will work through it with you.

FAQ

Should I upgrade my Peplink router to firmware 8.6.0 right now?
If nothing on the far side of your SpeedFusion or PepVPN tunnels relies on large UDP packets, most users are fine. If you run RADIUS EAP-TLS authentication or SIP phones across a tunnel, stay on 8.5.4 until Peplink releases the fix it confirmed on September 3.

Was the September 3 Verizon outage nationwide?
No. Verizon confirmed the interruption was limited to parts of Arkansas, North Mississippi, Oklahoma and West Tennessee, and reported restoration the same afternoon, though some rural customers reported longer recovery.

Did Starlink change pricing or plans this week?
No. The most recent changes are the August Global Roam shutdown and the 30 day international limit on Roam Unlimited. The September 3 event was a service disruption in Europe, not a plan change.