Optus outages and service status in Byron Bay, New South Wales

Problems in the last 24 hours in Byron Bay, New South Wales

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

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 Near Byron Bay, New South Wales

Latest outage, problems and issue reports in Byron Bay and nearby locations:

• 
  💧Costin Heaps 🌈 (@DianneCostin) reported 8 minutes ago from Ocean Shores, New South Wales

  Looks like yet another @Optus outage. Dropped out about 2 hours ago.

Optus Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Question (@Philssay) reported 8 minutes ago

  They said they'd fix it after the optus outage . Yet here we are again. Triple 0 failures . Well done anika fails

• 
  BRODA (@RazeBannon) reported 9 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.

• 
  James Hutcheon (@hutcho66) reported 9 minutes ago

  @MiddleMoney @aussiewongm @Anneeokeefe I'm pretty sure Metro went down during the Optus outages last year. But restoration time was quicker iirc.

• 
  bndt (@banditkayfabe) reported 11 minutes ago

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

• 
  Jarrod (@oneXaday) reported 18 minutes ago

  With Optus - national outage, price hikes ($45-60 monthly) and spotty, unexplained 4G and 5G city coverage. Decide to jump to Telstra. With Telstra - national outage... Yep.

• 
  𝔸𝕟𝕕𝕪 𝕄 (@m28_andy) reported 21 minutes ago

  @HaveeSnowball @JanSummersalt Only way to get customer service from Telstra is go to store or port your number to another company. They use ai bot systems that circle jerk you and waste your time. It's a joke. Same with Optus.

• 
  Dacian (@DevDacian) reported 22 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.

• 
  ▪️▫️DAVID▪️▫️ (@turtlemagpies) reported 22 minutes ago

  @Telstra What a disgrace that each Telstra customer has to individually apply for compensation for the outages last week. Really shows what you think of your customers. Just provide free data like Optus did you scabs. Pathetic 😡 #telstra #telstraoutage

• 
  JJ (@recursedand) reported 28 minutes ago

  @telstra hey ********: why give me free service all day to then leave me unable to recharge *still*? who is running your company? vote them out. you guys suck but you're better than optus *still* somehow.

• 
  🐟 (@mwupfront) reported 29 minutes ago

  @heathledgcrs i wanna come watch something at waca or optus so bad but no sports line up with my perth conventions 🥀🥀