# Telstra’s July Outage Review: Network Timing Was Never Treated as Critical > Catch-up: Telstra published the findings of Technology Audit Partners’ external investigation on 2 September 2026. The July outage was triggered by incorrect date information after timing-system maintenance, and the review found Telstra had not treated network timing as a critical “sovereign function”. What Telstra says it has changed. - Canonical URL: https://techxtelco.com/news/telstra-july-outage-review-findings/ - Published: 2026-09-12 - Updated: 2026-09-12 - Topics: Telco, News - Author: David Everson - Image: https://anrkjmgqmwfosbvyzrzc.supabase.co/storage/v1/object/public/article-images/telstra-july-outage-review-findings/hero-v1.webp - Publisher: Tech X Telco (https://techxtelco.com) Catch-up coverage: on 2 September 2026 Telstra chief executive Vicki Brady published the findings of an external investigation into the July mobile outage that disrupted calls, messages, data and some Triple Zero calls across Australia. The investigation, by Technology Audit Partners, found the trigger was incorrect date information spreading through parts of the mobile network after planned maintenance on the network timing system, and that Telstra had never treated network timing as a function critical enough to warrant its highest level of oversight. This article summarises what Telstra published; it is the company’s account of an independent report, not the report itself. **Quick answer** Telstra says the external review found the July outage was primarily the result of the company not treating network timing as a critical capability, a “sovereign function”, needing the highest levels of oversight and protection. Telstra has moved its timing services to new systems across three sites, added monitoring and alarms, and set up a company-wide remediation program. If you were affected, Telstra says it will continue to work with customers on any complaints or claims associated with the outage. ## What the Investigation Found Telstra’s post defines a sovereign function as a network function so critical that, if it fails, it could cause a network-wide outage. The primary finding was that network timing had not been treated that way. The post lists further shortcomings the investigators identified: ownership of the timing function was not adequately defined, which led to weak risk management; the timing architecture had evolved over time without adequate end-to-end oversight; there was insufficient technical expertise and insufficient investigation when issues appeared; and there were shortcomings in change management, configuration control, incident management, documentation and follow-through. Gaps in ownership and visibility also delayed the early identification of the problem once the outage began. Source: [Telstra Exchange: What we’ve learned from the external investigation of our July outage](https://www.telstra.com.au/exchange/what-we-ve-learned-from-the-external-investigation-of-our-july-o), read 12 September 2026. The post does not publish the full report, and it does not give updated figures for the number of Triple Zero calls affected. Readers wanting the underlying document or call numbers should look to Telstra’s Senate inquiry material rather than this summary. Source: [Telstra Exchange: What we’ve learned from the external investigation of our July outage](https://www.telstra.com.au/exchange/what-we-ve-learned-from-the-external-investigation-of-our-july-o), read 12 September 2026. ## What Telstra Says It Has Changed ### Actions Telstra Lists Each item is Telstra’s own description of work done or promised; none has been independently verified for this article. - Migrated timing services from the previous NTP servers to strategic systems across three sites. Described as already done. - Added monitoring and alarm capabilities for the timing function. Described as already done. - Introduced additional lab testing of network changes and worked with vendors on operational processes. Described as already done. - Established a company-wide remediation program. Ongoing. - Review other critical network functions to check they are prioritised correctly. Commitment. - Assess vendor alert notification processes, platform alarm instructions and service assurance arrangements. Commitment. - Continue to work with customers on complaints and claims associated with the outage. Commitment. Source: [Telstra Exchange: What we’ve learned from the external investigation of our July outage](https://www.telstra.com.au/exchange/what-we-ve-learned-from-the-external-investigation-of-our-july-o), read 12 September 2026. ## Why It Matters Beyond Telstra The finding is about governance rather than a single faulty box: a function that could take down the whole mobile network sat outside the tier of oversight reserved for the most critical systems. That is the kind of lesson regulators and the other carriers will read closely, especially with Optus facing court over its own emergency-call outage and a mobile coverage obligation moving through Parliament. This paragraph is editorial context, not a finding from the report. ## Sources and How This Was Checked Everything attributed to the investigation comes from Telstra’s Exchange post by Vicki Brady dated 2 September 2026, read on 12 September 2026. The Technology Audit Partners report itself was not available and was not read. No customer, Telstra representative or regulator was contacted. ### Official Pages Used - [Telstra Exchange: What we’ve learned from the external investigation of our July outage](https://www.telstra.com.au/exchange/what-we-ve-learned-from-the-external-investigation-of-our-july-o): the trigger, the sovereign function finding, the list of shortcomings, actions and commitments. Related on Tech X Telco: [New mobile coverage maps and outage registers: how to use them](https://techxtelco.com/news/mobile-coverage-outage-transparency/).