Telstra outages and service status in Sunderland Bay, Victoria

Problems in the last 24 hours in Sunderland Bay, Victoria

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

Telstra Issues Reports Near Sunderland Bay, Victoria

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

• 
  Matt (@thethorpstar) reported 19 minutes ago from Sunderland Bay, Victoria

  @Telstra Yes send me a message . I’m now told they want to charge me a cancellation fee for a service that doesn’t work properly

• 
  Matt (@thethorpstar) reported 38 minutes ago from Sunderland Bay, Victoria

  @andy_penn @Telstra your customer service is pathetic! Been waiting 10 days on an order and no one can tell me when it will be delivered!! Your messaging app people are pathetic! One hour waiting for a reply!

Telstra Issues Reports

Latest outage, problems and issue reports in social media:

• 
  👠 ☔ 👌🇦🇺 🏳️‍🌈Golden Girl (@Terri_1987a) reported 3 minutes ago

  @Westgat06583980 It has something to do with VicTrack as they use the Telstra network to radio trains

• 
  Zen🧘🏼‍♀️ Harley Jobe Arch CDT Werm Lindsay Stan (@sittingwanderer) reported 4 minutes ago

  @banditkayfabe @RayJCapo79 @Telstra Telstra sucks bro

• 
  El Presidente (@KeithKjm1) reported 4 minutes ago

  Telstra should be re-nationalised and be placed under direct government control. That would solve a number of problems such as today’s outage and ensure greater national communications security.

• 
  TradeFlock (@TradeFlock) reported 17 minutes ago

  Telstra outage halts Aussie commerce as nodes fail Software glitch breaks time sync across national network. Eftpos payments and trains down while ASX slips on oil shock fears. Reply with your disruption story

• 
  Kaz|#1 fan of Spider from rotld (@KazzyyStarr) reported 18 minutes ago

  MY INTERNET WENT OUT FOR HOURS **** YOU TELSTRA

• 
  Easy Z (@EasyZ51867924) reported 18 minutes ago

  @AshPolitik Or maybe its just the fact that Telstra have outsourced the support of their critical systems to India?

• 
  John Young (@JohnYoung146083) reported 18 minutes ago

  @newscomauHQ How dare you charge so much for your appalling service but if you ever have to contact for help you will just get a scripted nothing from the Philippines or a defensive snub from Melbourne. Just a deadwood union shop now @Telstra

• 
  Jason White (@JWhite90566) reported 19 minutes ago

  @mdtlion She sounds more like a Telstra public relations officer, than the Communications Minister. Maybe she’s grifting for a future job with them. I noticed the little dig she made at Optus by mentioning a previous issue they had had in the past, but totally relevant to today’s issues.

• 
  Tish (@oztish) reported 19 minutes ago

  @Telstra Still not working. Calls going to message back. Now what?

• 
  Samuel ⏳ (@osborne_sam) reported 19 minutes ago

  a likely root cause of the Telstra GPS node bug full extended week as a single integer is the older/legacy storage method used in GPS timing devices splitting the week into low (10-bit) + high bits using bit fields is the newer, more modern approach firmware updates that change the storage format from full week to bit fields are common but risky, as they require correct data migration the Telstra outage was most likely caused by a bug during such a storage format change in a firmware update a firmware update changed from storing the full week number to using the low and high bit-field structure the new firmware read the old data from NVRAM using the new bit-field layout without properly converting it because the bits were misaligned, the week_high value was interpreted as 1 less than it should have been this results in the time being exactly 1024 weeks too low (~November 2006) example // What the old firmware stored (simple integer) uint16_t old_stored = 2426; // Full extended week // New firmware reads it using bit fields (buggy) struct gps_week new_read; memcpy(&new_read, &old_stored, sizeof(uint16_t)); // Due to bit misalignment: // week_low might get 378 // week_high might get 1 instead of 2 uint16_t reconstructed = (new_read.week_high << 10) | new_read.week_low; // Result: 1*1024 + 378 = 1402 exactly 1024 weeks too low