Optus outages and service status in Sippy Downs, Queensland

Problems in the last 24 hours in Sippy Downs, Queensland

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

Live Outage Map Near Sippy Downs, Queensland

The most recent Optus outage reports came from the following cities: Sunshine Coast.

City	Problem Type	Report Time
Sunshine Coast	Internet	6 hours ago
Sunshine Coast	Internet	4 months ago
Sunshine Coast	Phone	5 months ago
Sunshine Coast	Phone	5 months ago
Sunshine Coast	Wi-fi	5 months ago
Sunshine Coast	Total Blackout	5 months ago

Nearby cities with recent reports

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.

Optus Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Toobs (@lockie_crash) reported 6 minutes ago

  @MickamiousG @Starlink When starlink finally get their mobile plans into Australia Telstra will be done within 2 years...one of Vodafone and Optus will survive as a budget telco, but people won't be paying Telstra prices for dogshit service

• 
  A K (@AK22762976) reported 11 minutes ago

  @Birdsperch Clearly no contingency for terrestrial fail [all eggs in one basket] even with satellite backup downlink distribution relies on terrestrial bearers (circuits), Even Optus with satellite support incorporates terrestrial distribution -Contingency planning is key & costs money

• 
  Anthony Hodge 🦁🏆🐴 B2B! '24 & '25 AFL PREMIERS!! (@AwesomeAntho91) reported 13 minutes ago

  Halftime at Optus. That second quarter was, despite the inaccurate set shots, actually a lot better than the first. But we're still down by 7 points, so it's time for the Lions to regroup and go again in the third term. Hopefully the Eagles will finally lose their legs by then. #AFLEaglesLions

• 
  Tweet Whisperer David J Smith (@Ausshot3Dave) reported 14 minutes ago

  @strangerous10 And they pushed back at global roaming as well. Happens as a default in most countries. Would save a lot of problems if Telstra or Optus shared their networks when network problems arose with any communications provider in Australia 🇦🇺 @AlboMP

• 
  bndt (@banditkayfabe) reported 16 minutes ago

  **** off triple nose I want the rumble at Optus Stadium in Perth

• 
  Digby’s mum (@CallieBuddy) reported 17 minutes ago

  @externallylaws Can confirm the outage impacted the wilds of NT - where there is no Optus service.

• 
  Dacian (@DevDacian) reported 21 minutes ago

  GLM is a lot less "forgiving" than Opus/GPT; use these techniques in your long workflows to avoid many GLM errors: 1⃣ incremental output - don't output at the end, make your agents output incrementally while working 2⃣ checkpoint writes - glm agents can timeout very easily during reasoning phases, so have them output checkpoints to prevent this 3⃣ tighten prompts - glm seems a lot dumber than opus/gpt at figuring out what the correct action is, so tighten up your prompts to remove any ambiguity 4⃣ negative & positive enforcement - opus/gpt generally do the right thing if given the reasons why that is the right thing to do, but glm benefits from explicitly being told what to not do since it loves to misbehave 5⃣ tolerate output variance - glm is worse at outputting correct formats. Tighten up output specification prompts but also consider tolerating greater output variance & using deterministic output cleanup to format things correctly 6⃣ verify outputs, auto retry - glm can return seemingly "successful" but without writing any outputs, it can return weird tooling info in its outputs, there are lots fo weird things that can happen. Ensure to check the outputs for correctness, diagnose the cause of failures & have automated system in place to re-try failed spawns using prompts which instruct the retried agent to correct the errors Perhaps I've just been spoiled by Optus/Gpt but GLM feels quite "rough around the edges" in comparison.

• 
  Jack The Aussie (@hammerofleft) reported 22 minutes ago

  @amagickeagle999 You stupid ****. She was mouthing off about increasing standards and enacting penalties for service outages after the Optus crash but has done **** all. So you partisan ******** get some facts, she ****** up.

• 
  FreoLou⚓🤘🛫⚖️ (@FreoLou) reported 23 minutes ago

  Better get my pre game post out before Optus is full and the network fails to load. Tonight is a test @freodockers . You have studied for it. You have prepared. Now it is time get out there and ace the exam. Harness the nerves and kick between the two big sticks #foreverfreo

• 
  BRODA (@RazeBannon) reported 27 minutes ago

  Ask Grok: Can ISPs block VOIP? Yes, ISPs can block Voice over IP (VoIP) traffic at their network level, and many do so in practice. This is technically feasible using tools like port blocking, deep packet inspection (DPI), and other traffic management techniques. How ISPs Block VoIP ISPs control the core network infrastructure, so they can inspect and filter traffic before it reaches customers. Common methods include: Port-based blocking**: Traditional VoIP often uses specific ports like UDP 5060/5061 for SIP (signaling) and a range of ports (e.g., 10000–20000) for RTP (media/voice). ISPs can simply drop traffic on these ports. Deep Packet Inspection (DPI)**: This examines not just headers but packet contents, signatures, packet sizes, timing, and protocol behavior to identify VoIP even if it uses non-standard ports or obfuscation. DPI can dynamically detect and block SIP, RTP, or app-specific patterns (e.g., Skype, WhatsApp calls). IP address or domain blacklisting**: Blocking known servers of VoIP providers. Protocol anomaly detection or traffic shaping**: Dropping or throttling UDP-heavy, low-latency streams typical of voice calls. Real-World Examples Certain countries and carriers (e.g., in the Middle East, Morocco, Philippines, or places with state telecom monopolies) block VoIP to protect traditional phone revenue or for regulatory reasons. Mobile providers like Optus 4G or others have blocked SIP traffic. Corporate/school networks or bandwidth-limited ISPs sometimes block or deprioritize VoIP to conserve resources. China has historically blocked VoIP, though workarounds emerged over time. Limitations and Challenges for Complete Blocking Encryption and obfuscation**: Modern VoIP (e.g., over WebRTC, HTTPS, or apps like Signal/WhatsApp) is harder to detect reliably. DPI isn't foolproof against randomized ports, variable packet patterns, or VPN-like wrapping. VPNs and tunnels**: Users can often bypass blocks by routing traffic through a VPN, which encrypts and hides the VoIP signature. Evasion techniques**: Providers and users adapt with port hopping, STUN/TURN servers, or proxies. False positives**: Overly aggressive blocking can disrupt other UDP-based services (gaming, video streaming). Complete, unbreakable blocking is difficult long-term without also harming general internet performance, but partial or effective blocking for most users is very achievable. Why ISPs Do This Reasons include protecting legacy telephony revenue, complying with regulations, managing bandwidth, reducing congestion, or enforcing content policies. In summary, yes—ISPs have both the capability and precedent for blocking VoIP, primarily via DPI and port controls, though motivated users can often circumvent it. If you're dealing with a specific ISP or scenario, details could help narrow down options. TCP/IP allows spam filters at the node level. This is one small example. TCP/IP remains neutral and ethical.