iiNet

iiNet Outage Report in Burrum River, Fraser Coast, State of Queensland

No problems detected

If you are having issues, please submit a report below.

iiNet Limited is Australia's second-largest internet service provider. Their focus is primarily on ADSL-based Internet access. iiNet also provides optical-fibre, dial-up, and voice services.

Problems in the last 24 hours in Burrum River, State of Queensland

The chart below shows the number of iiNet reports we have received in the last 24 hours from users in Burrum River and surrounding areas. An outage is declared when the number of reports exceeds the baseline, represented by the red line.

iiNet Outage Chart in Burrum River, Fraser Coast, State of Queensland 12/04/2025 08:15

At the moment, we haven't detected any problems at iiNet. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by iiNet users through our website.

  1. Internet (81%)

    Internet (81%)

  2. Total Blackout (7%)

    Total Blackout (7%)

  3. Wi-fi (7%)

    Wi-fi (7%)

  4. E-mail (2%)

    E-mail (2%)

  5. Phone (2%)

    Phone (2%)

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

iiNet Issues Reports

Latest outage, problems and issue reports in social media:

  • Gervo1865 L Gervasoni (@Gervo1865) reported

    @NBN_Australia @iiNet internet has been going out a lot in Hepburn Springs over the past 2 months. Been out for 20 mins now ... turned modem off and on 3 times but no joy. Anyone else having problems?

  • irreverentlaw Theirreverentlawyer (@irreverentlaw) reported

    @iiNet And it continues. After poor service with NBN and internet now I try..after 7 days..to instal 'Fetch ' only to be told my service is not fully operational. You people really suck.

  • Lee_Tennant Dame Holly says #gladysmustgo (@Lee_Tennant) reported

    @pauldutton1968 @iiNet The worst part was that they'd say they'd do something and never do it and then you have to call again and go through it again. I was ready to kill them, honestly.

  • pauldutton1968 👣 🌏 💫 Wiimpitja 🌳 🦅 🐾 (@pauldutton1968) reported

    @Lee_Tennant @iiNet That’s all we’ve had for two months of issues with the same broadband response to “fix” the problem. It’s bigger issue clearly if you’d check the history of complaints on the damn service.

  • Mannekethepup Manneke the Pup (@Mannekethepup) reported

    Hey @iinet our interwebz (vdsl2) are running at 2mbps and it's so slow it's making us sad! What's the story? Canberra 2614 (and why does it show us as connected to TPG?!)

  • SandiHLogan Sandi Logan (@SandiHLogan) reported

    .@iiNet THREAD. seems infected by Kris/Chris. Latest advice (back online, for now): "Apols, Sandi. We are seeing multiple responses from customers re this issue so my colleague may have been confused. It also appears they (?) were mistaken in saying that it has been resolved." 2/

  • tony_chatham Tony Chatham (@tony_chatham) reported

    @SandiHLogan @iiNet Customer Service 101: don’t argue with or act in a disparaging way towards your customer who pays your wage.

  • Fraying_hem Francis Tumeny-Tum (@Fraying_hem) reported

    Check out my Speedtest results! 0.7 Mbps down and 1.1 Mbps up. Another quality result from @iiNet

  • fluffylynx Riley (@fluffylynx) reported

    Its bad enough that @iiNet's new mobile plans require individual accounts each with their own unique login name and invoice (on top of an entirely seperate NBN account)... Now they seem to have charged me twice for one of them.

  • jobeth_b jo bella (@jobeth_b) reported

    Despite a technician coming on the 30th of October who saw what the issue was but even he couldn't get through to @NBN_Australia bc there was a process. We followed the process with @iinet but they couldn't seem to explain to @NBN_Australia the issue. So we languished.