Telstra outages and service status in Esk, Queensland

Problems in the last 24 hours in Esk, Queensland

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

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

• 
  ⱮìçհąҽӀ φҽʂąҟ (@rieper47) reported 34 minutes ago from Esk, Queensland

  Literally left Telstra for this (and their horrendous customer service)

• 
  ⱮìçհąҽӀ φҽʂąҟ (@rieper47) reported 46 minutes ago from Esk, Queensland

  Your support is horrendous. I had garbage speeds with Telstra, but at least they were available almost 24 hours a day.

Telstra Issues Reports

Latest outage, problems and issue reports in social media:

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

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

• 
  Pauline leonard (@Pauline21359471) reported 6 minutes ago

  @AlanBixter @Telstra how dangerous for all the necessary services eg ambulance etc thats very poor in a country this big that relies on critical communication

• 
  Stock Croc (Value Investor) (@ValueCroc) reported 8 minutes ago

  Australia’s largest Telco Telstra’s Outage yesterday Is a Wake-Up Call: Why Satellite Redundancy Matters More Than Ever $ASTS Australia woke up on Wednesday to find its largest telco offline. Telstra’s mobile network went down nationwide when a cluster of timekeeping nodes inside the company’s data centres stopped synchronising properly. The disruption rippled through the day: trains suspended, EFTPOS and taxi payments failed in places, and Uber and EV charging platform Chargefox both reported issues. Emergency service equivalent of 911 ie Triple-zero access became the most sensitive thread of the story. That’s the real lesson here, and it reaches well beyond Telstra. Developed-world telcos have spent decades building single, deeply optimised terrestrial networks with comparatively little redundancy underneath them. As more of daily life, payments, transit, emergency response, routes through one mobile network with no fallback, the cost of a bad software update or a failed sync node keeps rising. Direct-to-device satellite is still early and still limited, but it’s the first real second layer this industry has had, and it’s arriving from two directions at once: 🐊Starlink’s consumer-facing model, already live with carriers across the US, Japan, New Zealand and elsewhere, and 🐊AST SpaceMobile’s $ASTS wholesale approach, which is signing long-term commercial agreements with AT&T, Verizon, Vodafone, Bell and stc rather than trying to compete with any of them. I invested in ASTS, after this incident, not because I think it’s about to parachute into a Telstra outage, but because this is a small yet concrete example of the structural gap it’s built to fill. Though ASTS buildout risk is real, more BlueBird satellites still need to launch and commercial service is only just ramping through 2026, but the demand side of the thesis got a little more obvious this week, and not just in Australia. This is not financial advice. I invested in ASTS and may buy/sell at any time. DYOR.

• 
  Tania Campbell (@TaniaC1072) reported 9 minutes ago

  @WindsorBeaver @thmsenglsh My phone is Telstra I had no problems but I just changed modem from Telstra to starlink and it’s so much better and cheaper

• 
  sam (@JudgeJungHeewon) reported 11 minutes ago

  Sure Odysseus had it rough, but did he have to deal with public transport during the telstra outage? NO HE DIDNT! IVE GONE THROUGH HELL AND BACK AND THERE WAS NO REWARD WAITING FOR ME AT THE END OF IT ALL

• 
  Professor_Stinks (@ProfessorStinks) reported 11 minutes ago

  Footage used by the bunker to confirm Bostock didn’t knock on now confirms he did knock on in post match review. Error being blamed on #Telstra outage. Can’t make this **** up! #soo #origin

• 
  Katie the Exposer Of Albos Verbal Bullshit. (@SenstiveHearts) reported 14 minutes ago

  Hello @Ausbobsmit today I Had a Frustrating Day of Nothing Working. My In app Bank Card Didn't work on the Bus Or in office Works. The Bank said It was Because of Telstra Outage Iam Not with Telstra. THIS country Keeps The Borders Open But Can't Keep a Phone Company Working. 😡😡

• 
  Dr Ravi Nayyar (@ravirockks) reported 15 minutes ago

  'The telco first identified a problem impacting "some" mobile phone calls and data services at about 4.30am on Wednesday, with Telstra advising Ms Wells's staff about the network crash at about 7am.

• 
  Steven Payne (@CmonMick) reported 16 minutes ago

  @FetchStep @Telstra Classic. A once government owned asset is privatised by the Libs. The privatised company then delivers a **** service. Punters blame Labor government for the **** service of a now private company🤷🤦

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