iiNet Outage Report in Port Macquarie, New South Wales

Problems in the last 24 hours in Port Macquarie, New South Wales

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

Most Reported Problems

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

• Internet (62%)
• Wi-fi (19%)
• E-mail (8%)
• Total Blackout (7%)
• Phone (5%)

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 Near Port Macquarie, New South Wales

Latest outage, problems and issue reports in Port Macquarie and nearby locations:

• 
  Zaphod Beeblebrox (@Zaphod_BBX) reported 47 minutes ago from Port Macquarie, New South Wales

  @PetraAu @iiNet Using Google Drive to send and receive mail won't stop your problem because it still resides on IInet servers. The 1MB limit is ridiculously tiny. Suggest you bite the bullet and move to a Gmail or Hotmail address. Then you aren't tied into you internet provider for email.

iiNet Issues Reports

Latest outage, problems and issue reports in social media:

• 
  BC (@BCRSDivisioN_) reported 60 seconds ago from Adelaide, South Australia

  Hey @iiNet how about you get your shit together. Shouldn't have to wait 2 weeks to get internet turned on at a house.

• 
  Evan (@fictillius) reported 4 minutes ago from Sydney, New South Wales

  @NewtonMark @shaneoneill @Aussie_BB @Telstra I fired up an Aussie BB service at my parents new house just last week in 20 mins, after iiNet failed spectacularly at transferring their service from their old address. Did a Vodafone one on the weekend too and was online in an hour.

• 
  MurfasaurusRex (@dansheps_) reported 4 minutes ago from Brisbane, Queensland

  @iiNet Yup already spoken to them and there response tbh is not acceptable at this stage. For your interest here is the invoice that caused this problem. 695673371 you might find this a rather interesting case. This is just the start of the exposure of the illegal billing practices.

• 
  MurfasaurusRex (@dansheps_) reported 8 minutes ago from Brisbane, Queensland

  @iiNet Its too late its all ready with the TIO. Your support team failed to provide adequate support and at times ignored my requests and constantly spoke over me. I guess happens when you cut costs and move support overseas that have no idea about Australian consumer law. Damage done.

• 
  Jay Ball (@JayBallzup) reported 10 minutes ago from Melbourne, Victoria

  Hey @iiNet Why is your service status map reporting everything is fine at postcode 3156 when I, for the 4th time in 5 days, am again without internet due to an “outage”.

• 
  💧Robbie from SthGoldy (@RobbieSthGoldy) reported 15 minutes ago from South Golden Beach, New South Wales

  @LesStonehouse Go with iiNet so at least when it stops ... and it will you will get good customer service

• 
  Paul Hadlow (@VK2PNH) reported 18 minutes ago from Balranald, New South Wales

  @iiNet No I’ll do it tomorrow. But I think I may have found the issue. Your modem doesn’t like HF (7MHz & 14MHz) transmissions. Will have to find a work around to fix this. Might have to find a better modem.

• 
  Evan (@fictillius) reported 22 minutes ago from Sydney, New South Wales

  Also before they moved out their home internet had suddenly moved to Vodafone NBN but their iiNet account still showed usage up until the people at the new house turned off the modem. Sounds like a churn was done but iiNet support claims that is impossible

• 
  Joey B (@JoeyB_13) reported 22 minutes ago from Newcastle, New South Wales

  @Telstra Signed up with iiNet, not only is your service a disgrace but your customer service is as bad.

• 
  Flangela (@Flansq) reported 23 minutes ago from Point Talburpin, Queensland

  I think the solution was to change the WAN port from 1 to 4, despite the cable from the iinet modem being plugged into port 1.