The Claim
“Lied by claiming the MyGov website was taken down by a DDOS attack, admitting only hours later that it was due to the more obvious reason, which was a sudden, drastic and entirely predictable increase in legitimate load.”
Original Sources Provided
✅ FACTUAL VERIFICATION
The core claim is factually accurate. Minister for Government Services Stuart Robert did initially claim a DDoS attack was responsible for the MyGov website outage on March 23, 2020, and then contradicted himself just hours later [1][2].
Timeline of events:
On March 23, 2020, as the coronavirus pandemic intensified and unemployment surged, Australians sought to register for welfare services through the MyGov portal. The website became slow and inaccessible for much of the morning [1].
At approximately 1:00 PM, Stuart Robert held a press conference and stated: "MyGov has not been offline, it's simply suffered from a distributed denial of service attack this morning" [1]. He refused to provide further details about whether the attack originated overseas [1].
However, by question time at 2:55 PM (less than two hours later), Robert was forced to retract his statement in Parliament [1]. He stated: "The DDoS alarms showed no evidence of a specific attack today" [1]. Instead, Robert acknowledged that the system's DDoS detection alarms had been triggered by the legitimate volume of users attempting to access MyGov [1].
The capacity problem:
Robert revealed that MyGov had been upgraded from handling approximately 6,000 concurrent users to 55,000 over the weekend in preparation for increased demand [1]. However, approximately 95,000 people attempted to access MyGov simultaneously, which triggered the DDoS detection alarms [1]. The alerts were false positives—the system was detecting the legitimate user surge as if it were an attack [2].
Missing Context
The claim accurately identifies the core problem but frames it as deliberate deception ("lied"). However, important context includes:
Predictability of demand:
The claim correctly notes this was "entirely predictable." During the coronavirus crisis with rapid business shutdowns, a massive spike in welfare applications was obviously foreseeable [2]. The government did attempt to prepare by increasing capacity 10-fold over the weekend, but this proved insufficient given the emergency circumstances [2]. The ZDNET article notes that Robert acknowledged: "We've put a 10-fold increase on our digital channels over the weekend in preparation" [2].
System architecture limitations:
The underlying issue was deeper than a capacity planning oversight. The system was fundamentally inadequate for surge demand. Before the weekend, it could only handle 6,000 concurrent connections; a 10-fold increase to 55,000 still proved insufficient when 95,000 users attempted simultaneous access [1][2]. This reflects broader infrastructure design issues, not merely a single day's lack of preparation.
Historical precedent:
Australia had experienced a similar incident just four years earlier with the 2016 Census website crash. That system was also overwhelmed, triggered by a combination of legitimate traffic (most households attempting to fill in the Census in a single evening) and actual DDoS attacks (3Gbps and 210Mbps attacks occurred) [2]. IBM was blamed for their geoblocking strategy and architectural failures, with investigations concluding "There was a failure on the part of ABS to sufficiently check that the contract had been delivered" [2]. Yet similar systemic issues persisted four years later with MyGov.
No evidence of international attack:
The sources confirm that no actual distributed denial of service attack occurred—only the DDoS detection system triggering false alarms [1]. This is not a case where a real attack occurred but was mischaracterized; rather, legitimate traffic created the appearance of an attack to the monitoring system.
Source Credibility Assessment
The Guardian - Australia's leading left-leaning but mainstream news organization. Owned by Guardian Media Group (UK-based), with a well-established reputation for political journalism. The article is authored by Josh Taylor, a regular Guardian tech/security correspondent. The reporting presents the facts straightforwardly with direct quotes from Robert in Parliament and press releases [1].
ZDNet - Technology news publication owned by Ziff Davis, which provides technical analysis and reporting. The article is authored by Chris Duckett, a technology contributor. The piece is clearly opinion-driven (beginning with "Congratulations Australia, even in the most foreboding of times, we have found yet another way to highlight the incompetence...") [2]. However, the underlying factual claims are sourced and accurate; the opinion wraps factual reporting.
Assessment: Both sources are credible for factual reporting. The Guardian provides straightforward news reporting. ZDNet provides technical analysis with opinion framing. Neither source is primarily partisan (in the Labor vs. Coalition sense)—both are technology/policy focused rather than explicitly Labor advocacy.
Labor Comparison
Did Labor government have comparable infrastructure failures?
Search context: The 2016 Census website crash under the Coalition government revealed systemic infrastructure planning issues that hadn't been addressed by the previous Labor government (2007-2013) either. The Census systems were not built to handle simultaneous access from millions of users, a problem that predated the Coalition.
However, a direct Labor equivalent—a government website failure during an emergency requiring welfare access—was not found in available sources. The Labor government (2007-2013) did not face a comparable situation where millions needed simultaneous urgent welfare access.
Relevant parallel: The 2016 Census failure shows that website infrastructure problems affected both parties' governance. The Coalition inherited Census infrastructure but failed to adequately fix it. This suggests the problem is systemic to Australian government IT procurement and planning, not uniquely a Coalition failure. However, the MyGov failure under Coalition governance in 2020 demonstrates that lessons were not learned from 2016.
Balanced Perspective
The criticism is justified:
Robert's claim of a DDoS attack was factually incorrect and misleading, even if unintentionally [1]. In a national emergency with people desperate to access unemployment benefits, the minister should have immediately understood that legitimate user surge, not a cyber attack, was the likely problem. The rapid backtrack (within 2 hours) made the government look unprepared and dishonest, regardless of intent [1].
Anthony Albanese's opposition response—calling it "an incompetence attack" rather than a cyber attack—was apt [1]. Bill Shorten's accusation that Robert "lied" is harsh but reflects the seriousness of misleading public statements during a crisis [1].
Legitimate context and mitigating factors:
However, several factors provide perspective:
Genuine attempt at preparation: The government did increase capacity 10-fold over the weekend, demonstrating an awareness of incoming demand [2]. This was not pure negligence—it was inadequate preparation.
Emergency conditions: During the initial coronavirus panic, predicting the exact surge magnitude was genuinely difficult. A 10-fold increase that still proved insufficient is a planning failure, but not an absurd miscalculation given the unprecedented nature of the crisis.
DDoS alarm system design: The false positive itself reveals the system architecture was not designed for legitimate surge traffic. Modern high-traffic systems should distinguish between attack patterns and legitimate traffic spikes. This is a systems design issue, not necessarily a dishonest claim—Robert may have genuinely believed a DDoS was occurring based on the monitoring alerts [1].
Rapid correction: Robert corrected the statement the same day in Parliament, which shows accountability and transparency, albeit embarrassing [1]. He did not double down on the false claim.
Comparative government responsibility:
The incident reflects broader problems with Australian government IT infrastructure that predate and outlast the Coalition. The 2016 Census failure should have triggered comprehensive infrastructure modernization, but systemic issues remained four years later [2]. This suggests institutional problems in how government procures, designs, and manages IT systems—issues affecting government more broadly.
Key distinction: Whether Robert's statement was a deliberate lie (intentional deception) or a misinterpretation of DDoS alerts (honest mistake based on false alarm) affects the severity assessment. The sources support honest misinterpretation based on false alerts rather than deliberate fabrication.
TRUE
7.0
out of 10
The factual claim that Stuart Robert initially claimed a DDoS attack and then contradicted himself hours later is accurate and well-documented [1][2].
However, characterizing this as "lying" requires establishing deliberate deception. The evidence supports that Robert responded to DDoS detection alarms that were false positives triggered by legitimate traffic [1]. This represents a serious failure in communication and system architecture, but may not constitute intentional deception.
The more accurate framing: Robert made a misleading public statement based on (or claiming to respond to) false DDoS alerts, then corrected it the same day when the actual cause became clear. This is a significant failure in crisis communication during an emergency, but not necessarily a calculated lie.
Final Score
7.0
OUT OF 10
TRUE
The factual claim that Stuart Robert initially claimed a DDoS attack and then contradicted himself hours later is accurate and well-documented [1][2].
However, characterizing this as "lying" requires establishing deliberate deception. The evidence supports that Robert responded to DDoS detection alarms that were false positives triggered by legitimate traffic [1]. This represents a serious failure in communication and system architecture, but may not constitute intentional deception.
The more accurate framing: Robert made a misleading public statement based on (or claiming to respond to) false DDoS alerts, then corrected it the same day when the actual cause became clear. This is a significant failure in crisis communication during an emergency, but not necessarily a calculated lie.
Rating Scale Methodology
1-3: FALSE
Factually incorrect or malicious fabrication.
4-6: PARTIAL
Some truth but context is missing or skewed.
7-9: MOSTLY TRUE
Minor technicalities or phrasing issues.
10: ACCURATE
Perfectly verified and contextually fair.
Methodology: Ratings are determined through cross-referencing official government records, independent fact-checking organizations, and primary source documents.