Case Studies / Latest Case

Superloop Gigabit and an ASUS ROG Router Stuck on a DHCP Error: a Full Reset and a Patient Wait Fixed It (Glebe)

Move-in · GlebeSuperloop 1000M · NBNASUS ROG gaming routerDHCP configuration errorOrder held → active in ~10 minWired 1000M · WiFi ~900M

A friend moving into Glebe signed up for a Superloop gigabit (1000Mbps) plan the day before — we walked them through the online signup. The next morning the order sat on “hold”; one call to Superloop and about ten minutes later the activation SMS and email arrived. Then the real puzzle: their high-end ASUS ROG gaming router refused to get online, showing a “contact your ISP — DHCP configuration error” for so long we briefly suspected the router could not be used at all. It could. It just needed a full reset, a power-off pause — and five patient minutes.

From held order to gigabit · step by step

Order stuck on hold → called Superloop

Active SMS + email ~10 min later

Configured the ASUS ROG (WAN set to DHCP)

“Contact ISP: DHCP error” — for a long time

Swapped in a TP-Link test router

Online in minutes → ISP ruled out

Full reset, power off, reconfigure … and wait

~5 min later: IP acquired, online

Speed tests across the apartment

Wired ~1000M · WiFi ~900M in both rooms

One variable at a time: was it Superloop or the router?

Same line, two routers · the comparison that settled it

	ASUS ROG (first attempt)	TP-Link (test unit)
Result	DHCP config error, no internet	Online within minutes
What it proves	The line and Superloop were fine — the problem was the ASUS router’s own state, not incompatibility.
After a full reset	Got an IP after a ~5-minute wait, then ran at full speed	—

Why the wait mattered:

After a factory reset, a router can take several minutes to negotiate DHCP with the network. The worst move is to keep re-entering settings and rebooting mid-wait — you reset the clock every time.
The sequence that worked here: full reset → power off and let it sit → reconfigure the WAN as DHCP → leave it alone for five minutes.
Nothing about the final configuration was different from the first attempt — the fix was the reset plus the patience.

What the speeds looked like in the end

Final speed tests · wired vs WiFi

Wired

~1000 Mbps

WiFi (2 rooms)

~900 Mbps

~900Mbps over WiFi in both the living room and the bedroom, with the router sitting in the bedroom — no band-splitting needed.

A flagship gaming router earning its keep: wired tests went straight to gigabit, and WiFi held around 900 Mbps in both rooms even with the router tucked in the bedroom. Side by side with the budget test unit, page loads and speed tests felt noticeably snappier. On a gigabit plan, the router is usually the difference between paying for 1000M and actually feeling it.

Result

Root cause: stale state on the ASUS ROG — not Superloop, and not incompatibility. The TP-Link comparison cleared the line in minutes; a full reset, a power-off pause and a five-minute DHCP wait brought the ASUS online. Wired ~1000 Mbps, WiFi ~900 Mbps in both rooms.

Superloop guide ASUS routers Glebe service area How much speed for gaming TP-Link routers

Superloop Gigabit and an ASUS ROG Router Stuck on a DHCP Error: a Full Reset and a Patient Wait Fixed It (Glebe)

One variable at a time: was it Superloop or the router?

What the speeds looked like in the end

Related

Facing something similar?