A 100 Mbps FTTB plan stayed near 20 Mbps for weeks. A later test reached the subscribed 100 Mbps level after roughly 50 days of follow-up.
This anonymised case is based on source record 117. The starting point was: A Superloop FTTB connection in Zetland measured around 20 Mbps despite a 100 Mbps plan. The account below separates the report, the evidence that was actually available, the action recorded and the observed outcome. It omits the resident’s identity, full address, account details, credentials and any screenshot-only information. A result from one household or one remote session should not be mistaken for a universal setup instruction.
| Problem | Evidence |
|---|---|
| A Superloop FTTB connection in Zetland measured around 20 Mbps despite a 100 Mbps plan. | Repeated provider escalation and an on-site network visit preceded eventual upstream action; the local ASUS router alone was not shown to explain the limit. |
The diagnostic task was to separate the reported symptom from the carrier service, access equipment, router, indoor cable path and client device. The most useful comparison in this record was: Repeated provider escalation and an on-site network visit preceded eventual upstream action; the local ASUS router alone was not shown to explain the limit. That observation pointed the work toward a testable layer and reduced the value of repeatedly rebooting or replacing unrelated equipment. It did not rule out every other possible cause, because the source does not document tests that were never performed.
The recorded intervention was: The customer and technician tracked the case with Superloop until its access partner completed work. The order matters. Establish the current path and settings first, alter the part supported by the evidence, and then repeat a test matching the original complaint. If an upstream provider, account holder or later cabling visit was still needed, this article stops at the action actually recorded. A recommendation or appointment is not described as a completed repair.
The observable change was: A later test reached the subscribed 100 Mbps level after roughly 50 days of follow-up. This is the practical boundary of the result: it reports what happened under the conditions recorded at that time. It does not prove that every device, hour of the day or property would behave identically. For an intermittent fault, one successful test shows capability, while continued observation is needed to establish lasting stability.
A later test reached the subscribed 100 Mbps level after roughly 50 days of follow-up.
The case has an important limit: The source does not identify the exact upstream component fixed; a requested billing adjustment is not a confirmed refund. Before repeating a similar step, confirm the access type, device role and account state in your own home. If a change involves cancelling service, resetting a router, reinstalling a computer or attempting data recovery, preserve the information and backups needed to recover from an unsuccessful attempt.
A useful follow-up record includes the time, expected plan or service state, test device, whether the link was wired or wireless, and the result before and after the change. Keep one comparison condition stable where possible. That makes it easier to separate a local configuration problem from an upstream service problem and gives a provider or technician a reproducible starting point.
The reusable lesson is to advance from a verified observation to a proportionate action, then state what the retest does and does not establish. The source does not identify the exact upstream component fixed; a requested billing adjustment is not a confirmed refund. If the service remains unreliable, keep the evidence, escalate to the party responsible for that layer and label what is confirmed, what remains plausible and what is still unknown. Avoid turning a working hypothesis into an accusation or a guaranteed outcome.
Call or message us — 90% of messages get a reply within an hour.
Call 0420 119 140 Send a Message