Telstra outages and service status in Little Hampton, South Australia

Problems in the last 24 hours in Little Hampton, South Australia

The chart below shows the number of Telstra reports we have received in the last 24 hours from users in Little Hampton, South Australia 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

Latest outage, problems and issue reports in social media:

• 
  Ben B (@bennyb082) reported 3 minutes ago

  @SkyNewsAust What a load of nonsense, Telstra is private company how can government "systemically" fail to prevent a fault. Faults do happen even in most well designed systems.

• 
  Casey McGregor (@CaseyMcGregorAu) reported 5 minutes ago

  So we have another outage impacting 000 calls in Australia, this time by Telstra. This has already happened with Optus twice if I recall. Enough is enough. Renationalise Telstra and Optus, and give them all the funding needed to maintain, develop and expand our telecommunications infrastructure across Australia in the interests of the people rather than private and foreign shareholders. #auspol

• 
  💫CeeGee (@Georg_ie_C) reported 7 minutes ago

  @RayJCapo79 @Telstra Correct … they have come out today saying they are still working on some issues. Very frustrating!

• 
  Step and fetch (@FetchStep) reported 10 minutes ago

  @destiny_ridge Telstra build the cheapest system out of the cheapest components installed by the cheapest labour and charge the most of all its competitors . Putting profit before the people gets you a system where a "timing issue" brings down a countries communications network .

• 
  Naomi (@Manylivesinone) reported 11 minutes ago

  @margmopp @Kate3015 @KristyMcBain Oh **** right off with that bullshit. Only responsible thing my arse. Is he could warn us? Sure Margaret. All the media news about the Telstra network and warning messages from providers was enough? She is useless and my local senator. Wouldn’t feed her rocks.

• 
  Shamim A (@Shamim_A28) reported 13 minutes ago

  @Sahar_A_Writes What a disgraceful hypocrite senator Sarah Henderson is. She made a complete fool of herself on #AfternoonBriefing too where she was called out for her antics. Thanks to the Telstra outage we learn that Sarah, Barnaby Joyce and Angus Taylor are simply all very stupid #auspol

• 
  Matthew Walker (@keltra68) reported 13 minutes ago

  @RoadknightThe I don’t think Telstra deliberately sabotaged their network. Human error , faulty equipment etc will always happen.

• 
  Samuel ⏳ (@osborne_sam) reported 14 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

• 
  David May (@mayd) reported 14 minutes ago

  @Telstra Voice calls still not working.

• 
  Mel J🐝 (@mel_wright123) reported 16 minutes ago

  @PipoErgoSum @TheKennyDevine Why did Henderson Need To Know? She’s not in government. Potentially bumped a couple of real emergency calls. Telstra directed failed calls to emergency services to ensure welfare checks. There WAS back up in place.