20 Days Without Internet: a DSL Line Fault Between the Node and the Home, Not the Router (Sydney City)

Student · Sydney CityTelstra → SuperloopDSL line fault20+ daysNode-to-home faultNBN technician fix

A student in Sydney City lost all internet one morning: the router's DSL light was off and a reboot did nothing. Another technician had already been out with no result and suggested switching providers. This one took over three weeks to close — not because the router was broken, but because the fault was on the DSL line itself, somewhere between the estate's node and the home. That kind of fault can only be fixed by the provider arranging an NBN technician, so most of the work was ruling out everything on-site and then pushing the provider to dispatch.

Where the fault was: on the line to the home, not the gear

Fault location · along the chain

Estate node

→

Line to premises

No sync

Line fault

→

Wall DSL socket

→

Router

→

Your device

No net

The router, its power and the wall socket all checked out on-site. The DSL simply never synced, because the line between the estate's node and the premises was faulty — nothing inside the home can repair that; the provider has to send an NBN technician.

When the DSL light stays off no matter what you plug in, the problem is usually upstream of the home. We still verify everything reachable first — a swap router, known-good cables, and each wall socket — so that when we tell the provider “it's the line,” there's nothing left to argue about. The catch is that no one inside the home can access the estate's pit or the node; only the internet provider can raise an NBN job to send a technician out.

How it played out — a 20-day timeline

From the outage to reconnection

The connection dropped: DSL light off, reboot did nothing

DSL light off

First visit: tested other routers, cables and the wall port

Router & socket ruled out

Called the provider; a remote test reported no node fault, so no visit

Remote test: no dispatch

Second visit: re-checked the DSL socket and line, still no sync

Line fault confirmed

Supported a switch to Superloop, then chased the NBN booking

Switched to Superloop

Four follow-up calls over several days to book a technician

Booked via 4 calls (19/9/22/15 min)

NBN technician repaired the line from the node to the home

Restored — DSL back online

The timeline is long, but the logic is simple: prove it's the line, switch to a provider that will act, and keep chasing the booking until a technician is on-site.

Two on-site visits ruled out the router, cables and every wall socket.
A provider remote test can report “no fault” and still leave a real line fault unbooked.
Only the provider can raise an NBN job; persistence on the phone is what moved it.
The NBN technician fixed the node-to-home line and the DSL synced straight away.

What we can fix on-site vs what needs the provider

On-site fix vs provider/NBN job

	Fix on-site (same visit)	Needs the provider / NBN
Example fault	Dead router, wrong config, WiFi name/password, wrong wall port, faulty cable	DSL never syncs — line fault between the node and the premises
Who can act	Us, on the same visit	Only the ISP can raise an NBN technician job
Typical time	Same visit	Days: remote test → booking → visit
What moves it	Swap-test with known-good gear	Persistent follow-up; a provider that will dispatch

If a reboot and a swap router don't bring the DSL light back, stop buying new gear — it points to the line.

On-site faults (router, config, sockets, cables) we fix the same visit.
A dead line between the node and the home needs the provider to send NBN; no in-home fix reaches it.
Switching to a provider that will actually dispatch, plus persistent follow-up, is what closes it.

Result

Root cause: a DSL line fault between the estate's node and the premises — not the router, and not something any in-home fix could reach. After ruling out the gear on-site, switching to Superloop and chasing an NBN visit across four calls, the technician repaired the line, the DSL light came back, and the connection was restored after 20-plus days.

Why there's no internet & how to recover What is FTTN / DSL Telstra guide Superloop guide Sydney CBD service area

20 Days Without Internet: a DSL Line Fault Between the Node and the Home, Not the Router (Sydney City)

Where the fault was: on the line to the home, not the gear

How it played out — a 20-day timeline

What we can fix on-site vs what needs the provider

Related

Facing something similar?