Telstra outages and service status in Hamilton, Victoria

Problems in the last 24 hours in Hamilton, Victoria

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

Latest outage, problems and issue reports in social media:

• 
  Ancient Tiger (@TigerAncient) reported 2 minutes ago

  @CampbellMander1 @toni_symonds I was just literally on the line to telstra, 132999. They made me wait 50 minutes. That is not what you would do as the shadow minister for emergency communications. You’d check it yourself.

• 
  Toobs (@lockie_crash) reported 3 minutes ago

  @MickamiousG @Starlink When starlink finally get their mobile plans into Australia Telstra will be done within 2 years...one of Vodafone and Optus will survive as a budget telco, but people won't be paying Telstra prices for dogshit service

• 
  Big Breaking ⚡ (@bigbreakingit) reported 5 minutes ago

  Australia's biggest telecom outage in years has raised serious questions. Millions of Telstra users lost mobile service, payments were disrupted, transport was affected, and even emergency calls were impacted. Telstra says it was caused by a software defect—not a cyberattack—but many are asking: How can a single software failure cripple critical national infrastructure? An official investigation is now underway.

• 
  Marc Dunphy (@dunfff) reported 5 minutes ago

  @Matt__Welsh_ Has to be another Telstra outage. Unprecedented.

• 
  big J (@Dacey4Jason) reported 6 minutes ago

  @HaveeSnowball I pay twice as much as last year and get half the service. Telstra is just taking money but no up grades with the money. No wonder I and many others are moving to starlink

• 
  Luke Amott🇦🇺🐾🐶 (@luke_amott) reported 8 minutes ago

  @OMGTheMess If she came back, what exactly could she have done? Told Telstra to fix the problem faster I think not.

• 
  Jeremy (@jez99) reported 12 minutes ago

  What an absolute joke from Telstra today. Changed companies to them from Optus over their outage a few years ago and it still happens. Had no connection all morning.

• 
  Sharon Cook (@ShazzaCook) reported 13 minutes ago

  @Telstra While I'm not with telstra but my mobile provider uses your network, I lost a day work as I am self employed. I needed to work but couldn't as I needed my mobile data to carry out my work.

• 
  Orstraya (@orstraya) reported 14 minutes ago

  @HaveeSnowball I've never understood why so many people willingly pay through the nose for Telstra.

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