Arris Surfboard S33 Blinking Green Light

If you're staring at an ARRIS Surfboard S33 blinking green light, take a breath. It's rarely a dead modem. Most of the time, the S33 is simply working through its startup handshake with your cable provider.

That handshake follows the DOCSIS 3.1 standard, the same spec every modern cable modem is built on. Per CableLabs, a modem has to lock downstream channels, complete upstream ranging, and pull a configuration file before it can pass any traffic. On the S33, that whole sequence usually takes two to five minutes.

Here's how to read which phase your modem is stuck in.

Quick Answer

Quick Answer

A blinking green light on the ARRIS Surfboard S33 is usually normal. The Receive, Send, and Online LEDs blink during startup. A solid light means that phase finished.

An Ethernet LED blinks during normal data traffic. If blinking lasts past five minutes, check your coax and signal levels.

Why Your S33 Blinking Green Light Isn't Always a Bad Sign

Your S33 doesn't have a screen. It talks through five small LEDs on the front panel. Each one narrates a different stage of the boot process.

Here's the rule that clears up most of the confusion. A blinking LED means "working on it." A solid LED means "done with that step."

So a blinking green light is a progress bar, not an error code. The modem is telling you it's mid-task. Panic only makes sense when the blink never stops, or when it loops backward to an earlier stage.

Blinking green is normal when

  • The modem was just plugged in
  • You power cycled it after an outage
  • Your ISP pushed a firmware update
  • An Ethernet LED is blinking, which just means data is moving
  • The modem is under five minutes into its boot

Blinking green is a problem when

  • It lasts more than five to ten minutes
  • The Online LED blinks forever while Receive and Send sit solid
  • The LEDs cycle backward, like Online going dark and Receive blinking again
  • The same pattern repeats after a factory reset and a fresh coax line

What the S33 is actually doing while it blinks

The startup order is fixed. Power comes first. Then the modem hunts for downstream channels.

Then it ranges upstream. Then it grabs an IP address and a configuration file.

Only after all four steps does the Online LED go solid. That order matters because it narrows the fault fast. A stuck Receive LED points at your coax or the cable plant.

A stuck Online LED points at provisioning or your ISP's network.

The hardware you're working with

The S33 is a DOCSIS 3.1 cable modem with 32 downstream and 8 upstream DOCSIS 3.0 channels, plus DOCSIS 3.1 OFDM carriers. It ships with a 2.5 Gbps Ethernet port and a second 1 Gbps port. Manufacturer documentation from CommScope describes each LED state in detail.

One more thing worth knowing. The S33 is a modem only. It has no built-in Wi-Fi.

If you see a blinking green Ethernet light and still have no internet, the modem may be fine and your router may be the problem.

First, Identify Which LED Is Blinking Green

Before you touch a single cable, figure out which light is blinking. The fix is completely different for each one.

The S33's front panel has five indicator lights in a row. From left to right they read Power, Receive, Send, Online, and Ethernet. Each label sits directly under its LED.

On two-port revisions, the Ethernet indicator may be split into Ethernet 1 and Ethernet 2.

If you can't read the labels from where you're standing, unplug the modem and look closely. Or grab your phone and zoom in on the panel. Getting this wrong sends you down the wrong troubleshooting path for twenty minutes.

S33 LED reference table

LEDWhat it tracksBlinking green meansSolid means
PowerElectrical power and bootBooting or firmware updatePowered on and ready
ReceiveDownstream channel lockScanning for downstream channelsDownstream locked
SendUpstream rangingRanging upstreamUpstream locked
OnlineIP address and provisioningGetting IP or config fileFully online
EthernetLAN link and trafficData moving on that portLink up, no traffic

Why the label matters more than the color

A blinking green Online light and a blinking green Ethernet light look identical from across the room. They mean opposite things.

Ethernet blinking is good news. It means your router and modem are talking to each other. Online blinking means the modem hasn't finished registering with your ISP.

How long should each LED blink?

Normal boot timing on the S33 looks roughly like this.

  • Power: solid within seconds of plugging in
  • Receive: blinks 10 to 60 seconds, then goes solid
  • Send: blinks 5 to 30 seconds, then goes solid
  • Online: blinks 5 to 30 seconds, then goes solid
  • Total: two to five minutes from a cold start

If any single stage runs past two or three minutes, that's your bottleneck. That's the one to chase.

What Each S33 LED Sequence Actually Means

Now let's walk through each LED one at a time. For every one, we'll cover what the modem is doing, how long it should take, and what to check if it hangs.

Power LED Blinking Green

The Power LED blinks during boot and during firmware updates. A short blink at startup is completely routine.

If Power blinks for more than a couple of minutes, the modem may be stuck mid-boot. Unplug the power adapter, wait 30 seconds, and plug it back in.

Still blinking? Check the adapter itself. The S33 uses an external power supply, and a failing adapter can cause partial boots.

Try a known-good adapter with matching voltage and polarity if you have one.

Also check heat. The S33 needs airflow. A modem crammed behind a TV or stacked under a router can throttle or reboot on its own.

If the Power LED blinks forever with a good adapter and decent airflow, the unit is likely failing. That's a warranty or replacement conversation.

Receive LED Blinking Green

This is the most common stuck state, and it's almost always a signal problem.

The Receive LED blinks while the modem scans for downstream channels. Once it locks, the light goes solid. If it keeps blinking, the modem can't find a clean downstream signal.

What to check, in order:

  • Tighten the coax at the modem and at the wall
  • Remove any splitter between the wall and the modem
  • Check for a damaged or kinked coax cable
  • Try a different coax wall outlet if you have one
  • Look for a loose terminator on an unused splitter port

Splitters are the usual suspect. Every split costs you signal. A three-way splitter can knock 5 to 7 dB off your downstream level, which is often enough to stop a lock dead.

If the Receive LED still blinks after all that, the problem is likely outside your home. That's an ISP call.

Send LED Blinking Green

The Send LED blinks while the modem ranges upstream. Ranging is how the modem finds the right transmit power to reach your cable provider's equipment.

A stuck Send LED usually means one of two things. Either the upstream path is too noisy, or your transmit power is maxed out.

Signs to look for on the status page:

  • Upstream power level at or above 51 dBmV
  • Multiple T3 timeouts in the event log
  • Upstream SNR below 30 dB

High upstream power is often a symptom of too many splitters or a bad cable run. Same fixes as the Receive branch. Remove splits, swap the cable, tighten everything.

If the Send LED blinks and the Online LED never lights, the modem isn't reaching the provider's CMTS. That's usually a line or plant issue, not something you can fix at home.

Online LED Blinking Green

This one is different. The Online LED blinking means your modem already locked downstream and upstream fine. It just hasn't finished registering.

Registration has two parts. First the modem gets an IP address over DHCP. Then it downloads a configuration file that tells it your speed tier.

If Online blinks forever, check these:

  • Is your modem's MAC address registered with your ISP?
  • Did you recently swap modems without updating your account?
  • Is there an outage in your area?
  • Did the modem pull a bad or mismatched configuration file?

This is the branch where a factory reset sometimes helps. A reset forces the modem to re-request provisioning from scratch. Just know that a reset also wipes any stored settings and adds another full boot cycle.

If a reset doesn't fix it, call your ISP with your modem's MAC address and serial number ready. Both are printed on the label on the bottom or back of the unit.

Ethernet LED Blinking Green

Stop worrying about this one. It's fine.

A blinking Ethernet LED means data is moving between the modem and whatever is plugged into that port. It blinks faster during heavy traffic and slower when the connection sits idle.

A solid Ethernet LED means the link is up but nothing is being transmitted right now. Both states are normal.

The only Ethernet state worth investigating is dark. If the LED is off, check the cable, try the other port, and confirm your router is powered on.

Expected boot timeline on the S33

StageTypical durationLED behavior
Power up0 to 10 secondsPower blinks, then solid
Downstream scan10 to 60 secondsReceive blinks, then solid
Upstream ranging5 to 30 secondsSend blinks, then solid
Provisioning5 to 30 secondsOnline blinks, then solid
Full boot2 to 5 minutesAll four solid

Green vs Blue on the S33: Reading Color and Blink Patterns

Color matters as much as blinking on this modem. The S33 uses two colors for a reason.

Green means DOCSIS 3.0 mode. Blue means DOCSIS 3.1 mode. That's the whole story.

Neither color is an error.

DOCSIS 3.1 is the newer standard, and it's what lets a modem bond wider channels for more speed and lower latency. When your S33 goes blue on Receive, Send, and Online, it's running in 3.1 mode. When it stays green, it's running in 3.0 mode.

Why your modem is green and your neighbor's is blue

This trips people up constantly. Color depends on what your cable provider has configured, not on your modem.

A few reasons your S33 might stay green:

  • Your speed tier doesn't need DOCSIS 3.1
  • Your local node hasn't been upgraded for 3.1 yet
  • The ISP hasn't enabled 3.1 carriers for your account
  • The modem is running a legacy configuration file

None of those are faults. As of 2026, most major US cable providers have DOCSIS 3.1 deployed somewhere in their footprint, but coverage is still uneven street by street.

Does green mean slower?

Not automatically. DOCSIS 3.0 with 32 bonded downstream channels can still deliver several hundred megabits per second.

The gap shows up on multi-gig plans. If you're paying for 1 Gbps or higher and your S33 never goes blue, that's worth a call to your provider.

Blink rate tells you something too

PatternMeaning
Slow, steady blinkPhase in progress, normal
Fast flickerData traffic (Ethernet only)
Blink, pause, blinkRetry after a failed attempt
Rapid cycling between LEDsBoot loop or power issue
Blink then solidPhase completed

A blink, pause, blink rhythm on Receive or Send usually means the modem is retrying a step it already failed. That's the pattern that points to a line problem rather than a modem problem.

The S33 Blinking Green Decision Tree: Quick Flow

Here's the whole thing as a decision path. Work top to bottom and stop when you hit a fix.

Step 1: Which LED is blinking?

If it's the Ethernet LED, you're done. That's normal traffic.

If it's Power, jump to the power branch.

If it's Receive, jump to the signal branch.

If it's Send, jump to the upstream branch.

If it's Online, jump to the provisioning branch.

Step 2: How long has it been blinking?

Under five minutes means wait. The modem is still booting.

Five to ten minutes means start checking cables.

Over ten minutes means treat it as a fault and work the branch.

Step 3: Check the status page

Open a browser and go to 192.168.100.1. That's the S33's built-in status page.

You'll see bonded downstream and upstream channels, power levels, SNR, the software version, and the event log. The event log is the fastest way to see what's actually failing.

Step 4: Work the branch

If Receive is stuck blinking

  1. Tighten coax at both ends.
  2. Remove splitters between the wall and the modem.
  3. Swap the coax cable.
  4. Try another wall outlet.
  5. Call your ISP if it still blinks.

If Send is stuck blinking

  1. Check upstream power on the status page.
  2. Look for T3 timeouts in the event log.
  3. Remove splitters and amplifiers.
  4. Check for a MoCA filter issue if you have cable TV.
  5. Call your ISP.

If Online is stuck blinking

  1. Confirm your ISP has your MAC address.
  2. Check for a local outage.
  3. Power cycle once.
  4. Factory reset as a last resort.
  5. Call your ISP with MAC and serial ready.

If Power is stuck blinking

  1. Reseat the power adapter.
  2. Try a different outlet.
  3. Improve airflow around the modem.
  4. Test with a matching adapter if you have one.
  5. Replace the unit if nothing changes.

Step 5: Know when to stop troubleshooting

If you've removed splitters, swapped cables, confirmed your MAC is registered, and the light still blinks, the problem isn't on your side of the wall.

Call your ISP. Give them three things: your modem's MAC address, its serial number, and what the status page shows for downstream power, upstream power, and SNR.

Branch A: Power or Ethernet LED Blinking Green

Two very different problems sit in this branch. One is a real fault. The other is completely normal behavior.

If the Power LED is blinking green

Start with timing. A blinking Power LED for the first 30 to 60 seconds after plugging in is normal. The modem is loading firmware and running self-tests.

Past two minutes, treat it as a fault. The S33 has no user-serviceable parts inside, so everything you can fix lives outside the case.

Work through these in order:

  1. Unplug the adapter from the wall and the modem. Wait a full 30 seconds.
  2. Plug it back in and watch the sequence from the start.
  3. Confirm the adapter is the original or a matching replacement.
  4. Move the modem to an open spot with airflow on all sides.
  5. Try a different wall outlet on a different circuit.

Manufacturer specs for the S33 list a 12V DC external power adapter. A mismatched adapter with the wrong polarity or amperage can cause partial boots. It can also cause a boot loop where Power blinks, goes solid, then blinks again.

If the Power LED blinks in a loop

A repeating loop is a distinct symptom. It usually means the modem is rebooting itself, not just booting slowly.

Common triggers:

  • Failing power adapter
  • Overheating from blocked vents
  • Unstable wall voltage on a shared circuit
  • Corrupted firmware that keeps failing its checksum

Heat is the sneaky one. Verified buyer feedback reports the S33 runs warm under load, which is normal. It only becomes a problem when it's boxed in with no air gap.

If the loop persists on a cool, ventilated modem with a known-good adapter, the unit is likely dying. That's a warranty claim, not a troubleshooting win.

If the Ethernet LED is blinking green

Relax. This is the one blinking light that almost never means trouble.

A blinking Ethernet LED means packets are moving across that port. It blinks faster during downloads and slower when the link sits idle. A solid Ethernet LED means the link is up with no current traffic.

Both are healthy states.

The only Ethernet state that matters is dark. If the LED is off, you've got a physical link problem.

Check these if Ethernet stays dark:

  • Reseat the Ethernet cable at both ends
  • Try the other Ethernet port on the S33
  • Swap to a known-good cable
  • Confirm your router is powered on and not in a failed boot

Port speeds and cable quality

The S33 has a 2.5 Gbps port and a 1 Gbps port. The 2.5G port only negotiates at full speed with a router that also supports 2.5G.

If you're on a multi-gig plan and seeing capped speeds, check which port you're using. Also check the cable. Cat5e handles 2.5G over short runs.

Cat6 is the safer bet.

SymptomLikely causeFirst fix
Ethernet blinks, no internetRouter or ISP issueTest direct to a PC
Ethernet solid, no internetLink up, no trafficCheck router WAN settings
Ethernet darkCable or port faultSwap cable, try other port
Ethernet blinks rapidlyHeavy trafficNormal, no action

Branch B: Receive LED Blinking Green

This is the most common stuck state on the S33, and it's nearly always a signal problem. The modem can't lock downstream channels.

What the modem is doing

The Receive LED blinks while the modem scans the coax for downstream carriers. On the S33, that means hunting for DOCSIS 3.0 QAM channels and DOCSIS 3.1 OFDM blocks.

Once it locks enough channels to proceed, the LED goes solid. If it never locks, it keeps blinking and retrying. Sometimes it locks, drops, and starts over.

The numbers that matter

Downstream signal levels live in a narrow window. Outside it, lock becomes unreliable or impossible.

MetricHealthy rangeProblem zone
Downstream power-10 to +10 dBmVBelow -15 or above +15
Downstream SNR35 dB or higherBelow 33 dB
Locked downstream channels32 (DOCSIS 3.0)Fewer than 8

These are the standard ranges cable techs work from. You'll see them on the S33 status page once you can reach it.

If downstream power is too low

Low downstream power means the signal arriving at the modem is weak. Every splitter, connector, and cable length between the street and your modem steals a little.

Typical losses:

  • Two-way splitter: about 3.5 dB
  • Three-way splitter: about 5.5 to 7 dB
  • Four-way splitter: about 7 to 8 dB
  • 100 feet of RG-6 coax: roughly 1 to 2 dB at cable frequencies

The fix is almost always to reduce loss. Remove splitters between the wall and the modem. Swap RG-59 for RG-6 if you've got old cable in the wall.

Tighten every F-connector by hand, then a quarter turn with a wrench.

If downstream power is too high

High downstream power is less common but still real. It usually shows up when you're the only drop on a node, or when the cable plant is pushing hot.

If power sits above +15 dBmV, add an attenuator. A 3 dB or 6 dB inline pad is cheap and effective. Your ISP can also adjust node levels from their end.

What to check in the event log

The event log tells you which failure you're hitting. Look for these entries:

  • SYNC Timing Synchronization failure
  • No Ranging Response received
  • T2 timeout
  • MDD timeout

T2 and MDD timeouts point at downstream problems. That matches a blinking Receive LED.

If nothing at home fixes it

Once you've removed splitters, swapped coax, and tightened every connection, the remaining causes sit outside your walls. A bad drop, a damaged tap, or a plant issue all produce the same symptom.

Call your ISP. Tell them the Receive LED never goes solid and give them your downstream power and SNR readings. That's enough for them to check the line from their side.

Branch C: Send LED Blinking Green

The Send LED blinks while the modem ranges upstream. Ranging is the process of finding the right transmit power to reach your provider's CMTS.

Why ranging matters

Your modem shares the upstream path with every other modem on the node. It has to hit the CMTS at the exact right power level. Too weak and the signal gets lost.

Too strong and it drowns out neighbors.

The modem starts low and steps up until the CMTS answers. That's why the Send LED blinks instead of just turning on.

The upstream numbers to watch

MetricHealthy rangeWarning sign
Upstream power37 to 48 dBmV51 dBmV or higher
Upstream SNR30 dB or higherBelow 25 dB
Locked upstream channels8 (DOCSIS 3.0)Fewer than 4

If upstream power sits at 51 dBmV and won't climb higher, the modem has maxed out. It's screaming as loud as it can and still not being heard.

If upstream power is maxed

Maxed upstream power almost always means excess loss on the return path. Same suspects as the Receive branch, but the symptoms hit harder.

Work through this list:

  1. Remove every splitter between the wall and the modem.
  2. Check for a bad or corroded F-connector.
  3. Look for a damaged drop cable on the outside of the house.
  4. Check for an old amplifier on the line that isn't return-path capable.
  5. Confirm no MoCA filter is sitting in the wrong spot.

That last one catches people. MoCA filters block cable TV signals from leaking into your home network. If a filter got installed between the modem and the wall, it can wreck the upstream path.

If the event log shows T3 or T4 timeouts

T3 and T4 timeouts are upstream failures. A T3 means the modem sent a ranging request and got no answer. A T4 means it tried too many times and gave up.

A few T3s during boot are normal. A stream of them means the upstream path is broken or too noisy.

Common causes:

  • Loose connector on the drop
  • Water in an outdoor connection
  • A neighbor's bad equipment injecting noise
  • A failed amplifier or tap on the plant

Only the first two are things you can fix. The rest need a tech visit.

If Send blinks and Online never lights

This combination narrows the problem further. Downstream locked fine, upstream didn't. That points squarely at the return path.

It's usually outside your home. But before you call, do one clean test. Bypass every splitter and run a single coax straight from the wall to the modem.

If Send goes solid, you found it.

Branch D: Online LED Blinking Green

This branch is different from the others. Downstream and upstream already locked. The modem just hasn't finished registering with your ISP.

The two steps behind this LED

Registration happens in two parts. First the modem requests an IP address over DHCP. Then it downloads a configuration file that sets your speed tier.

If either step fails, the Online LED keeps blinking. The modem retries on a loop.

If the modem has never been activated

A brand-new S33 won't go online until your ISP adds its MAC address to your account. That's true even if the hardware is perfect.

The MAC address is printed on a label on the bottom or back of the unit. It looks like six pairs of hex characters. You'll need that, plus the serial number, when you call.

Most major cable providers let you activate online through your account portal. You'll enter the MAC address and wait while the system pushes a config file. That usually takes a few minutes.

If you recently swapped modems

Swapping hardware without updating your account produces this exact symptom. The old modem's MAC is still on the account, so the new one gets no config file.

Log into your ISP account and update the modem on file. Or call and read them the new MAC. Either way, the Online LED should go solid within a few minutes.

If it worked before and now it doesn't

A modem that was online yesterday and is stuck today points at something else. Check these in order:

  1. Look for a local outage on your ISP's status page.
  2. Power cycle the modem once.
  3. Check the event log for TFTP errors or DHCP failures.
  4. Confirm the config file matches your speed tier.
  5. Factory reset as a last resort.

A factory reset forces the modem to re-request provisioning from scratch. That sometimes clears a corrupted config file. Just know it wipes stored settings and adds another full boot cycle.

If you see a walled garden IP

Some ISPs hand out a temporary IP in a walled garden range when a modem isn't activated. The modem looks half-online but can't pass real traffic.

If the status page shows an IP that starts with 10. or 172.16 through 172.31, that's likely a walled garden. Activation is the fix.

If the modem is activated and still won't go online

At this point the modem is doing its job. Something upstream is blocking it.

Call your ISP. Have your MAC address, serial number, and a screenshot of the status page ready. That gives their support rep everything they need to push a fresh config or check the provisioning system.

Check Signal Levels at 192.168.100.1

This is the single most useful diagnostic tool you have. The S33 has a built-in status page, and it shows exactly what the modem sees on the line.

How to reach the status page

Connect a device directly to the S33 with an Ethernet cable. Open a browser and type 192.168.100.1 into the address bar. Hit enter.

The page loads with no login on most firmware versions. If it asks for credentials, try admin for both the username and password.

You can also reach it through your router in many setups. Just browse to the same address from any device on your network.

What the page shows you

The main status screen lists your bonded channels and their health. Here's what each column tells you.

FieldWhat it means
Channel IDThe channel number the modem locked
FrequencyWhere that channel sits in the spectrum (MHz)
PowerSignal strength in dBmV
SNRSignal-to-noise ratio in dB
ModulationQAM or OFDM/OFDMA
Lock StatusLocked or not locked

Scroll down and you'll also find the software version, MAC address, and serial number.

Reading the downstream table

Every downstream channel should show Locked. Power should sit between -10 and +10 dBmV. SNR should be 35 dB or higher.

If one channel shows lower SNR than the rest, that channel is likely getting interference. A single bad channel is usually fine. Several bad channels will drag your speeds down.

If power is drifting up or down over time, the line has an intermittent fault. That's worth logging for a few days.

Reading the upstream table

Upstream channels should all be Locked with power between 37 and 48 dBmV. Anything at 51 or above means the modem is maxed out.

Watch for channels that won't lock. On a DOCSIS 3.1 modem, a couple of 3.0 channels dropping out while the OFDMA channel holds is usually tolerable. Losing the OFDMA carrier is a bigger deal.

The event log is the real gold

The status page has an event log, and it's where the story lives. Timestamps matter here. Look for what happened right before the light got stuck.

Entries worth knowing:

  • SYNC Timing Synchronization failure: downstream lock lost
  • T3 timeout: upstream ranging failed
  • T4 timeout: upstream retries exhausted
  • DHCP failure: couldn't get an IP
  • TFTP failed: couldn't download the config file
  • Config file error: config downloaded but rejected

Each entry maps to one of the branches you've already worked. T3s and T4s point upstream. DHCP and TFTP failures point at provisioning.

What to screenshot for your ISP call

Before you dial, capture three things. The downstream table, the upstream table, and the recent event log entries.

That gives the support rep concrete data instead of "the light is blinking." You'll skip the first ten minutes of scripted questions and get routed to someone who can actually help.

Power Cycle vs Factory Reset vs ISP Call

These three moves escalate in severity. Doing them in the wrong order wastes time and can make things worse. Here's when each one earns its place.

What a power cycle actually does

A power cycle clears the modem's working memory and forces a full boot from scratch. It's the first thing to try because it's free, safe, and fixes a surprising number of stuck states.

Do it in the right sequence. Unplug the modem's power adapter. Unplug your router too.

Wait a full 30 seconds, not five.

Plug the modem in first. Watch the LEDs until Online goes solid. Only then plug the router back in.

Reversing that order can leave your router holding a stale IP.

What a factory reset actually does

A factory reset wipes the modem's stored settings and forces it to re-request provisioning from your ISP. That's a bigger hammer than most people realize.

The reset button sits on the back of the S33 in a small recessed hole. You'll need a paperclip or a thin pen tip. Hold it for 10 to 30 seconds, then release.

Here's the catch. Some providers push a custom configuration file that includes your speed tier and any service add-ons. A reset can throw that away.

The modem then has to pull a fresh config, which may require your ISP to re-authorize it.

The risk nobody warns you about

If your modem is on an account with a specific config file, a reset can leave you offline longer than the original problem. Our research into user reports shows this is most common with providers that tie config files tightly to account provisioning.

That's why a reset belongs third, not first. Power cycle, check the status page, then decide.

When to call your ISP instead

Call when the data points outside your home. That means downstream power below -15 dBmV, upstream power at 51 dBmV or higher, T3 or T4 timeouts, or a MAC address your provider can't see.

Have three things ready before you dial. Your modem's MAC address, its serial number, and the status page readings. That turns a 20-minute scripted call into a five-minute fix.

Side-by-side comparison

ActionTime to completeWhat it fixesRisk level
Power cycle3 to 5 minutesStuck boot, stale IP, minor glitchesNone
Factory reset5 to 15 minutesCorrupted config, failed provisioningModerate
ISP call10 to 40 minutesLine faults, provisioning, outagesNone

If the light is still blinking after all three

Then the problem isn't software, and it isn't your account. It's physical. Move on to the coax and splitter checks below.

Common Mistakes That Keep the S33 Light Blinking

Most stuck-modem cases we've looked at trace back to one of these. Some are harmless time-wasters. A few actively make things worse.

Resetting before you've checked the signal

A factory reset won't fix a weak downstream signal. It just adds another boot cycle to a modem that was never going to lock anyway.

Check your signal levels first. If downstream power is out of range, fix that before touching the reset button.

Power cycling everything at once

Unplugging the modem, router, and any mesh nodes simultaneously scrambles the boot order. The router can come up before the modem and grab a dead WAN address.

Do it in sequence. Modem first. Wait for solid Online.

Then router.

Leaving the splitter in place

This is the single most common physical cause we see reported. A splitter that feeds three TVs is also starving your modem of signal.

For a test, run one coax straight from the wall to the modem with nothing in between. If the light goes solid, you've found your culprit.

Using the wrong power adapter

The S33 runs on a 12V DC external adapter. A generic adapter with the wrong polarity or too little amperage can cause partial boots and boot loops.

If you've misplaced the original, match the voltage, polarity, and amperage printed on the modem's label. Don't guess.

Testing over Wi-Fi

The S33 has no built-in Wi-Fi. It's a modem only. If you're testing "the internet" over Wi-Fi, you're actually testing your router.

Plug a laptop directly into the S33 with an Ethernet cable. That removes the router from the equation entirely.

Blaming the modem for a router problem

A blinking green Ethernet light with no internet usually means the modem is fine. It's talking to your router. Your router just isn't passing traffic.

Test direct to the modem. If the internet works there, your router is the problem, not the S33.

Skipping the outage check

Before you spend an hour on cables, check your provider's status page or outage map. A plant outage produces the exact same symptoms as a home wiring fault.

It takes 30 seconds and can save you a wasted evening.

Ignoring the event log

The status page at 192.168.100.1 keeps a timestamped log of every failure. Most people never open it.

A T3 timeout and a DHCP failure both cause a blinking light, but they need completely different fixes. The log tells you which one you're dealing with.

Swapping modems without updating your account

A new S33 won't come online until your provider registers its MAC address. Plugging it in and waiting won't help.

Log into your account portal or call. Either way, the MAC needs to be on file.

Buying a modem your ISP won't support

Not every provider certifies every retail modem. Per FCC rules, cable providers must allow customer-owned equipment, but they set the technical requirements.

Check your provider's approved modem list before you buy. A modem that isn't certified may never fully provision.

Stacking the modem on top of the router

The S33 runs warm. Verified buyer feedback reports it gets noticeably hot under load, which is normal for the chipset.

What isn't normal is blocking its vents. Give it an inch of clearance on every side. Heat causes random reboots that look exactly like a stuck boot.

Assuming blinking means broken

It usually doesn't. Blinking means the modem is working on a step. Only a blink that never resolves is a fault.

Replace the modem only after you've ruled out signal, provisioning, power, and cable issues. That's the last step, not the first.

Coax, Splitters, and Signal Quality Fixes

If you've made it here, the modem is probably fine and the line is the problem. This is the section that actually fixes it.

Start with the cable type

Older homes sometimes still have RG-59 coax in the walls. RG-59 has higher loss than RG-6 at cable frequencies and was never meant for modern DOCSIS service.

Cable typeTypical loss per 100 ftBest for
RG-594 to 6 dBLegacy cable TV, avoid for modems
RG-61 to 2 dBStandard cable internet, DOCSIS 3.0
RG-6 quad shield1 to 2 dBHigh-interference runs, DOCSIS 3.1

If your wall plate has an old thin cable behind it, that alone can explain a stuck Receive LED.

Check every F-connector

Loose connectors are the most underrated cause of signal problems. A single bad connector can drop several dB and inject noise.

Hand-tighten every connection first. Then give it a quarter turn with a 7/16-inch wrench. Industry guidance from SCTE puts the target torque for F-connectors at roughly 7 to 8 inch-pounds.

Don't overtighten. You can crack the dielectric or strip the threads.

Look for corrosion and water damage

Any outdoor connection is a candidate for water ingress. Look for green or white corrosion on the center conductor or the connector body.

If you find it, the connector needs replacing, not cleaning. Water in a connection also causes intermittent faults that come and go with the weather.

Understand what your splitters are costing you

Every splitter divides signal, and the loss isn't equal across all ports. Unbalanced splitters send more signal to one port and less to the others.

Splitter typeTypical loss per portNotes
2-way balanced3.5 dBFine for one modem plus one TV
3-way balanced5.5 dBCommon culprit in modem faults
3-way unbalanced3.5 dB and 7 dBUse the low-loss port for the modem
4-way7 to 8 dBAvoid if the modem is on it

If you need a splitter, use the lowest-loss port for the modem. Better yet, give the modem its own dedicated run.

Remove amplifiers that can't handle the return path

Old cable TV amplifiers often boost downstream only. They block or distort the upstream signal your modem needs to range.

If you find an amplifier on the line, check whether it's return-path capable. If it isn't, remove it. Modern DOCSIS service doesn't play well with one-way amps.

Check for MoCA filters in the wrong spot

A MoCA filter blocks cable TV frequencies from leaking into your home network. It belongs at the point of entry, not between the wall and the modem.

If a filter got installed on the modem's line, it can wreck both downstream and upstream. Move it or remove it and retest.

Use an attenuator when power is too hot

Most people have the opposite problem, but too much signal causes faults too. Downstream power above +15 dBmV can overload the modem's tuner.

A 3 dB or 6 dB inline attenuator costs very little and drops the level into range. Check the status page after adding one.

Fix the wall plate and barrel connector

The connector behind your wall plate is a common failure point. It's a female-to-female barrel that joins the in-wall cable to your jumper.

If it's loose, corroded, or the wrong impedance, it degrades everything downstream of it. Pull the plate and inspect it. It's a two-minute job.

Grounding and surge protection

Coax lines need proper grounding, and that's covered by the National Electrical Code in Article 810 and Article 820. The drop should bond to your home's grounding electrode system at the point of entry.

This isn't a DIY fix for most people. If you see a disconnected or missing ground block, have a technician handle it. It's both a safety issue and a code requirement.

For surge protection, an inline coax surge protector at the ground block can save your modem during a nearby strike. Replacing a $10 protector beats replacing a modem.

Give the cable room to breathe

Don't coil excess coax into a tight loop or staple it against a sharp corner. Coax has a minimum bend radius, and kinking it changes the impedance at that point.

A kink creates a reflection that shows up as reduced SNR on one or more channels. Keep bends gentle and avoid tight zip ties.

Retest after every change

Change one thing at a time. Then check the status page.

If downstream power moved from -14 dBmV to -6 dBmV after removing a splitter, you're on the right track. If nothing changed, put it back and try the next thing.

Chasing two variables at once means you'll never know which fix worked.

Frequently Asked Questions

Is a blinking green light on the ARRIS Surfboard S33 normal?

Yes, during startup it's completely normal. The Receive, Send, and Online LEDs all blink while the modem completes its DOCSIS handshake. That takes two to five minutes.

Blinking past ten minutes means a phase is stuck. At that point, check which LED is blinking and work that branch.

How long should the S33 take to go online?

A cold boot takes two to five minutes from the moment you plug it in. The downstream scan is usually the longest phase, running 10 to 60 seconds. Upstream ranging and provisioning each take 5 to 30 seconds.

Anything beyond ten minutes points to a signal or provisioning problem.

Will a factory reset fix a blinking green light on the S33?

Sometimes, but only for provisioning faults. A reset won't help if your downstream or upstream signal is out of range. Check the status page at 192.168.100.1 first.

If power levels and SNR look healthy, a reset is worth trying. If they don't, fix the signal instead.

Why does my S33 stay green and never turn blue?

Green means the modem is running in DOCSIS 3.0 mode. Blue means DOCSIS 3.1. The color depends on what your cable provider has enabled on your node and account.

It isn't a fault. If you're paying for a multi-gig tier and never see blue, ask your provider whether 3.1 is active on your line.

Can a blinking green light mean my modem is broken?

Rarely. Blinking means the modem is working through a step. A hardware failure usually shows up as a Power LED that blinks in a loop, or a modem that never gets past the first few seconds of boot.

Rule out signal, cable, power, and provisioning before you replace the unit.

Does the S33 work with Xfinity, Spectrum, and Cox?

The S33 is certified for DOCSIS 3.1 and works with most major US cable providers, including Xfinity, Spectrum, Cox, Optimum, and Mediacom. Compatibility still depends on your specific speed tier and whether your provider has approved that model. Check your provider's approved modem list before buying.

Final Decision Guide: Fix It, Replace It, or Escalate

Work down this table until you find your symptom. The right column tells you what to do next.

What you're seeingMost likely causeWhat to do
Ethernet LED blinking, internet worksNormal trafficNothing
Power blinking under 60 secondsNormal bootWait
Power blinking in a loopAdapter, heat, or failing unitSwap adapter, improve airflow, then replace
Receive blinking, downstream power below -15 dBmVToo much loss on the lineRemove splitters, swap coax, call ISP
Receive blinking, SNR below 33 dBNoise on the lineCheck connectors, call ISP
Send blinking, upstream power at 51 dBmVReturn path maxed outRemove splits and amps, call ISP
Send blinking with T3 or T4 timeoutsUpstream failureCall ISP, report the timeouts
Online blinking, MAC not registeredProvisioningActivate the modem with your ISP
Online blinking after a modem swapOld MAC still on the accountUpdate your account with the new MAC
Online blinking with DHCP or TFTP errorsConfig file failurePower cycle, then factory reset
Everything solid but no internetRouter problemTest direct to the modem, then check the router
Lights never progress past PowerHardware faultReplace the modem

The three-question shortcut

Ask yourself three things in order. Is the blinking LED the Ethernet one? If yes, you're done.

If no, has it been blinking more than ten minutes? If no, wait.

If yes, open the status page and look at downstream power, upstream power, and SNR. Those three numbers tell you whether the fault is in your home or outside it.

Fix it yourself when

The fault is inside your walls. That means loose connectors, a splitter in the wrong place, a bad jumper cable, a kinked run, or a modem that needs a clean power cycle.

You can also fix provisioning issues yourself in most cases. Activating a modem through your provider's portal takes minutes and needs nothing but the MAC address.

Call your ISP when

The numbers say the line is bad. Downstream power outside the -10 to +10 dBmV window, upstream power at or above 51 dBmV, SNR under 33 dB, or a stream of T3 and T4 timeouts all point outside your home.

Give them the readings. That's the fastest route to a truck roll or a node-level fix.

Replace the modem when

You've removed every splitter. You've swapped the coax. Your provider has confirmed the line is clean and the MAC is registered.

The adapter is the original. The modem has airflow.

If the light still blinks through a full boot cycle at that point, the hardware is the remaining variable. That's when a replacement, or a warranty claim through CommScope, is the right call.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.