Australian racing and wagering giant Tabcorp has been fined AU$1 million (US$646,000) by the Victorian Gambling and Casino Control Commission (VGCCC) for failing to comply with two directions issued during an investigation into a major system outage. The fine is the largest ever imposed by Victoria’s regulator on Tabcorp.
The VGCCC said Tuesday that the fine was linked to a major system outage during the 2020 Spring Racing Carnival and reflects Tabcorp’s repeated failure to comply with Commission directions to provide information concerning the outage, which left Tabcorp’s Wagering and Betting System (WBS) unavailable for approximately 36 hours.
“We will not tolerate licensees that are not forthcoming and cooperative when the Commission investigates,” said Commission Chair Fran Thorn.
“The Commission had to use its compulsory powers and issue directions because Tabcorp did not provide the information we required about the business continuity and disaster recovery capability of its systems. It is Tabcorp’s failure to comply with these directions that has led to the fine announced today.
“All entities we regulate – no matter how big or small – have an obligation to be open and honest with the Commission and responsive to its lawfully issued directions. We will not tolerate attempts to frustrate our investigations.”
Providing further detail on the incident in question, which occurred on Saturday 7 November 2020, the VGCCC said there is an obligation under the Wagering and Betting Licence and Agreement for the WBS to be continuously available.
The VGCCC’s predecessor, the Victorian Commission for Gambling and Liquor Regulation, commenced investigating the outage and issued directions after Tabcorp failed to voluntarily provide adequate information about the outage to the regulator. Tabcorp’s conduct during its dealings with the VGCCC over the course of the investigation and in response to the directions impacted the VGCCC’s ability to understand the cause of the major outage and gain confidence that it would not recur, the regulator said.
The VGCCC found Tabcorp did not comply with the first direction because it failed to produce a response that – in either form or substance – confirmed the WBS business continuity and disaster recovery arrangements established after the outage were “fit for purpose” to deliver the “continuously available” performance requirement.
Tabcorp was found to have failed to comply with the second direction by submitting a compliant report four months after the deadline.
RelatedPosts
