Skip to Content
logologo
AI Incident Database
Open TwitterOpen RSS FeedOpen FacebookOpen LinkedInOpen GitHub
Open Menu
Discover
Submit
  • Welcome to the AIID
  • Discover Incidents
  • Spatial View
  • Table View
  • List view
  • Entities
  • Taxonomies
  • Submit Incident Reports
  • Submission Leaderboard
  • Blog
  • AI News Digest
  • Risk Checklists
  • Random Incident
  • Sign Up
Collapse
Discover
Submit
  • Welcome to the AIID
  • Discover Incidents
  • Spatial View
  • Table View
  • List view
  • Entities
  • Taxonomies
  • Submit Incident Reports
  • Submission Leaderboard
  • Blog
  • AI News Digest
  • Risk Checklists
  • Random Incident
  • Sign Up
Collapse

Incident 379: Error in Pepsi's Number Generation System Led to Decades-Long Damages in the Philippines

Description: Pepsi's number generation system determining daily winners in its Number Fever promotion in the Philippines mistakenly produced a number held by thousands which resulted in riots, deaths, conspiracy theories, and decades of lawsuits.

Tools

New ReportNew ReportNew ResponseNew ResponseDiscoverDiscoverView HistoryView History

Entities

View all entities
Alleged: D.G. Consultores developed an AI system deployed by Pepsi, which harmed Filipinos.

Incident Stats

Incident ID
379
Report Count
2
Incident Date
1992-05-25
Editors
Khoa Lam
Applied Taxonomies
MIT

MIT Taxonomy Classifications

Machine-Classified
Taxonomy Details

Risk Subdomain

A further 23 subdomains create an accessible and understandable classification of hazards and harms associated with AI
 

7.3. Lack of capability or robustness

Risk Domain

The Domain Taxonomy of AI Risks classifies risks into seven AI risk domains: (1) Discrimination & toxicity, (2) Privacy & security, (3) Misinformation, (4) Malicious actors & misuse, (5) Human-computer interaction, (6) Socioeconomic & environmental harms, and (7) AI system safety, failures & limitations.
 
  1. AI system safety, failures, and limitations

Entity

Which, if any, entity is presented as the main cause of the risk
 

Human

Timing

The stage in the AI lifecycle at which the risk is presented as occurring
 

Post-deployment

Intent

Whether the risk is presented as occurring as an expected or unexpected outcome from pursuing a goal
 

Unintentional

Incident Reports

Reports Timeline

Incident OccurrenceThe Computer Error That Led to a Country Declaring War on PepsiPepsi-Cola's Number Fever Fiasco: How the Media Portrays the Actors of a Crisis
The Computer Error That Led to a Country Declaring War on Pepsi

The Computer Error That Led to a Country Declaring War on Pepsi

mentalfloss.com

Pepsi-Cola's Number Fever Fiasco: How the Media Portrays the Actors of a Crisis

Pepsi-Cola's Number Fever Fiasco: How the Media Portrays the Actors of a Crisis

docs.rwu.edu

The Computer Error That Led to a Country Declaring War on Pepsi
mentalfloss.com · 2018

On May 25, 1992, the Channel 2 News program in Manila, Philippines aired a segment that had been running since February of that year. Each night, the station alerted viewers to the day’s winning number in Pepsi’s Number Fever promotion. Buy…

Pepsi-Cola's Number Fever Fiasco: How the Media Portrays the Actors of a Crisis
docs.rwu.edu · 2021

In 1992, Pepsi created a marketing ploy to increase interest in its products in the Philippines. The game was aptly called “Number Fever,” and participants had to look at the number printed underneath the cap of their soft drink bottle and …

Variants

A "variant" is an incident that shares the same causative factors, produces similar harms, and involves the same intelligent systems as a known AI incident. Rather than index variants as entirely separate incidents, we list variations of incidents under the first similar incident submitted to the database. Unlike other submission types to the incident database, variants are not required to have reporting in evidence external to the Incident Database. Learn more from the research paper.

Similar Incidents

By textual similarity

Did our AI mess up? Flag the unrelated incidents

Kronos Scheduling Algorithm Allegedly Caused Financial Issues for Starbucks Employees

Kronos Scheduling Algorithm Allegedly Caused Financial Issues for Starbucks Employees

Aug 2014 · 10 reports
Amazon Alexa Responding to Environmental Inputs

Amazon Alexa Responding to Environmental Inputs

Dec 2015 · 35 reports
Nuclear False Alarm

Nuclear False Alarm

Sep 1983 · 27 reports
Previous IncidentNext Incident

Similar Incidents

By textual similarity

Did our AI mess up? Flag the unrelated incidents

Kronos Scheduling Algorithm Allegedly Caused Financial Issues for Starbucks Employees

Kronos Scheduling Algorithm Allegedly Caused Financial Issues for Starbucks Employees

Aug 2014 · 10 reports
Amazon Alexa Responding to Environmental Inputs

Amazon Alexa Responding to Environmental Inputs

Dec 2015 · 35 reports
Nuclear False Alarm

Nuclear False Alarm

Sep 1983 · 27 reports

Research

  • Defining an “AI Incident”
  • Defining an “AI Incident Response”
  • Database Roadmap
  • Related Work
  • Download Complete Database

Project and Community

  • About
  • Contact and Follow
  • Apps and Summaries
  • Editor’s Guide

Incidents

  • All Incidents in List Form
  • Flagged Incidents
  • Submission Queue
  • Classifications View
  • Taxonomies

2023 - AI Incident Database

  • Terms of use
  • Privacy Policy
  • Open twitterOpen githubOpen rssOpen facebookOpen linkedin
  • 8b8f151