Six categories of work we handle every week, each shown with a real, anonymised example.
During a roughly 30-minute on-site use test, the restart and screen failures did not recur.
Read the full case →A migration and its gaming outcome were not recorded; this case ends with a tested diagnosis and a proposed next step.
Read the full case →The subtenant could use internet on move-in day; the record does not give an independent throughput measurement.
Read the full case →The household gained WiFi and an on-site speed test reached about 900 Mbps.
Read the full case →Internet access worked and a later WiFi download test exceeded 450 Mbps against the 500 Mbps plan.
Read the full case →Wireless testing later reached about 430 Mbps and wired testing approached the plan speed.
Read the full case →Both local and overseas pages loaded after the provider action, and the record reports a 1000 Mbps speed test.
Read the full case →The PC returned to use; the reported room-network test rose from about 20 Mbps to above 90 Mbps.
Read the full case →The test router connected immediately; the requested WiFi name and password were set and the connection was checked after restart.
Read the full case →A local WiFi test reached about 50 Mbps after relocation, versus only a few Mbps reported earlier; no fixed-line migration was completed.
Read the full case →The wired computer test rose from about 20 mbps to above 900 mbps, restoring the expected high-speed path for gaming.
Read the full case →The operating system and drivers were installed in about 30 minutes and the computer returned to a usable boot state.
Read the full case →The reported deployment covered both floors, and tests could approach the gigabit service rate in the completed layout.
Read the full case →About 100 gb of playable high-definition footage was recovered with the original reported frame-rate and file-size characteristics.
Read the full case →Internet service returned after about 40 minutes of guided carrier coordination, and the customer also obtained an adjustment for the outage period.
Read the full case →The case was escalated as a premises-to-building line fault and a technician appointment was arranged.
Read the full case →The broadband move and activation were completed after about 100 minutes of carrier-call time across the changing request.
Read the full case →The service activated in under an hour and on-site wi-fi testing later reached the plan's 500 mbps rate.
Read the full case →One resident used a different provider successfully and another confirmed that both alternative providers and higher-speed plans were available.
Read the full case →The fault domain was narrowed to the provider line, avoiding more time spent rechecking or replacing the router.
Read the full case →The activation email arrived roughly five hours after the corrected order was created.
Read the full case →The wired test exceeded 900 mbps on the 1 gbps plan and the requested wi-fi name and password were set during a 20-minute visit.
Read the full case →The secondary-router path could reach gigabit link speed with the replacement lead, and the two wi-fi bands were made explicit for more deliberate device selection.
Read the full case →The cause of the delay was identified and the activation path became clear: install the optical box first, then complete the retail service activation.
Read the full case →Speed reached close to 500 mbps, 4k playback became smooth, and the earlier game-latency rise during television use was no longer observed.
Read the full case →The phone over wi-fi and desktop over Ethernet both measured about 500 mbps, while reported game latency fell from 40 ms to 18 ms.
Read the full case →Four mesh units in a three-storey home plus basement were unstable on wireless backhaul despite extensive built-in cabling.
Read the full case →A resident paid for months of fixed broadband at the wrong unit while the router quietly used its mobile backup connection.
Read the full case →A gifted desktop stopped being usable after system software was deleted, so a clean Windows installation was completed on site.
Read the full case →A gigabit fibre connection underperformed on one desktop because of its wireless adapter and a faulty nearby wall port.
Read the full case →A new router on an FTTB service showed no internet light because its cabling and internet configuration were incomplete.
Read the full case →A long five-bedroom home without internal Ethernet used a wireless mesh design, with extra attention to the gaming room.
Read the full case →A bedroom far from the main DSL router gained its own wired access point when wireless reach could not meet the resident’s needs.
Read the full case →A router repeatedly vanished from the WiFi list because a locally sourced power adapter delivered less voltage and current than required.
Read the full case →A city apartment’s fibre service was ordered, escalated for activation and configured on site with a gigabit plan.
Read the full case →A new FTTP service allowed only one device online because the router had not been configured to perform its routing role.
Read the full case →A new arrival received help from provider selection through activation and an on-site router installation on an HFC service.
Read the full case →A gigabit upgrade initially remained at 25 Mbps. Direct modem testing separated the active service from delayed router behaviour.
Read the full case →An unreadable camera card prompted format warnings after an interrupted copy. Imaging first allowed recovery attempts without working directly on the original media.
Read the full case →A student accommodation Ethernet outlet could not feed a newly purchased cable-modem router because the device expected coaxial input.
Read the full case →A café depended on a heavily loaded secondary router with undocumented settings. Network roles were reassigned carefully around live trading.
Read the full case →A remote router replacement failed because the DSL service was connected with the wrong cable path.
Read the full case →A moved broadband service appeared dead at the visible outlet, but another wall port hidden behind furniture was the active path.
Read the full case →An active fibre service remained unusable for a week because a new router was left in an incompatible operating mode.
Read the full case →A dark DSL light was traced to an intermittent wall connection; after service returned, the customer router also restarted repeatedly.
Read the full case →A desktop on a gigabit plan downloaded slowly because its wireless adapter chose the combined network’s 2.4 GHz band.
Read the full case →Whole-home WiFi in a 400sqm house, four hours of business IT support across ~50 desks, two student call-outs, and a week-old connection fault fixed in 20 minutes — 15.5 hours in one day.
Read the full case →Some devices appeared online through an upstream network while a Mac failed because the router mode and manual IP settings were wrong.
Read the full case →A newly activated service broadcast WiFi but could not reach the internet until the router received the provider PPPoE details.
Read the full case →Three unrelated routers were replaced by one routed network with two wired mesh nodes across a large two-storey home.
Read the full case →Two broadband bills were investigated and one service was found to have been activated at a different address.
Read the full case →Two gamers replaced an unstable 5G home service with fixed broadband, a WiFi 7 router and wired desktop links.
Read the full case →A miswired modem-router chain let only one device use the provider connection. Correct cabling plus an ISP reset restored routed access.
Read the full case →A DSL-connected home lost internet when its provider router stopped showing status lights. A known-good router restored the connection while a replacement was arranged.
Read the full case →A second-hand router kept losing its wireless network. Substitution testing separated a hardware fault from an upstream broadband problem.
Read the full case →Planning started before the move. The ABB service and eero were configured, tests in several rooms reached the 100 Mbps plan rate, and the bedroom and TV Ethernet paths were checked for plug-in use after move-in.
Read the full case →A previous support session had pointed toward the building line. Remote checks found a live link on the first wall port, then the TP-Link was set to automatic IP and the connection came online after a short wait.
Read the full case →The old tenant’s router worked before the ISP switch, then no wall socket produced DSL sync. On-site testing narrowed the fault to the building side; a qualified worker with comms-room access restored the line.
Read the full case →An ABB gigabit account showed zero traffic for almost three months because the router still dialled a former tenant’s Harbour service. Correct DHCP settings and a Huawei WiFi 7 router lifted the test from 44 Mbps to 1.1 Gbps.
Read the full case →The plan was active, Opticomm had already upgraded the premises off the old DSL wiring, and the crew had pointed at the socket that now worked — nobody had configured a router, because that is not in anyone's contract. We proved the socket was live with a router we knew was good, then found the customer's new D-Link would not accept the admin credentials printed on its own base, before or after a factory reset. It went back for a refund; the TP-Link already in the flat took the settings and reached the plan's speed.
Read the full case →The line was fine, the wall socket was fine and the tenant’s own Redmi router was fine — and nothing would connect, because the service runs PPPoE and the username and password had been issued to a flatmate two tenants earlier, whose router had left the flat with him. We established on site that the fault was informational rather than physical, then worked back through the former flatmates until the original account holder found the activation email.
Read the full case →Nothing in this flat was broken. The previous tenant had simply taken the ONT’s power lead, plus the router’s power lead and network cable, and the broadband had not been ordered yet either. The customer had already tried several shops without finding a matching adapter. We walked them through the ABB order, which came through in under ten minutes, checked one of our own adapters matched on output and brought it over that afternoon — and the better of their two routers reached the full 100 Mbps over 5 GHz.
Read the full case →The building supplied the internet through a captive portal: every device had to open a web page and enter a code first. A games console has no way to display or fill in that page, so it simply never got online — and only one of the room’s two wall ports worked, testing at 100 Mbps. A switch cannot help because it signs in to nothing. We set up an OpenWRT router to complete the portal login itself and share the connection over both WiFi and its LAN ports.
Read the full case →A university teacher who had just moved from Hong Kong to a Sydney university could not open a web page on her laptop — not on hotel WiFi, not on the campus network, not on her own phone hotspot — while one messaging app still received messages normally. Three unrelated networks with one thing in common settles the question of where the fault is. Over a video session the obvious checks all came back clean, and the problem turned out to be leftover network configuration on the machine itself.
Read the full case →A UNSW postgraduate who had just moved into Chippendale wanted the hardest version of this job: apply on his behalf, activate the same day, install that night. The application went in early and an FTTP service can come up in hours — then the comms cupboard opened. The previous tenant had ripped the Huawei ONT off the wall and every cable, the fibre lead included, was loose on the floor. A snapped pigtail means waiting for a splice, so the seconds after powering the ONT back up were the tense part of the evening.
Read the full case →From the wall port, a dead router and a dead line look identical — the DSL light simply never comes on. On the first visit the only units in the flat were second-hand: a TP-Link with no DSL modem at all, and a DSL-capable Telstra unit of unknown condition that got no sync on any wall port. That proved nothing. We returned the next morning with a known-good DSL router, tested every port again, still got no sync, and called Exetel from the flat to book a free NBN technician for Thursday morning.
Read the full case →The link light came on the moment the cable went in, which is exactly why this one was confusing: a lit port proves the cable and the sockets and nothing more. Our test device worked on the same cable and port, so the fault was inside the desktop — a network adapter with no working driver after the system had been reset the day before. We installed the driver, reset the router when the connection kept dropping straight after connecting, and turned a spare TP-Link into a wired second router in the bedroom in place of a wireless extender.
Read the full case →Not every job involves a router. This customer's broadband worked fine — they just wanted it to stop, and TPG was not stopping it. They had already tried calling and emailing themselves with no result either way. We made the call on their behalf: account details first, one transfer from the intake agent to the team that handles cancellations, an identity check, then a short wait while it was processed. The agent confirmed the plan was cancelled that day, effective immediately.
Read the full case →The network name did not just stop working — it vanished from the list, most reliably the moment a download started. The ASUS RT-AX59U was near new, its admin settings were normal and the customer had already reset it, which is exactly why this class of fault gets blamed on the provider. We waited on site until the fault reproduced, then swapped a test router onto the same Opticomm line; the provider reset the connection remotely so the new unit could come online, and the dropouts did not return.
Read the full case →Two symptoms arrived together: websites would not load, and the NETGEAR router's own admin page reported no network connection. We ran it as a remote video session — confirmed the Superloop account and the line first, then reproduced the fault on a second device to prove it was every device rather than one misconfigured laptop. That single check is what decides whether you touch the router at all. Reset, power-cycle with the modem, reconfigure, and the internet indicator came back within seconds.
Read the full case →A USYD student lived in the loft upstairs while the router sat downstairs on an Occom 100 Mbps DSL connection; phone tests up there came back at 20-30 Mbps and gaming on a tablet was unstable. Buying a faster DSL router would have changed nothing — the line caps at 100 Mbps either way. So the old TP-Link stayed downstairs doing the connection, a 10 m cable carried it up to an eero Pro 6E in the loft, and phone, tablet and desktop all came back at close to the full plan speed.
Read the full case →A UNSW student in Waterloo pre-booked the Superloop activation date about two weeks before moving in, so the 100 Mbps DSL line was live on day one and tested fine the evening we installed the router. Then a pattern started: at fairly regular intervals phones would drop off the WiFi to mobile data for a few seconds, then come back — while the WiFi indicator on the Netcomm router stayed lit the whole time. A lit light is not proof the network name is still being broadcast, and that gap is the whole case. An A/B swap to a TP-Link on the same wall connection ended the dropouts.
Read the full case →It read like a simple speed complaint: a Telstra 1000 Mbps fibre plan testing under 200 Mbps over WiFi right beside the router and under 100 Mbps on a cable. It took an 80-minute remote video session, because the house was wired end to end through two switches and dozens of cables. Two of them were the problem — the run to the router was printed CAT5E, and the switch-to-switch cable was printed CAT7, looked perfect and still measured under spec. Both went to CAT6 and the speeds came up to what the plan should deliver.
Read the full case →An honest write-up of a job we did not solve. A student in Sydney city had months of working internet, then woke up one morning to no connection and a DSL light that would not come on, with nothing changed in the flat. Over two site visits and two calls made on the student’s behalf we swapped in our own known-good router and phone cable — the light stayed dark. Telstra reported their side healthy, NBN reported theirs healthy, and Telstra would not dispatch anyone. Re-seating the wall connection got the light flashing once every few minutes but never solid, which points squarely at the run between the building comms room and the flat — and the building manager would only admit credentialed provider staff to that room.
Read the full case →A student messaged in the morning about getting internet sorted for a move. We matched a provider and plan to the address and the budget, the Superloop 100 Mbps service was ordered, the activation email came through quickly, and we attended that same afternoon with a TP-Link router in hand. The service obtains its address automatically, so there were no dial-up credentials to enter — connect, set the WiFi name and password, test on the student’s own devices. The case breaks down the four things that have to line up for a same-day result, and why the step that most often stalls a move is waiting for a router to arrive in the post.
Read the full case →Students in Sydney, France and the Netherlands keep sending the same message: the WiFi that comes with the accommodation is unstable, and in Sydney the complaint is ping spikes and lag while gaming. Shared building WiFi fails in the last few metres — a corridor access point shared by the whole floor, with your walls in between — which is why a speed test can look acceptable while a game still feels terrible. There are only three ways out, worth trying in order: check whether your exact address can take its own connection, test whether the wall Ethernet port is live and wire into it, or repeat the building WiFi with a router that supports repeater mode. In one Sydney dorm we deployed that third option on an ASUS router and the student reported the experience improved.
Read the full case →A student living near Central Park in Chippendale was on a Superloop 1000 Mbps fibre plan, running it through a Telstra router he already had. One week the router’s lights simply stopped coming on and the WiFi went with them. “No lights” on its own does not tell you whether the router died or the line did, so we brought a spare router along, connected it to the same line and watched the WAN side carry signal normally — which isolated the fault to the hardware. The broadband account details went across to a TP-Link router, the two bands were split into separate networks at his request, and we speed-tested against the plan before leaving.
Read the full case →Nothing was faulty. An incoming undergraduate moving into Zetland had a Superloop 50 Mbps plan booked by a third party to activate on 2 June, because he had been told that starting on 31 May would cost him an extra month — so he accepted being offline on move-in day. We called Superloop with him and asked for immediate activation; the confirmation arrived about ten minutes after the call ended. The ASUS router was then set up over video with the Opticomm dial-up details, and his bedroom laptop was wired for gaming and tested at plan speed. With a link diagram, a remote-support timeline and a table on who can actually move your activation date.
Read the full case →A student in Brisbane collected a Telstra router on the day his service was connected, got online, then renamed the WiFi. The router’s admin page reported the change as saved and kept showing the new name — but every phone in the flat still saw the old network, and that network had no password on it. A power cycle changed nothing in either direction, which is the detail that matters: the settings were stored but the wireless hardware never applied them, so this was not a mistake in his steps. Handled entirely over messages; a manual factory reset and a clean reconfiguration made the new name appear.
Read the full case →Frequent dropouts whenever several devices were connected, in a house running two identical ASUS routers on an NBN 250 Mbps plan with PPPoE. Diagnosing them one at a time found faults in both — a band split the admin page accepted but the hardware never applied, and a LAN port cycling in and out of recognition. The socket the router plugged into was loose and briefly cut power to the NBN box beside it, in a house that had already lost an NBN device to lightning. With a power-path diagram and an apartment-vs-house table.
Read the full case →The ONT failed overnight and by morning showed only its power light. A new power adapter brought every light back to normal — and then the provider-supplied ZTE router would not connect. A known-good router got online immediately, isolating the fault to the ZTE. Support had asked for the PPPoE dial-up settings to be reconfigured, but that option does not exist in this unit’s admin page: it is a deeply customised carrier build. With a two-fault link diagram and a locked-vs-unlocked router table.
Read the full case →Phones and tablets joined the WiFi normally while the desktop spun and never joined. The flat ran two routers — a main unit doing the DSL dial-up and a second ASUS on its WAN port serving as the everyday WiFi. That arrangement is common, but the second unit had not been configured for the role, so address allocation failed for the desktop. We reset it, moved it into his bedroom to use its gaming LAN port for a wired connection, and restored the original network name. With a link diagram and a phone-vs-desktop symptom table.
Read the full case →A lower north shore house with a direct view of the Harbour Bridge and the Opera House, three ensuite bedrooms, and the WiFi problem every home of this type has: solid double-brick walls with heavy sound insulation block signal severely, no network cabling was ever run, and drilling the finishes was not an option. With no route for a wired backhaul we used Deco mesh nodes on a dedicated backhaul band, placed along the hallway to avoid the thickest load-bearing walls. Roaming verified on video calls and 4K streaming.
Read the full case →Four housemates, four gaming desktops, and a Netcomm router with exactly four LAN ports, all in use. The student who called was in the furthest room, where the wireless was bad enough that short videos stuttered, and he wanted a wired port at his desk. He also mentioned game downloads never passed about 100 Mbps on a gigabit plan. Two problems, one visit: a router added in his bedroom for a wired port plus close-range WiFi, then a hardware swap that took the wired desktops from about 100 to around 900 Mbps.
Read the full case →A two-storey share house near UNSW with seven bedrooms, a Telstra 100 Mbps plan over a DSL phone line, a Telstra router upstairs and a Telstra Smart WiFi Booster downstairs sharing one network name. It looked like a dead router and took three visits. Replacement router one would not mesh with the Telstra booster; a NETGEAR mesh pair gave WiFi with no internet within half an hour; a TP-Link main with the NETGEAR as an extender on deliberately separate names finally held. With an attempt-by-attempt comparison table.
Read the full case →A student in Auburn had just activated an Occom fibre plan and could not work out how to drive the router at all. Two things made it unusual: the router was an AmpliFi, a brand and interface I had not met on a job here, and the plan was 25 Mbps — the slowest I have been called out to. Handled remotely over video with no spare computer on site, and the unit expected two mesh nodes that were not there. Resetting it, driving it through the official app and entering the PPPoE details brought it online at plan speed.
Read the full case →A three-storey detached house running five TP-Link Deco nodes, a five-port switch and more than twenty connected devices — cameras, smart home gear and sensors as well as phones and laptops. The mesh had failed and the owner had already deleted it from the app, so there was nothing left to repair, only to rebuild. The owner also wanted the provider-supplied router retired. Five hours on site: reading the existing cabling first, migrating the primary network onto Deco, then resetting and re-adding four nodes floor by floor.
Read the full case →Two ASUS routers, different models but both mesh-capable, and still weak bedroom WiFi. The building runs on Redtrain fibre infrastructure with Occom as the provider. The line arrives in the bedroom but the main router had been carried to the living room through the flat’s only wall port, leaving no cable path for a wired backhaul. We swapped the roles instead of buying hardware. With a before/after topology table and on-site timeline.
Read the full case →The 50Mbps fibre plan had been active for a long time with still no internet. A DSL cable on a fibre service, two routers behind the modem at once, and settings changed across many attempts. We confirmed the connection type from her own Superloop account, stripped everything back to modem LAN1 into one known-good router on PPPoE, then had support refresh the service. With a before/after cabling table and timeline.
Read the full case →A newly activated Superloop plan that would not stay online with an ASUS router. We corrected a genuine connection-type error on the router and it briefly reported success — then dropped within seconds. The give-away was the Huawei ONT: PON, LAN and status lights all flashing abnormally, unchanged by a reset or a power cycle. We reproduced the failure live for the provider and an Opticomm visit was booked. With a link diagram and router-side vs line-side table.
Read the full case →Not slow WiFi, not dropouts — there was no network name in the list to tap at all. Handled entirely over messages: a factory reset brought the router’s label SSID back, and then a second, separate fault surfaced. The cable was in wall port UID1 while the provider’s activation email specified UID2, so the port light stayed dark. With a stacked-fault link diagram and a table of why an SSID disappears.
Read the full case →An order submitted in early April was still not activated weeks later. On the call the Superloop agent could not detect any equipment at the address and asked about an Opticomm box. We tested every wall port while on the line, moved the router to the one live port, and the account was activated on the spot. With a blocking-step chain diagram and full call timeline.
Read the full case →A Margaret St apartment was already serviced by Gigafy and the in-room router belonged to the provider. We read through their sign-up process, called their support line, then guided the student over video: connect to the in-room router's WiFi, choose a plan, pay, and the line went live immediately. No technician visit. With an activation chain diagram and timeline.
Read the full case →A graduating student wanted their Superloop service to stop when the current billing cycle ended in mid-June, not roll into another period. Details taken at 14:48, Superloop called on their behalf at 15:03, confirmation email at 15:13. With an on-site timeline and a what-usually-happens comparison table.
Read the full case →Total loss of internet on a Telstra DSL service near Chinatown: no front panel lights at all, only a faint glow at the back, unchanged by repeated power cycles. Our own TP-Link on the same wall socket synced and the 25 Mbps service came back in the same visit. With a link diagram, on-site timeline and a dead-unit vs needs-a-restart table.
Read the full case →A gaming room three walls from the router lagged badly at night. A straight cable wasn’t practical, so a wireless repeater plus a short LAN run to the PC held in-game LOL ping stable under 20 ms. With a signal-path diagram, before/after table and on-site timeline.
Read the full case →Activated and installed, but the DSL light only flickered. After ruling out our own gear, the fault was upstream: the line wasn’t linked through the building’s comms room to the room’s DSL port. An NBN tech fixed it free the next morning. With a line-fault diagram and free-vs-paid-visit table.
Read the full case →On an Aussie Broadband gigabit plan (eero), the living-room desktop’s best WiFi was ~300 Mbps; wired to a live wall port it reached ~900 Mbps — about 3x faster and far steadier, no plan change. With before/after speed bar, wired-vs-WiFi table and timeline.
Read the full case →A new NETGEAR Nighthawk stayed offline despite a factory reset. The account and line were fine — the router simply won’t let you configure the connection until you set a device admin password first. Then the PPPoE login brought it online at the full 100 Mbps. With timeline and a reset-vs-configured table.
Read the full case →An Optus 1000M line dropped at random, with the router’s Internet and WiFi lights going dark. We show how to tell “no WiFi name” from “WiFi but no internet”, simplify the cabling, restart clean (wired hit full 1000 Mbps) and wire the desktop. With timeline and diagnosis table.
Read the full case →The account was active, but the TP-Link router stayed on “connecting”. We ruled out the router, then found the feed was in the DSL port when this Superloop/Opticomm service needed Ethernet in the WAN port — a mix-up even the installer made. Moving it brought 100 Mbps online at once. With timeline and DSL-vs-WAN table.
Read the full case →A new-home install on an Aussie Broadband gigabit plan in Mascot tested at only ~100 Mbps. The cap wasn’t ABB — it was an old 100M Ethernet cable already run in the room. Swapping to a gigabit cable restored ~1000 Mbps wired, with the desktop and TV connected. With before/after speed, bottleneck-chain and install-timeline diagrams.
Read the full case →A Sydney City DSL connection stayed dead for 20+ days — the router’s DSL light never came back. Two on-site visits ruled out the router and wall sockets; the fault was on the line between the node and the home. After switching to Superloop and four calls to book an NBN technician, the line was repaired. With a full timeline, fault-location diagram and an on-site-vs-provider table.
Read the full case →A Sydney Superloop user’s Xiaomi router worked on one uplink cable, but a second cable run to a wall socket dropped the whole connection. Its four ports auto-detect WAN/LAN, so the extra cable was misread and the uplink was lost. Fixed over a remote session by changing the port/socket combo and power-cycling — WiFi and the wired living-room port both live. With topology, remote timeline and an auto-sensing vs fixed-port table.
Read the full case →A Sydney student on Origin 250M had plugged their eero’s WAN cable into a random living-room socket and got nothing. Over an 18-minute video call we found the real NBN box tucked in a bedroom wardrobe — never powered on. Powered and wired correctly, the Origin-provisioned eero tested the full ~250 Mbps across the flat. With an inlet-locator diagram, remote timeline and a wall-socket vs NBN-box table.
Read the full case →A Zetland student brought a Redmi router from China and bought a TP-Link on Amazon, and neither could connect — the flat runs on a DSL phone line and both were plain wireless routers with no DSL modem inside. He had already switched from Occom to Superloop blaming the provider. One call got the account activated in ten minutes; that evening a DSL modem-router plus two support calls brought the line up, and the bedroom wall port was wired through. With link diagram, on-site timeline and a router comparison table.
Read the full case →Six housemates on a Dodo 250Mbps fibre plan had constant dropouts, devices that would not join and slow tests — and had already tried every online tip including changing DNS. Link-by-link testing ruled out the line, the cabling, the provider and the main router; the second router was still in router mode dialling PPPoE with its uplink in a LAN port. Reconfigured and re-cabled, and a follow-up an hour later found no recurrence. With fault-chain diagram, on-site timeline and a router-mode comparison table.
Read the full case →A Sydney CBD student on Occom wanted the gaming desktop off WiFi. Two spare cables matched the living-room wall port to the router, and a five-minute live test held ~5 ms ping. Same afternoon, another flat: three dead sockets on two routers meant dead in-wall cabling — one for the ISP technician. With timeline, WiFi-vs-wired table and fault-chain diagram.
Read the full case →Every device joined WiFi but only one could reach the internet — it had grabbed the provider’s single address directly. On-site we found a dead NBN cable in the Nokia’s WAN port and the live Opticomm line in a LAN port. Two cables re-seated brought the flat back; the new ASUS went in as a wired AP. With fault chain, two-visit timeline and WAN-vs-LAN table.
Read the full case →Two cases where the router and cabling were fine. One student’s Optus 250Mbps HFC plan had never been activated — the router was quietly running on its built-in SIM backup at ~30 Mbps. Another’s TPG PPPoE dialled in with a real IP but still loaded nothing. With bottleneck chain, comparison table and diagnostic timeline.
Read the full case →A returning client’s ASUS router came back with a red indicator after the power cable was knocked out — devices joined the WiFi but nothing loaded. Most routers recover a line on their own; this one needed a reset plus a remote refresh from Telstra. With link diagram, comparison table and on-site timeline.
Read the full case →Booked two weeks before flying to Sydney, online on landing day. The student’s own multi-LAN gaming router went onto the building’s HFC NBN box — a little less stable than fibre, but tested ~900 Mbps, gaming-ready from night one. With visit timeline and connection-chain diagram.
Read the full case →The admin page said saved, but nothing changed — even hiding the SSID and full resets were ignored. We switched the faulty Telstra unit’s WiFi off with the physical button and wired the student’s own router behind it as an AP: their WiFi name and password, live the same visit. With timeline and option-comparison table.
Read the full case →Two technician visits found nothing wrong — because the Opticomm line was fine. The Telstra router had failed over to its backup SIM, so every test measured the mobile fallback. Back on the fixed line: ~250 Mbps wired and on WiFi, lag-free gaming. With a timeline and a fixed-line vs backup-SIM table.
Read the full case →The order sat on hold — one call, active in ~10 minutes. Then the flagship ASUS ROG kept showing a DHCP configuration error. A TP-Link test unit cleared the ISP in minutes; a full reset plus a five-minute DHCP wait brought the ASUS online: wired ~1000M, WiFi ~900M in both rooms. With timeline and comparison table.
Read the full case →We activated this student's Superloop plan in February; in May they moved out and we called to cancel. The rep explained the terms on this account: 30-day notice, billed to the end, connection still working. With a call timeline and a cancel-vs-address-change table.
Read the full case →A Zetland student's Telstra router went completely dark — roughly the fifth identical dead unit in two weeks. We confirmed the hardware failure, swapped in a TP-Link that hit the 100M plan speed, and cloned the old SSID so every device reconnected itself.
Read the full case →A Zetland student on Telstra 100M DSL lost all WiFi. Our DSL router got online on the same socket in minutes — the line was fine; the Telstra gateway was stuck in a reboot loop. With an on-site timeline and a line-vs-router diagram.
Read the full case →Late-night outage near Chinatown: a Telstra gateway on Aussie Broadband 50M DSL had died, and a China-bought Xiaomi had no DSL port to take over. We arrived at 11pm, proved the line was fine and had them back online the same night.
Read the full case →A Superloop 1000M plan tested at only ~100 Mbps. Link-by-link we found a second-hand router with a 100M Fast Ethernet LAN port — not the provider. A gigabit router restored ~920 Mbps wired (9×). With visual speed & bottleneck diagrams.
Read the full case →Two fibre (FTTP) students: one on Occom kept dropping out at night mid-game, one on Aussie Broadband was paying more for less. We showed both how to confirm fibre, that they aren't locked to one provider, and why a Superloop 1000Mbps plan is better value.
Read the full case →A Zetland student on Exetel 100Mbps DSL couldn't get online with a ZTE router. Over video we found it was in the wrong wall socket — the smaller phone/DSL port (RJ11) vs the wider Ethernet port. Here's how to tell them apart.
Read the full case →A UTS student's Superloop read "active" but had no internet; a second-hand eero 6 wouldn't help. We arrived within 30 minutes in heavy rain and traced it to an Opticomm line a technician never provisioned — escalation in progress.
Read the full case →A referred UTS student's new apartment: we activated Superloop 1000M, booked the NBN visit, supplied a TP-Link WiFi 7 router and rewired every room from phone line to Ethernet.
Read the full case →A USYD gamer we'd helped for free planned his move around the network — we advised the house & provider, installed WiFi 7 and rewired 8 Ethernet runs for two bedrooms.
Read the full case →Found via Google: a shop PC joined WiFi but had no internet. We isolated it to the computer (not the network) with comparison testing and fixed it on-site in 20 minutes.
Read the full case →Occom showed activated, router was fine — but every wall socket tested dead. Line fault isolated in 30 minutes, NBN tech booked, router pre-configured for plug-and-go.
Read the full case →An FTTB-to-FTTP upgrade took down a multi-AP UniFi system: router misconfig + cabling errors + throttled channel width, all fixed in one visit.
Read the full case →Four brands of legacy gear, double NAT, and Sonos/B&O speakers that kept dropping — replaced with one pre-staged 4-node mesh.
Read the full case →Big houses in Sydney rarely have a coverage problem — they have a coherence problem: several routers bolted on over the years, each with its own WiFi …
Read the full case →A landmark harbour-view estate on Sydney's Lower North Shore: circular picture windows framing the bridge and Opera House, three full-harbour-view mas…
Read the full case →On-site is Sydney-only, but most network problems don't actually need a van in your driveway. Two interstate cases, both solved entirely through a pho…
Read the full case →Two weeks of travel vlogs on a DJI Pocket 3, an interrupted copy to the laptop, and suddenly the SD card wouldn't read at all — every device just offe…
Read the full case →A USYD postgrad's desktop dropped into a blue-screen loop with critical thesis files trapped inside. On-site next morning in Zetland: data backed up first, clean reinstall, drivers tuned — plus a WiFi fix from 20 to 90+ Mbps.…
Read the full case →A 1000M plan tested 900+ Mbps in the morning and under 100 by afternoon, nothing changed. Router and ISP both checked out — the culprit was an in-wall port negotiating an unstable link rate.…
Read the full case →From move-in day to move-out day: setup, bills, gaming and everything in between.
A postgraduate student who did his undergrad in the US moved into a harbourside Barangaroo apartment (about $1,400/week). He was used to 2Gbps symmetr…
Read the full case →English call-centre queues, notice periods and billing fine print are where international students lose real money. Two typical cases we handled by ph…
Read the full case →Paying for gigabit-class fibre and still teleporting around the map? We see this weekly. One Sydney household on a 500Mbps plan was hitting 800ms in V…
Read the full case →Houses and apartments: coverage, mesh, upgrades that suddenly break everything.
Upgrading your plan or router and suddenly having no internet at all is one of the most common calls we get. The router usually gets the blame; it's u…
Read the full case →Big houses in Sydney rarely have a coverage problem — they have a coherence problem: several routers bolted on over the years, each with its own WiFi …
Read the full case →A landmark harbour-view estate on Sydney's Lower North Shore: circular picture windows framing the bridge and Opera House, three full-harbour-view mas…
Read the full case →Offices, hostels and fleets: procurement, LAN builds, upgrades and rescue calls.
A business client we served last year referred their contact: another company had just relocated its whole office and everything IT was, in their word…
Read the full case →The same relocation client's second problem: a fleet of older Windows machines that had grown slow, inconsistent and occasionally alarming. No two com…
Read the full case →A CBD hostel owner called after two days of guest complaints: WiFi worked near the front desk, but on every other floor the access points glowed red. …
Read the full case →Plain-language explainers so customers understand what they're paying for before we even visit.
NBN is the government-funded national network; retailers like Telstra, Optus and TPG just resell access to it. Many newer apartment blocks instead run on Opticomm, a private fibre network with its own pricing, completely separate from NBN. Understanding this distinction upfront saves new arrivals real money and confusion.
Getting a brand-new connection live, tested, and actually fast — same day where possible.
A UNSW postgraduate near Waterloo (Sam Sing Street) needed internet fast. After a quick needs assessment — household size, devices, gaming/streaming habits — we submitted a 500Mbps Superloop plan and had it installed and speed-tested the same day.
Making an already-working connection actually reach every room.
A 50Mbps Telstra NBN line, a 10+ year old WiFi-4 repeater, and a strict no-visible-cabling rule (a wheelchair-using family member). We retired the old repeater and deployed a wired-backhaul TP-Link Deco X50 mesh — zero new visible cabling, full-strength WiFi upstairs in time for kickoff.
5GHz carries more data but travels a much shorter distance through obstacles than 2.4GHz. We explained the trade-off and reconfigured the setup — splitting bands and repositioning the router — for reliable coverage in that specific room.
When something that used to work suddenly doesn't, or never worked as advertised.
A UNSW student apartment in Zetland was contracted for a 450Mbps NBN plan but WiFi speed was capped around 200Mbps with an unstable connection. The cause: the wall-mounted UniFi access point had its Ethernet port disabled by the building's own network configuration, blocking a wired connection entirely. We diagnosed it on-site, bypassed the restricted building AP configuration, then supplied and installed a dedicated router with a wired Ethernet run to the PC — restoring a stable 450Mbps+ wired connection at the full contracted speed.
A Grandstand Parade apartment in Zetland had a 100Mbps Superloop/Opticomm FTTB plan testing at only 20Mbps from day one. We traced it to the ISP's incomplete technical provisioning and pushed for a fix until the connection reached full plan speed.
A Mascot household's WiFi worked perfectly on a Xiaomi router, but switched to nightly dropouts the moment they installed an imported high-end gaming router. The router's advanced radar-detection features were unusually sensitive to signals near the airport flight path — an unusual, hard-to-diagnose fault we traced through elimination.
From student laptops to serious hardware — diagnosed honestly, fixed properly.
A friend's high-end ASUS ROG GT6 AX10000 gaming router kept failing to get an IP address on a freshly activated Superloop 1000Mbps line. After ruling out an ISP-side fault (a loaner TP-Link connected instantly), a full reset and reconfiguration got it back online — wired speeds hit full gigabit, WiFi held 900Mbps+ throughout the apartment.
A desktop worth roughly AU$20,000 (RTX 4090, Ryzen 9, dual monitors) suddenly lost internet access, with volume, brightness and Bluetooth controls all greyed out. Diagnosis traced it to a ShellHost.exe stack-based buffer overflow — cleaned and restored over a five-hour session without wiping the customer's data.
Data first, reinstalling second — always in that order.
A USYD postgraduate's desktop was stuck in a blue-screen reboot loop with important research data on the drive. We backed up everything first, then rebuilt the system cleanly. As a bonus, we noticed the room was only getting 20Mbps on a much faster plan — optimised on the spot to 90Mbps+.
Sydney student network notes
Anonymised troubleshooting patterns for common move-in, WiFi and wired-network symptoms. They explain what to observe first, not a promise about a particular provider or address.
Official download route, the correct UOC-weighted formula, a privacy-aware AI prompt and clear limits—reviewed by a UNSW graduate.
MOVE-IN