Free tool. Private.

NBN fault log

Sample: this is what a fortnight looks like. Your own log starts empty.

Turn on JavaScript to keep your own log, or print the blank log sheet below.

  • Monday: 7 pm (1), 9 pm (1)
  • Tuesday: 8 pm (2)
  • Wednesday: 7 am (1), 6 pm (1)
  • Thursday: 6 pm (1), 9 pm (1)
  • Friday: 7 pm (2), 8 pm (1), 10 pm (1)
  • Saturday: 11 am (1)
  • Sunday: 1 pm (1)

Most of your dropouts are between 6 pm and 10 pm. 10 of 13 dropouts where you noted the weather were on days you marked as rain or wind.

NBN service fault: evidence log (sample)

Connection
Fibre to the curb
Plan
Home Fast (NBN 100)
NBN box
The box with a phone-style lead
Covers
Mon 12 Oct 2026 to Sun 25 Oct 2026
Prepared
Mon 26 Oct 2026

Summary

14 dropouts over 14 days (1 a day on average). Worst day: Fri 16 Oct 2026 (3). Most of your dropouts are between 6 pm and 10 pm. 10 of 13 dropouts where you noted the weather were on days you marked as rain or wind.

When it dropped out

  • Monday: 7 pm (1), 9 pm (1)
  • Tuesday: 8 pm (2)
  • Wednesday: 7 am (1), 6 pm (1)
  • Thursday: 6 pm (1), 9 pm (1)
  • Friday: 7 pm (2), 8 pm (1), 10 pm (1)
  • Saturday: 11 am (1)
  • Sunday: 1 pm (1)

Speed tests Plan: Home Fast (NBN 100)

On a cable, the median of 3 tests was 51 Mbps down, 18 Mbps up, 12 ms ping. On wifi, the median of 1 test was 22 Mbps down, 9 Mbps up, 31 ms ping.

WhenDownUpPingOnDeviceResult
Tue 13 Oct 2026, 8:30 pm461714CableLaptop on a cable at the modem
Thu 15 Oct 2026, 7:00 pm22931WifiPhone in the back bedroom
Tue 20 Oct 2026, 8:20 pm511812CableLaptop on a cable at the modemhttps://secureacom-nbn.speedtestcustom.com/result/5e3c1a72-0f4b-4d8e-9a61-2b7d0c9e4f13 (opens in a new tab)
Sun 25 Oct 2026, 10:10 am94199CableLaptop on a cable at the modemResult ID 1842-7731

Down and up in Mbps, ping in ms, as the test reported them.

Calls and visits

  1. Tue 13 Oct 2026 Provider, ref INC-204418. Said: Asked me to restart the modem and the NBN box.
  2. Wed 14 Oct 2026 Provider, ref INC-204418. Said: Line test passed; try a different cable.
  3. Fri 16 Oct 2026 Provider's technician visited. Found: Tested at the wall while it was working; nothing found. Written result: no.
  4. Sat 17 Oct 2026 Provider, ref INC-204418. Said: Logged as an intermittent fault. Promised: A call back with a line test result by Wed 21 Oct 2026. Overdue

Reference numbers, in order: INC-204418.

What I'm asking for

A technician to find and fix the fault, booked by a date I can plan around, and the result of the line test in writing.

Made with the free NBN fault log at secureacom.com.au/nbn-fault-log/. Kept by the customer; not checked by Secure A Com.

The log is saved in your browser on this device only. Nothing you type is sent to us or anyone else. The speed test runs on Ookla's servers, like any speed test, and never sees your log.

Print a blank log sheet. The same columns on paper, for the fridge. Show and print the sheet

NBN fault log sheet

Provider: ______________________ Plan: ______________ Connection: ______________ Reference numbers: ____________________________

Dropouts

DateTimeHow longCable or wifiLights on the NBN boxWeatherNotes

Speed tests (on a cable at the modem where you can)

Date and timeDownloadUploadPingCable or wifiDevice

Calls and visits

DateWhoReferenceWhat they saidWhat they promised, and by when

Made with the free NBN fault log at secureacom.com.au/nbn-fault-log/. Kept by the customer; not checked by Secure A Com.

Free fault log

Your NBN keeps dropping out. Here's how to prove it.

Log every dropout, speed test and call as it happens, and turn it into a one-page report your provider can't wave away. It all stays on your device.

Illustration: a paper-clipped stack of pages, the top one a grid of blue squares with a cluster of red ones, beside a modem with a cable to the pages

Why a log works when phone calls don’t

A fault that comes and goes is the hardest kind to get fixed. When your provider runs a test, it runs it at that moment, and at that moment your connection is often fine. So the test passes, the ticket closes, and you’re back where you started.

A log changes that. Twenty dropouts with dates and times, a pattern that sits in the evenings or on rainy days, speed tests on a cable at the modem, and every reference number in order: that’s a fault with a shape. It’s much harder to close, and it tells whoever comes out where to start looking.

We see it on jobs all the time. In our study of 324 fault jobs, faults that came and went were where people got stuck longest.

What to write down every time it drops

The tool asks for these, and so would a technician:

  • When it started, to the minute, and how long it lasted.
  • Cable or wifi. If a computer on a cable at the modem dropped too, it isn’t your wifi.
  • The lights on the NBN box. Which one changed, and to what colour. What the lights mean.
  • The weather. Rain and wind matter more than people expect. How weather affects your connection.
  • What you were doing, only if it might matter: a video call, a game, nothing at all.

Speed tests that count

A speed test on wifi in the back bedroom tests your wifi. A test that counts is on a cable, plugged into the modem, with other devices off the network and nothing big downloading. Ask your provider how many tests they want and how they want them done; some ask for several, a few minutes apart, on more than one device. Log every one, with the time. Run one in the Speed tests tab at the top of this page.

Every call, every reference number

Each time you contact your provider, write down the date, who you spoke to, the reference number, what they said and what they promised by when. The log marks a promise as overdue when its date passes with nothing after it. That one line, “promised a technician by the 14th, nothing since”, is often what moves a complaint up.

When to send it, and to who

Send the report to your provider first, in writing, and ask for a reference number. If it isn’t resolved, send it to their complaints team. If it still isn’t resolved, it goes with your complaint to the Telecommunications Industry Ombudsman. How each step works, and how long to give them.

Let software keep the log for you

If you can leave a computer on, PingPlotter will record every dropout to the second, around the clock, and you can log the speed tests and calls here. How to set it up.

When the log isn’t enough

Sometimes the provider sends someone, the test passes, and they say it’s your wiring. Sometimes it is. A log can’t tell you which side of the wall the fault is on. A test of the line from your side can. What an independent technician tests and puts in writing.

Your log stays with you

The log is saved in your own browser on this device. It isn’t sent to us or anyone else, and we can’t see it. Save a backup file if you want to move it to another device, and clear it whenever you like. The speed test runs on Ookla’s servers, like any speed test, and never sees your log.

Frequently asked questions

How long should I log dropouts for?

Long enough to show a pattern. A week is a good start; two is better. Keep going while the fault does.

Does it matter if I'm on wifi?

Yes. A dropout on wifi might be the wifi. If a computer on a cable at the modem drops at the same moment, it's the connection.

How many speed tests does my provider need?

Ask them. It varies, and some want several tests a few minutes apart on more than one device, all plugged into the modem with a cable.

Is my information sent anywhere?

No. Everything you type stays in your browser on this device. Nothing is sent to us. The speed test runs on Ookla's servers, like any speed test, and never sees your log.

Can I use the report for a complaint to the ombudsman?

Yes, as your own record of what happened. The TIO calls documents and evidence optional but helpful. How to complain.

Need this fixed rather than explained?

This is written from the field. When the fault needs a technician on site, this is where to go next.

Ask us anything