AI Risk Wire

Cases › made things up › LR-2026-0690

Google AI overview falsely labelled Canadian musician Ashley MacIsaac a sex offender

Preliminary Why: Publisher not yet named · subject to change

Status: no action reported

Severity moderate
Reported 18 Aug 2026

No source states: loss or records, developer and model, agent tool, could do, deployer, industry.

Severity moderate: Test applied: moderate tier, data or systems of others touched with bounded scope. The source states one named third party (the musician) was harmed and one concert was cancelled by its organizers, a bounded scope; no count of affected parties is stated.

Google's AI overview, a generated summary shown at the top of its search page, stated that Canadian fiddler Ashley MacIsaac had been convicted of sexual offences and was on the national sex offender registry. The source says all of this was untrue. MacIsaac said the claims came from online articles about a different man in Atlantic Canada with the same last name. After a concert was cancelled by organizers who cited the AI summary, he sued Google in the Ontario Superior Court of Justice, seeking $1.5 million. A notice of discontinuance ended the case on July 29, and MacIsaac gave no reason. Google Canada said its summaries change frequently and that mistakes are used to improve the system.

What happened

1 · What it was doingGoogle was running AI overviews, AI-generated summaries shown at the top of its search page, which it began introducing in 2024.
2 · What went wrongThe AI overview stated that musician Ashley MacIsaac had been convicted of sexual offences and was on the national sex offender registry. The source says all of this was untrue.
3 · What it reached or didConcert organizers cancelled a MacIsaac concert and cited the AI summary.

What was done

No source states an action or fix.

Risks

Sorted by rule from the case's fields; not yet read from the sources.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Application

Grounding and fact checks · Human approval for high-impact actions · Output filtering and redaction · People told they are dealing with AI

Evidence

No source states: how it was caught, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off, what was done.

Show the full account: 8 items from the primary sources

What happened, in order

  1. 2024 Google first began introducing AI overviews.
  2. June Google said it would challenge the Munich ruling.
  3. July 29 A notice of discontinuance was filed to end MacIsaac's lawsuit.
  4. December MacIsaac found out about the misinformation after a concert was cancelled by organizers who cited the AI summary.
  5. December Google Canada said its AI summaries change frequently and that mistakes are used to improve the system.

Not dated in the sources:

  • MacIsaac later said the incident caused him deep anxiety in subsequent performances.
  • MacIsaac initiated a civil lawsuit with the Ontario Superior Court of Justice.
  • A Munich court, in a separate case, ruled that Google is legally liable for false information in its AI-generated summaries.
Show every field, with its source and grade

What happened

Earliest source we hold
2026-08-18
D inferred by us from the described behaviour, reason shown
Where its input came from
online articles about a man in Atlantic Canada with the same last name
C one secondary source states it
What went wrong
made things up
C one secondary source states it

Impact

Severity
moderate
D inferred by us from the described behaviour, reason shown
Why this severity
Test applied: moderate tier, data or systems of others touched with bounded scope. The source states one named third party (the musician) was harmed and one concert was cancelled by its organizers, a bounded scope; no count of affected parties is stated.
D inferred by us from the described behaviour, reason shown

Notes on gaps

No year is stated for the December events, the lawsuit or the July 29 filing, so no full dates are given for occurrence or disclosure. No count of affected third parties is stated. The Munich ruling and Air Canada case concern other incidents and were not used for controls or fields.

LR-2026-0690 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON