How a 000-linked death, confused customers, and scrambled safety pages expose a deeper crisis inside Vodafone/TPG.
When a telco canât even keep 000 calls reliable – while its own staff tell customers to ignore safety warnings – youâre not looking at a âtechnical glitchâ. Youâre looking at a system where process consistently wins over people – until someone gets hurt.
â Part 1 – The 000 Failures: Not Just One Tragedy
Thereâs a moment in every corporate crisis where the public noise dies down but the internal temperature spikes.
For TPG Telecom, that moment arrived with the Triple Zero failure linked to a customer death on the Vodafone network – and with another customer publicly describing how Vodafone staff repeatedly failed to help her fix 000 call problems for months.
Publicly, this is being framed as a handful of older Samsung phones and âout-of-date softwareâ.
But if you look properly at the ABC reporting and TPGâs own hurried content, itâs bigger than that:
- a death after failed 000 calls
- tens of thousands of at-risk devices
- a customer who did exactly what the warnings said, then got told by Vodafone to ignore them
- and a regulator now openly questioning compliance and oversight.
This isnât a quirky handset issue.
This is a systemic failure where people only get taken seriously after the media steps in.
1. The death on Vodafone: 000 failed, and someone didnât come home
From the ABCâs consumer affairs coverage:
- A Sydney TPG customer using Lebara on the Vodafone network tried to call Triple Zero and could not connect.
â - That customer later died after the failed emergency attempts.
â - TPG says the Vodafone network itself was âoperationalâ at the time. No outage.
â - The problem relates to older Samsung devices that donât correctly connect to another network for 000 when Telstra/Optus arenât available.
â - Telstra testing had already identified more than 70 Samsung models that could not call 000 on Vodafone in certain fallback scenarios.
â - TPG has now admitted that:
â- 24,000 customers need urgent software updates; and
- another 6,000 devices must be replaced so they can reliably call 000.
- Those devices will be blocked from the network if people donât comply.
So weâre not talking about a freak one-off.
We are talking about tens of thousands of phones that may silently fail at the exact moment people expect their telco not to screw up.
2. Janeâs story: Vodafoneâs warnings said âurgentâ, staff said âignore itâ
The second ABC piece puts a human face on what âsystemic failureâ actually looks like.
âJaneâ (not her real name):
- is 68
- lives alone in the Adelaide Hills
- uses an older Samsung Galaxy Note 8 on Vodafone.
She began receiving Vodafone SMS warnings last year, after the 3G shutdown, telling her:
âYour device is still identified as unable to make emergency 000 calls. It is urgent you update your device software⌠your phone will be blocked.â
She did what a responsible customer is supposed to do:
- She took the messages seriously.
- She called Vodafoneâs call centre straight away for help.
And what happened?
- Vodafone staff told her to ignore the warnings because her device was supposedly unaffected and ânot on the listâ of problematic phones.
â - The 000 warning messages kept coming anyway.
â - She became worried, so she actually tested calling 000 – and the calls didnât connect, even though her call log shows repeated attempts.
â - When the warnings escalated to a âfinal warning – service will be shut down tomorrowâ message, they still didnât clearly tell her which software needed updating or how to do it.
â - It was only when she went to an independent repair shop weeks ago that someone showed her the exact update she needed to perform. She then had to fill out a Vodafone form to get unblocked.
â - Only then could she successfully call 000 again.
Her verdict on Vodafoneâs handling?
âItâs very unclear and it keeps consumers in the dark. I donât have time to spend hours on the phone.â
This isnât just a handset problem.
This is frontline staff contradicting safety warnings, muddled internal information, and a customer left at risk for months.
When a telcoâs own safety SMS says âurgentâ and the call centre says âdonât worry about itâ, thatâs not a glitch.
Thatâs a process failure, a training failure, and a governance failure.
3. Consumer groups and experts: this should have been fixed a year ago
Between both ABC pieces, the chorus is loud and consistent:
- ACCAN CEO Carol Bennett says the phones should have been identified and blocked a year ago, and that theyâve âslipped through the cracksâ with tragic consequences.
â - She openly questions whether telcos are complying with strengthened 000 obligations, and whether ACMA has been proactive enough.
â - She points out that older devices are typically held by more vulnerable customers, who are least able to absorb forced handset upgrades.
â - IT professional James Parker told a Senate inquiry that these kinds of failures have been obvious âfor a very, very long timeâ, but sufficient action wasnât taken by anybody.
â - Telecoms expert Mark Gregory asks why there hasnât been earlier testing of older phones to produce a consolidated non-compliant list, and calls for stronger oversight and faster action.
â - Shadow Communications Minister Melissa McIntosh bluntly says trust in 000 has been undermined again and asks: âWhat have the telcos been doing for a whole year and what has the government been doing to ensure the safety of Australians who need to call triple-0?â
This isnât me editorialising.
This is what the consumer lobby, technical experts, and opposition are saying, on record.
4. ACMA, the Government, and the âwe met our obligationsâ defence
On the regulatory side:
- ACMA says it was notified about the device issue and is now assessing whether any provider has failed to comply with the Emergency Call Service Determination.
â - It says it has already introduced new rules to ensure customers are notified and non-compliant devices are fixed or blocked.
â - The Albanese Government says telcos are responsible for testing, and points to strengthened requirements and a UTS-based National Telecommunications Resilience Centre for more rigorous testing.
â - ACMA is clear it can impose formal warnings or financial penalties if breaches are found.
Meanwhile, the telcos – including TPG – keep repeating the same line:
- âWeâre complying with our obligations.â
â - âWe acted as soon as we became aware.â
â - âWeâre working with Samsung.â
â - âThis is not a fault of the Vodafone network, but a limitation in how some devices were originally configured.â
But in the same breath, TPG/Vodafone also admit:
- Some customers may have been previously told their device was unaffected when that was no longer true.
â - They have only recently identified a âsmall numberâ of additional devices requiring updates or replacement based on ânew adviceâ and Telstraâs testing.
â - They âsincerely regret any confusionâ.
Read between the lines and the picture is simple:
They didnât know what they didnât know. And when they did know, their own internal communication to customers was still a mess.
That is exactly the pattern weâve been tracking on this site.
5. The giveaway: TPGâs sudden 000 micro sites and device-block messaging
You can tell how serious this is for TPG by what theyâve suddenly rolled out online:
âUpdate on calling emergency servicesâ – the emergency landing page
TPG has now published a central page saying:
- It covers all their brands: Vodafone, TPG, iiNet, Internode, Lebara, Kogan, felix.
â - If your device canât reliably call 000, it will be blocked.
â - Youâll get 28â35 daysâ notice.
â - Once blocked, you wonât be able to make or receive calls, send texts, or use mobile data.
â - Thereâs a list of impacted devices, and instructions to:
â- update your device (sometimes multiple times), or
- replace it immediately.
â
- It directs people to Vodafone stores and various call centres for help.
âTriple Zero and Samsung Devicesâ – the rushed newsroom explainer
On Vodafoneâs own media site, thereâs now:
- An admission that older Samsung handsets were blocked around the 3G shutdown because they couldnât call 000 on Vodafone.
â - A statement that they ârecently became awareâ those same devices, when used on other networks, still tried to send 000 via Vodafone 3G in some scenarios.
â - A claim this limitation âwas not previously knownâ.
â - A fresh acknowledgement that some devices now need updates or replacements to ensure they can call 000 on the Vodafone network.
Put all of this together:
- Years of known handset/000 issues raised by others.
â - A death after failed 000 calls on the Vodafone network.
â - A second customer publicly saying Vodafoneâs call centre told her to ignore 000 warnings.
â - A flurry of new 000 safety content, device lists, and âweâll block youâ messaging after it all blows up.
This is not what proactive safety leadership looks like.
The timing and sequencing is more consistent with reactive management than planned disclosure.
â Part 2 – A Microcosm of Vodafone/TPGâs Broader Rot
This 000 saga is not happening in a vacuum.
It sits on top of everything weâve been documenting on voda.fail for months.
1. The same pattern, just with higher stakes
Elsewhere in the business, weâve seen:
- TIO complaints spiking â not as isolated horror stories, but as a pattern.
â - Billing and credit chaos – promised bill credits that never land, chargeback mismatches, suspense accounts, and refunds that require manual journalling.
- Debt collection dysfunction â external agencies chasing wrong amounts, internal bad-debt systems that push the mess down the road.
- Felix cannibalising Vodafone postpaid while barely breaking even.
- Fixed Wireless constrained by capacity, and fixed-line in a steady state decline.
- Investor disclosures quietly watered down â churn % and ARPU breakdowns removed while management still boasts about ARPU âsuccessâ.
Now add:
- a 000-linked death;
â - tens of thousands of at-risk devices;
â - a customer who was correctly worried but wrongly reassured;
â - and emergency safety pages rolled out only after all this hits ABC and Parliament.
Same pattern, different stakes:
Minimal compliance over genuine care. ARPU over reality. Dashboards over lived experience.
2. Regulatory and market risk is now layered, not hypothetical
Where things stand now:
- ACMA is investigating.
â - A Senate inquiry will pull TPG in to explain what happened, what they knew, and why it took this long.
â - ACCAN, experts, and the opposition are all asking the same questions about compliance and oversight.
â - The public can now see on ABC that:
â- a person has died after failed 000 calls, and
- another customer was left in limbo for months while Vodafoneâs own systems and staff contradicted each other.
Overlay that with:
- Negative postpaid momentum and churn that appears worse than the decks suggest.
â - MVNOs and Felix eroding core ARPU and AMPU.
- Fixed-line decline and constrained Fixed Wireless capacity.
- A 000 incident that actively reinforces into TPGâs reputation with regulators, Parliament, and the media.
This is not a âbad headline and move onâ story.
This is the kind of event that:
- sticks in ACMAâs memory,
- shapes future enforcement,
- and makes investors think twice about the underlying risk profile.
3. Why ACMA canât treat this as just âa Samsung thingâ
If ACMA is serious, it canât stop at:
âDid you send the right number of SMS before blocking handsets?â
It has to follow the chain:
- Why did external testing (Telstra, Senate evidence) pick up these 000 failures so much earlier?
â - Why did customers like Jane get contradictory advice – SMS saying âurgentâ and staff saying âignore itâ?
â - When exactly did TPG know devices were failing 000 on their network?
â - What controls does TPG have in place over its outsourced customer-care provider, Tech Mahindra, to ensure compliance with legal and regulatory obligations – especially on matters involving safety, emergency-call handling, and consumer escalation?
â - What did they do internally between that moment and the death?
â - How much weight does TPG give to external signals – such as TIO complaint trends, online customer sentiment, and ABC News reporting – compared to its own internal dashboards and self-reported metrics?
This is bigger than Samsung firmware.
Itâs about how a telco with a damaged culture handles risk, truth, and customer safety.
â Part 3 – The Late ASX Announcement: Panic Disguised as Procedure
If you want proof this incident has detonated internally at TPG Telecom, look at the timing of their ASX announcement.
- The ABC ran its first Triple Zero failure story in mid-October.
â - The death linked to a Vodafone customer became public in November.
â - Parliamentâs Senate inquiry signalled the issue would be examined.
â - The media, consumer groups, and national tech experts were already reporting systemic gaps in device testing, compliance, and customer notification.
Yet TPG only released a market announcement on the 000 issue a full month after the ABCâs initial reporting and only after the story had spiralled into national scrutiny.
If this were a routine disclosure, it would have been timed with the initial incident.
If it were a transparent disclosure, it would have been published once Samsung and Telstra identified the device failures.
Instead, TPG waited until:
- the ABC published multiple pieces,
â - consumer groups accused telcos of breaching obligations,
â - the regulator confirmed an investigation,
â - Parliament put TPG on notice, and
â - the public pressure became impossible to ignore.
The result? An ASX announcement that looked far less like routine disclosure and far more like regulatory firefighting.
Investors arenât stupid.
They know the difference between:
- a proactive operational update, and
- a âwe waited until reputational containment failedâ announcement.
The timing alone suggests internal panic – a scramble to show compliance after the story broke, not before. And when you combine that with the rushed emergency micro sites, the updated safety pages, and the sudden device-blocking messaging, it paints the picture clearly:
The timing suggests TPG was responding to external pressure rather than acting proactively.
For a listed telco facing a Senate inquiry, an ACMA investigation, and collapsing consumer trust, that timing isnât just bad optics – itâs a flashing red light for governance and disclosure risk.
4. Where voda.fail fits in (and why this matters beyond one case)
This site has never been about one bill dispute.
Itâs about showing that:
- if you let a telco operate on spin and short-term metrics long enough,
â - eventually, you donât just get annoyed customers –
â - you get people who canât get help when their life depends on it.
The 000 stories are heartbreaking.
But they also vindicate what this campaign has been saying:
You canât fix Vodafone/TPG with a one-off apology.
You need structural change, enforced by regulators, under real scrutiny.
So hereâs the ask:
For ACMA & Parliament
- Treat the 000 failures as a systemic safety and governance issue, not just a technical edge case.
â - Demand full transparency on device testing timelines, internal risk assessments, and call-centre guidance.
â - Join the dots between TIO volumes, billing/credit chaos, and now 000.
â - Require a public, enforceable remediation plan with milestones, not marketing language.
For investors and analysts
- Ask why churn % metrics and ARPU sub-breakdown disappeared from the investor decks.
â - Ask what the real cost of these systemic failures will be:
- in remediation,
- in regulatory penalties,
- and in long-term brand damage.
â
- Stop accepting glossy narratives about ARPU while ignoring the rear-view mirror of complaints, outages, and now 000 failures.
For customers
- If youâre on Vodafone, Lebara, Kogan, TPG, iiNet, Internode, felix, make sure your device is updated and not on a blocked list.
- If youâve ever had 000 issues, document everything and escalate – to your provider, the TIO, and ACMA.
- Know that none of this is your fault. These are engineering, governance, and cultural failures at the provider level.
voda.fail will keep tracking this because, bluntly, somebody has to.
âď¸ Disclosure & Public-Interest Disclaimer
This article represents the authorâs independent analysis and opinion, based on:
- publicly available reporting from ABC News,
- regulatory statements and government disclosures,
- contemporaneous consumer records and correspondence submitted through the voda.fail campaign,
- industry-standard telco operations knowledge, and
- observable system behaviour across TPG Telecom brands (Vodafone, TPG, iiNet, Internode, Lebara, Kogan and felix).
This publication is made in the public interest, given the serious implications for:
- emergency call access (000),
- consumer safety,
- regulatory compliance,
- market disclosure obligations, and
- systemic risk within Australiaâs telecommunications sector.
All operational interpretations, systemic analyses, and risk assessments reflect reasonable inferences drawn from publicly available data and industry norms. They do not allege confirmed operational failures beyond what has already been publicly reported by ABC News, ACMA, Parliament, Samsung, or TPG Telecom.
Financial or quantitative impacts referenced in this article are illustrative estimates only. They are based on reasonable modelling and publicly available information, and do not represent verified financial results for TPG Telecom or any related entity.
This article does not constitute legal, financial, investment, or professional advice Readers should obtain independent advice before making any decisions.
No allegation of criminal conduct is made, implied, or intended unless formally determined by a competent court, regulator, or authorised investigative body.
Leave a Reply