Optus outages and service status in Muswellbrook, New South Wales

Problems in the last 24 hours in Muswellbrook, New South Wales

The chart below shows the number of Optus reports we have received in the last 24 hours from users in Muswellbrook, 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

Latest outage, problems and issue reports in social media:

• 
  Peter 🏊🏼🚲🏃🏻 (@Ironman_peter) reported 6 minutes ago

  @7NewsBrisbane Why doesn’t 000 have an alternative number as a backup run by? Maybe Optus or Tpg or Vodafone? How does a company or a business run with just one solution? 000 is incompetent.

• 
  saint_ted (@saint_ted3) reported 8 minutes ago

  @TonyShepherd4 Where was the communications minister? Some one needed to step up and actually test it! Not like the the bungled Optus uggrade where the 000 outage went unnoticed for hours. Smart and proactive! Not something you Labtards would know anything about Tones.

• 
  Mark A (@MarkA5859) reported 8 minutes ago

  I really am angry the LNP rooted the NBN. Now I have to seriously consider Musk’s Starlink for my Internet especially since both Telstra & Optus have & are having issues.

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

  @sorcy79au @freodockers slow internet at Optus so yep lol

• 
  William Butcher (@WilliamBu49) reported 9 minutes ago

  @ShimogaHuduga @ravikeerthi22 Optus stadium costs 8000cr. NaMo stadium is **** 👍🏻

• 
  NewsTongue (@NewsTongueX) reported 14 minutes ago

  🔴 Telstra CEO faces parliamentary inquiry over nationwide outage affecting emergency calls, payments Telstra chief executive Vicki Brady will testify Friday before an emergency parliamentary inquiry into last week's outage that knocked out triple zero emergency calls, disrupted payment systems, and stopped trains in two Australian states. Greens communication spokesperson Sarah Hanson-Young said: "Telstra, just like Optus, has put their profits ahead of public safety and public service for far too long, and the law allows them to." • Telstra accepting compensation claims from affected customers and small businesses with supporting evidence

• 
  Mr J (@warcroft) reported 15 minutes ago

  @TimjboAU Remember a week ago when the entire telstea network went down? Remember a month before that when the entire optus/tpg network went down? Now next week we have the entire network government alert thing happening? Yeah, those network outages were 100% preparation for next week.

• 
  James Bernard 🇦🇺✝️☕🎸 (@jamesabernard) reported 16 minutes ago

  Telstra network issues rumble on in qld. Messages delayed Calls dropped. How's Optus & Vodaphone doing?

• 
  Ash 🇦🇺 (@TheInspectorAsh) reported 18 minutes ago

  @JacintaAllanMP We saw similar issues with Optus. There is supposed to be redundancy that allows emergency calls to be carried over any available mobile network. If our emergency communications and critical infrastructure are meant to be resilient, why do single network outages continue to have such widespread impacts? It’s time to review whether our redundancy is truly independent, or whether we’re relying on backup systems that share the same points of failure.

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