ARRIS SURFboard S34 stuck at low upload speeds? Check your device registration — not your plan

If you're running an ARRIS SURFboard S34 and your upload is far below what your plan states, read this before anyone talks you into a plan change. I just spent four days on it, and the cause wasn't my plan, my line, my router, or my modem — it was that Comcast's device database never registered my modem's MAC as an S34.

My symptom: 1 Gig plan, download fine at 600–800 Mbps, upload stuck between 6 and 35 Mbps. Now resolved at 117 Mbps up, with no plan change and no price increase.

There are several existing threads here from S34 owners with the same symptom, so this appears to be a recurring pattern with this model rather than a one-off.

First, know what your S34 is actually certified for. The S34 is on Xfinity's own compatible-devices list as supporting enhanced speeds up to 2.32 Gbps down / 444 Mbps up. If you're told your modem doesn't support your plan's upload speed, that's incorrect and worth pushing back on politely.

Step 1 — Find what you're supposed to be getting.
Account → Broadband Facts label (customer.xfinity.com/broadband-labels). Note the "Typical upload speed" figure. That's the number to hold everyone to. Mine said 117 Mbps.

Step 2 — Measure what you're actually getting.
Use speedtest.net, wired if possible. Built-in OS speed tools can read low — macOS's networkQuality measures capacity under load and showed me 78 Mbps upload over Wi-Fi at the same moment Ookla showed 117. If your numbers look off, confirm with a second tool before concluding anything.

Step 3 — Check whether your area has the mid-split upgrade.
This is the step nobody mentions and it takes ten seconds on the S34. Log into 192.168.100.1, open Event Log, and look for CMSTATUS:US_Diplexer_Mode_Change:

• [5-85MHz] = mid-split — your area is upgraded
• [5-42MHz] only = sub-split — not upgraded yet

Sub-split means ~35 Mbps is your ceiling until the area is upgraded, and no support call changes that. Mid-split means you should be getting the higher tier — keep going.

Step 4 — Compare against Comcast's published configurations.
xfinity.com/networkmanagement lists every tier they run. For 1 Gig there are exactly two HFC options: Sub-Split 1000/20 and Mid-Split 1,000/100 (measured ~114 up). There is no 35 Mbps 1 Gig tier in that document. If your S34 registers mid-split but you're well under 100, something on the account side is wrong.

Step 5 — The S34-specific one: check the device registration itself.
Your account page can display "ARRIS S34" while the underlying device record is wrong or missing. Mine did, for two days — an agent had typed the model onto the account page manually, but in the actual device database the CM MAC was never associated with an S34.

That single field is what gates the higher upload tier. Because the provisioning system couldn't confirm my modem was mid-split capable, it kept serving a legacy upstream config — through four reprovisioning signals, a coax reset, and three agents who each told me my plan tier was the problem. The actual fix took about two minutes once someone corrected the device record and pushed a new boot file.

Ranked list of causes, cheapest first:

1. Router QoS or traffic limits — free to check, and genuinely the cause sometimes.
2. Device registration mismatch — the S34-specific one described above.
3. Legacy plan tier — real, but verify 2 first.
4. Area not yet upgraded — Step 3 answers this immediately.

The three questions that actually move things with support:

• "Is my CM MAC registered to an ARRIS S34 in your device database, or was the model entered manually on my account page?"
• "What upload tier is my account provisioned for right now?"
• "My S34 registers in mid-split mode (5–85 MHz). Can you confirm the boot file being served matches that?"

Your S34's CM MAC is on the sticker underneath, labeled HFC MAC ID.

One warning. If you're told the fix requires a plan change that raises your bill or costs you a price guarantee, ask them to verify the device registration first. In my case that proposed plan change would have cost roughly $60/month more — to fix what turned out to be a wrong entry in a database field.

---