It'll just be me being awkward then...…

I think that there can be issues with some of the FIOS routers. I recently moved from a location with a FIOS router and over the years I learned that the network would get its knickers tied in a knot unless I rebooted the router every month or two. Nothing special with the reboot, I just waited for a time when no one needed an external connection, then rebooted only the router. I also have a business location with FIOS. It’s a very simple network, no SONOS, and the network becomes unstable without the monthly router reboot. There was a positive FIOS experience at a suburban location. Over several years the only reboot was due to an occasional power outage.

Why oh why did I run this update? Because I thought things would improve 🤣.

Instead now after the update I can’t play anything continuously - encoding errors, general errors, etc. etc. on all streaming services, Apple, Spotify and Sonos Radio.

I have reset all services, reset my router, powered down all speakers etc. etc. You all know the drill.

I have a fibre to the premises connection, and almost never have internet dropouts.

Finally resorted to calling Sonos Support. 

The support person didn’t believe that I had an issue from their diagnostics. Another hot mess from Sonos:

iOS - 80.30.35 and New Firmware version - 91.0-70011 ☠

You have been warned.

Sonos Update Failures: A Logical Breakdown

Sonos is deflecting responsibility for its latest system failures by blaming users’ networks. This tactic shifts the burden of proof and remediation onto the customer, despite clear evidence that the issue stems from Sonos’s own update.

The Deflection Loop

By claiming “it’s the network,” Sonos forces users to:

• Contact their ISP or network administrator
• Run diagnostics
• Attempt to isolate and prove the issue
• Rebuild or reconfigure their network
• Discover that none of these steps resolve the problem

At which point, users return to Sonos support—only to be:

• Dismissed
• Disbelieved
• Told again that it’s the network

A Simple Logic Test

Let’s examine two key moments:

• Moment A: System worked perfectly before the update
• Moment B: System failed immediately after the update

No network changes occurred between A and B. Therefore, if the system fails at B, the fault lies in Sonos’s updated software—not the network. The network didn’t change. Sonos’s ability to connect did.

Why the Blame Game?

Sonos’s insistence on blaming the network likely serves a PR purpose:

• If it’s “user error,” it’s not a news story.
• If it’s a systemic software failure, it risks public backlash.
• By deflecting, Sonos diminishes public awareness:
  • Delays escalation & visibility until enough users post on Reddit, forums, and Google to force visibility.

A Diagnostic Walkthrough

To isolate the issue, I built a dedicated sub-network:

1. Created a subnet with only Sonos devices
2. Connected via iPhone running the Sonos app
3. No improvement—same post-update failure - moment b behavior
4. Ran ping tests—subnet fully functional
5. Added and removed devices—no degradation
6. Sonos still failed to connect or operate properly

This further confirms: the network is not the issue. The update is.

Customer Support Experience

After hours of troubleshooting and multiple calls:

• Level 1 support repeated the “network” script 
• Escalation to Level 2 took days
• Still no resolution

Meanwhile, other users report bricked devices, overheating, degraded sound, and persistent connectivity failures.

Final Thoughts

I post this in solidarity with fellow users impacted by this update. After 8+ hours of wasted effort, I’ve ordered speakers from another manufacturer. Sonos appears to be using customers as unpaid QA testers. Decisions seem driven by marketing—not engineering.

If anyone from Sonos reads this: your update rollout is driving away loyal customers.

​@Hulla 

I’m having no such issues with the update. However your profile shows no Sonos products and you posted an almost identical post eight (8) months ago. Makes one wonder about the legitimacy.

Hello ​@AjTrek1

I am legit, and find it vastly amusing that you would try to insinuate otherwise, perhaps to help deflect and continue the Sonos line? I have 7 registered devices, ranging from as far back as 2019. SL1, SL2, Beam, Move, etc etc. That my account on the shopping website doesn’t auto link to the customer support or community, falls on SONOS (again) and not on anything I have done. I as the consumer, cannot make Sonos correct their errors - as seen with this repeated (and as you said near identical) behavior on their part. 

I see where I can toggle the devices owned under Member Account - but don’t feel the desire to, since I have answered your question. Selecting a toggle doesn’t prove a thing. My account in the community was built last year when the epic boondoggle happened. And I haven’t been back till now, for the same reason I didn’t go on from 2019 till 2024 - I didn’t need to participate in the community in order to review and read what was being said.

I came on last year, because I felt the need to share - and that is the same reason I came on now. As for implying “Identical” complaints- that the behavior is similar to last year, doesn’t negate the problem. In this round, in the last two days, I have done 8 hours or more of troubleshooting, many calls to customer support, and watching others on here with similar issues be disregarded  - I felt the need to participate in order to support others facing similar problems. 

The issues last year were a large systemic problem. 
It looks solidly to me, as if there is about to be yet another epic update launched by non technical people - to be “first to market” instead of listening to or perhaps even having testers.
 

Thanks for asking.

😉

​@Hulla 

You say your intentions are to show solidarity for others which by looking at this thread only amount to approximately 5-6 members. If you know anything about tech and updates there are always going to be a select few whose devices/networks can’t properly handle the update as opposed to the vast majority. That applies to any company not just Sonos.

Your participation seems only to come when you can add fuel to the fire; so to speak. You also seem to be able to predict the future by claiming this update is yet another epic update leading to an apocalyptic app crisis. Not exactly your words but reading between the lines that’s what your statement implies; no matter how you want to spin it.

However you are entitled to your opinions. Good luck with your speakers from the other manufacturer.

EDIT

You mentioned that it’s the fault of Sonos that your purchase account does not sync your purchased products with this community. News flash… that would be improper for any company to expose your purchased products to a general community like this without your input. I’m sure you’d be outraged if that were the case. What you purchase is your personal business and not that of others unless you choose to make it public. Some would call that an invasion of privacy or publication of Personal Identifiable Information (PII).

When every update requires a reboot of every Sonos device, thus causing a request for a new IP address from the network, saying:

A Simple Logic Test

Let’s examine two key moments:

• Moment A: System worked perfectly before the update
• Moment B: System failed immediately after the update

No network changes occurred between A and B. 

is 100% false.  There were most certainly some network changes occurring.  Specifically, a new IP address was handed out by a router that may or may not be handing out IP addresses that are currently in use.  Multiply this by the number of Sonos units on your system and you now know why “IT WAS THE %*%$# UPDATE!!!” is a foolish conclusion. 

Also take into account that the dozen or so complaints which show up here after an update would number in the thousands if an actual bug was present in the update, and not only is that conclusion foolish, it’s downright stupidity. 

I’ll end this by saying that in the almost 2 decades I’ve been posting here, I can count on one hand the number of times there was an actual bug in the Sonos software.  The rest of the time, a simple network refresh and assigning of reserved IP addresses was the cure.

​@AjTrek1 

Again, your implication that I should be active on the community boards, when nothing is wrong is … interesting.

I wouldn’t come to Sonos Community except to look for similar reports, issues, and work arounds. When I see others are having similar challenges, and are being given the same information, I list my troubleshooting as a method to clarify that steps have been taken, CS has been reached to, and resolution has not followed.

It’s fortunate that it isn’t everyone but it is real, and it is happening.

And thank you, I do look forward to the new speakers arriving, I’m currently using my camping speaker for music (not a sonos product) - and look forward to having music again. 🤞

​@Hulla 

That’s the problem a lot of members like yourself think that a community is only to report issues or complaints. That’s not the sole purpose. You can provide posts on what you find positive as well. Maybe suggest a feature request or report a positive discovery made that is useful to others as Sonos is very versatile.

Also, be sure to read the EDIT to my previous post.