234 incidents on record · 2026HeadlightsIncident reports by Ellie Harris · Melbourne
5 new this weekLibrary last updated 14 October 2026
← The incident library
HD-INC-034
Technology · United States · 2023 · Hallucination & fabrication

Google's Bard Ad Got a Telescope Fact Wrong, and Alphabet Lost 100 Billion USD in a Day

By Ellie Harris · Filed 6 to 8 February 2023

Alleged: Google (Alphabet) developed or deployed the AI system implicated in this incident. Details are drawn from public reports; parties are presumed innocent of any wrongdoing not established by an official finding.

Google's Bard Ad Got a Telescope Fact Wrong, and Alphabet Lost 100 Billion USD in a Day

What happened

It was reported that in February 2023, Google was preparing to introduce Bard, its answer to ChatGPT, when a factual mistake in a promotional advertisement attracted worldwide attention and contributed to a sharp fall in the company’s share price.

The advertisement showed Bard answering a question about discoveries made by the James Webb Space Telescope, including a claim that it had taken the first photographs of a planet outside our solar system. The answer sounded convincing, but it was wrong because the first such image had been captured in 2004, almost two decades before the James Webb telescope was launched.

The mistake was spotted by an astrophysicist and quickly circulated online, attracting particular attention because Google was competing with Microsoft to establish itself as a leader in generative AI.

On 8 February, Alphabet’s shares fell approximately 7.7%, wiping around 100 billion USD from its market value amid wider investor concerns about Google’s AI strategy. Although the inaccurate advertisement was not the only factor behind the decline, it became a highly visible example of the risks associated with presenting AI-generated information as fact.

What made the incident unusual was that the error appeared in Google’s own promotional material rather than in a conversation with an ordinary user, suggesting that a basic factual mistake had passed through the company’s preparation and review process before being published.

What an auditable version would have shown

An auditable system would have recorded whether Bard’s claim about the telescope had been checked against a reliable scientific source before it appeared in the advertisement, including what evidence supported the answer and whether anyone had approved it for publication.

That record would have made it possible to identify whether the mistake came from the model generating an incorrect answer or from the human review process failing to recognise that the information needed checking.

Where the gap was

Headlights identifies overconfidence and a rules-behaviour gap, where people place too much trust in information generated by a system without ensuring it meets the standards expected of the organisation using it.

Google had the expertise and resources to verify a straightforward scientific claim, yet the incorrect answer still appeared in material intended to demonstrate the capabilities of its new technology.

There is a familiar human behaviour behind this failure because information that sounds confident and comes from a sophisticated system can feel more reliable than it actually is, particularly when people are focused on demonstrating what the technology can do rather than questioning where it might be wrong.

The incident illustrates how easily a convincing answer can move from an AI system into a public statement when the people responsible for reviewing it assume that someone else has already checked the facts.

What governance should have looked like

Any organisation publishing AI-generated factual claims should have a clear process for checking important information against independent, reliable sources, particularly when those claims appear in advertising or other high-profile communications.

A VerificationGate could require factual statements to be checked before publication, while a ConductRecord could preserve evidence of which claims were reviewed, the sources used and whether verification was successful.

The wider lesson is that the quality of an AI-generated answer cannot be judged by how convincing it sounds, and even the largest technology companies remain responsible for checking information before presenting it to the public as fact.

Failure Pattern: Google’s Bard generated an incorrect scientific claim that appeared in a promotional advertisement, exposing a failure to verify AI-generated information before publication.

Governance Principle: Organisations should independently verify factual claims generated by AI and maintain records of those checks, particularly when information is being published under the organisation’s name.

The reference implementation of VerificationGate and ConductRecord is open source. It lives at github.com/saffronandindia/headlights-oss, Apache 2.0 licensed and free to install. The repository is public now.

Sources

The mailing list

Fresh incident reports every week. One email to match.

We add new incidents to the library regularly, and send a single short email each week with what's new. The library stays free and open; this is just how you keep up with it.

Sent through Substack. Unsubscribe in one click.

The record

An auditable system would have produced a signed, tamper-evident record the moment this happened: what the system did, the version that did it, the basis it acted on, and the action taken, and Google (Alphabet) could have produced it on demand.

This is the record the system as deployed did not produce in a signed, auditable form.

What this teaches
Capture what happened when it happens
What the system did, the version that did it, the basis it acted on, and the action taken, recorded at the moment, not reconstructed after.
Sign it, so no one has to trust the record-keeper
A tamper-evident entry. Edit it later and the signature breaks. The record does not ask for the benefit of the doubt.
Make it verifiable by anyone
A court, a regulator, a customer's lawyer can check the record themselves, without taking the company, or us, at our word.

Headlights summarises publicly reported AI incidents. All summaries are independently written, attributed to their original sources, and intended for research and educational purposes. Allegations are identified as such until established through official findings.

This report is based on the sources listed above and reflects information available at the time of review; later developments may not be captured. Where a person is described as charged with or alleged to have done something, that allegation is unproven unless a conviction or a court or regulatory finding is stated. Headlights publishes journalism and commentary, not legal advice.

Want to write back?

Direct to my inbox.

ellie@useheadlights.com →