Optus outages and service status in Greenwald, Victoria

Problems in the last 24 hours in Greenwald, Victoria

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

• 
  Anthony Hodge 🦁🏆🐴 B2B! '24 & '25 AFL PREMIERS!! (@AwesomeAntho91) reported 7 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

• 
  antiwoke82 (@antiwoke82_) reported 7 minutes ago

  @newscomauHQ Telstra sucks period optus no better

• 
  Sarisa sandy lindsay (@Sarisasand6rzp) reported 12 minutes ago

  gang Thailand Australia business online my location data internet WiFi Optus Telstra’s Vodafone unknown network my location gang student be I Ning university NSW Vitoria Melbourne Australia

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

• 
  Anouk72 (@Anouk724) reported 13 minutes ago

  @WesleySouthcott @ScomoCchio No. Optus has had outages too. And their response was just as pathetic as Telstra’s. But the point remains, huge service providers that can cause disrupt/impact nationwide are not held to account in any meaningful or significant way.

• 
  mark macca 🐅🐅🏆 (@mcdonellaussie) reported 14 minutes ago

  @Fallingsky556 I gather she was on the Optus network?

• 
  Richie_Night Owl (@richardmelb05) reported 16 minutes ago

  Our nbn internet/phone service isnt working. A @Optus techician was sent to my home to find out why we dont have nbn internet. He told me there is something wrong with the fibre optic internet cable. The cable brings the internet to our home.

• 
  dick_taylor (@dick_taylor) reported 18 minutes ago

  @VoteLewko On my mates farm in the coast they have redundancy (Starlink) & anothet mate who runs ASIC’s infrastructure says they have always had both Telstra & Optus to try & avoid over reliance on a single network. So if farmers & some federal bureaucrats know this why don’t Victoria’s?🤡

• 
  Metta Bhavana "officialfineprintenvoy" #5xjabbed (@MettaBhavana1) reported 19 minutes ago

  @james00000001 @Schtang Optus is not the problem! It's individual users and their settings.

• 
  Chris Eastaughffe (AZ Vac done) (@Chris_E_Qld_Au) reported 22 minutes ago

  @therevaknight Because of Government incompetence, they had no simple backup system, they made NO allowances for technological failure, complexity is the enemy of reliable; the reliability issue was known (ref previous OPTUS outage). NO REDUNDANCY for critical infrastructure! @heidimur