Optus outages and service status in Bungendore, New South Wales

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

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

Latest outage, problems and issue reports in Bungendore and nearby locations:

• 
  Andrew Christian (@GGL_Drew) reported 53 minutes ago from Queanbeyan, New South Wales

  Just spoke with family in Tuross Heads. Tuross is unaffected apart from smoke. Connectivity available on the Telstra network (but not optus). Power just turned on at 2am this morning. Water is on and working. #SouthCoastFires #BushfireEmergency #tuross

Optus Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Daisy Cutter how dare you (@daisycuttertz) reported 2 minutes ago

  @MRowlandMP Who got the cash from 50 billion labour hire MICK Telstra and Optus rolled a nationwide network in 18 months using their own employees get stuffed Mick Big Build 101

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

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

• 
  Oz Trooper (@TrooperOz) reported 3 minutes ago

  @jbulldogs4 Not really as its still ongoing. They told people to use a optus or vodafone device thats not Telstra. Thats some reliable service isnt it. Shouldn’t be happening but probably a overseas disgruntled workers!.

• 
  saint_ted (@saint_ted3) reported 5 minutes ago

  @Woodygocats59 @TonyShepherd4 Once again I refer you back to the Optus outage where everybody including the government and Optus thought the 000 service was functioning but it was found to still be out of action several hours later. And the government minister was AWOL again. A couple of hours can save lives.

• 
  Cameron Holt (@Strikerminime) reported 6 minutes ago

  @Optus are the worst telco on the planet. You’d think that after over 30 years of loyalty they’d be willing to negotiate a compromise and maybe even a little leniency to someone in financial hardship, but no. They don’t care. It’s all about the money. Stay away from @Optus

• 
  Littleaud (@littleaud1) reported 6 minutes ago

  @LeeshieV @Optus No problem with Optus on my phone.

• 
  V (@VDejan0000) reported 11 minutes ago

  @NoticerNews Same reason for the recent Optus outage. This woke CEO & Labor government needs to swing.

• 
  Brendan Kelly (@brendan_kelly9) reported 12 minutes ago

  @nicko_316 Thats bad news for Brizvegas if you’re right. Freo will be favourites in that match up at Optus.

• 
  Optus (@Optus) reported 13 minutes ago

  @Sharkies2035 Hi there, I'm sorry to hear about your poor experience with Optus' prepaid plans. We'd like the opportunity to turn this around for you. Please send us a Direct Message with more information so that we can investigate further. -San

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