Optus’s 11 September outage affected 190,911 voice services. The emergency-call questions remain

Optus has recorded a major mobile voice outage affecting 190,911 services across Victoria, South Australia, Tasmania and the Northern Territory on 11 September. The interruption ran from 1:33pm to 2:49pm AEST, according to its national outage register.

The service count gives some sense of the scale. The more important question is what happened to people trying to reach emergency assistance—and whether the published account explains that clearly enough.

What Optus has put on the record

The register labels incident IM2344068 a major outage and identifies an equipment or system fault or failure as the high-level cause. It says the cause was not a natural event or weather. The entry was published on 13 September.

Optus does not provide a premises count, saying it lacks the technical visibility. Its affected-service figure is for mobile voice. Those distinctions matter: a headline about hundreds of thousands of failed Triple Zero calls would not be supported by this record.

The listed start and end times amount to one hour and 16 minutes. The register’s duration field displays “1.16”; reading that as 1.16 decimal hours would give the wrong duration.

What the emergency-service reporting says

ABC News reported on 12 September that Triple Zero Victoria had received details from Optus of around 40 calls that experienced difficulty connecting to the national emergency call operator. Victoria Police conducted welfare checks. The same report said South Australia Police carried out two checks without incident.

Those figures describe particular reports and jurisdictions. They are not a complete national count, and “difficulty connecting” should not automatically be rewritten as a permanent failure to receive help.

Communications Minister Anika Wells said on 13 September that the outage had produced no adverse outcomes for Australians. That is the minister’s statement. It should sit alongside the documented disruption, rather than erase it.

A restored service is only part of the explanation

The public record should let a reader follow the sequence: when the fault began, when the company recognised an emergency-call risk, when emergency services received useful information, and when affected callers were checked. Those are different milestones.

A network can be restored before every missed caller has been accounted for. Equally, a person may receive help through another route while a fault continues. A useful review needs to show both the technical recovery and the response to callers.

The register’s broad cause category does not establish which component failed or why an alternative route did not work for a particular call. It would be premature to name a technical cause beyond the one Optus has published.

Optus outage history: three incidents worth keeping distinct

These are selected major incidents relevant to the emergency-call questions, not a complete history of every Optus service interruption. The dates below are when the outages happened; investigations and enforcement came later.

8 November 2023: nationwide network outage

ACMA later found that Optus failed to provide emergency-call access for 2,145 people and failed to conduct 369 welfare checks. On 8 November 2024, the regulator announced that Optus subsidiaries had paid more than $12 million in penalties. That enforcement announcement concerned the 2023 outage, not a separate incident in 2024.

18 September 2025: emergency-call disruption

On 30 July 2026, ACMA announced Federal Court proceedings over this outage. It alleged that Optus Mobile breached emergency-call access and carriage obligations on 1,005 occasions. Those are allegations in the regulator’s announcement, not court findings. They should not be presented as a penalty already imposed.

11 September 2026: the current voice outage

Optus’s register records 190,911 mobile voice services affected across four jurisdictions for 76 minutes. The emergency-service reporting described earlier in this article is separate from that service count. The register alone does not establish how many emergency callers ultimately could not obtain assistance.

These figures cannot be added together or used as a simple ranking. The 2023 finding counts people denied emergency-call access; the 2025 proceedings describe alleged breaches; the 2026 register counts affected voice services. Nor does recurrence prove that each incident had the same technical cause. The useful comparison is whether the safeguards and follow-up procedures introduced after earlier incidents worked when needed again.

For readers checking their own experience, keep the approximate time, location and service used with any provider complaint. A screenshot of a failed ordinary call can document your experience; it cannot establish the national scale or cause. Do not make a test emergency call to check whether a network works.

What a useful follow-up should establish

The next useful information is a clear failure explanation, a reconciled account of affected emergency calls, and specific measures addressing that failure. “Services restored” is necessary operational information. It does not answer whether the same conditions could recur.

For an essential service, the standard should be understandable evidence: what broke, how people were protected, and what has changed. We will distinguish any later investigation findings from the limited incident record available now.