Hearth Record

Back to Fans

VAGKRI fans

1 report to CPSC, the latest made Aug 6, 2025. A report isn’t a recall.

Watch it to hear when CPSC publishes new reports about it. CPSC’s own search, on saferproducts.gov

Watch and the shortlist are kept with a free account, on every device. Your watch list. CPSC’s own search is on saferproducts.gov.

At a glance

From SaferProducts.gov, released Oct 25, 2026.

  • 1report to CPSC
  • Aug 6, 2025the latest report was made
  • Aug 6, 2025the earliest
  • 0with the company’s comments
Brand
VAGKRI
Maker
SHENZHEN GUIYANG NETWORK TECHNOLOGY CO., LTD dba VAGKRIMakers, importers or sellers, as the reports name them
Product
FansCPSC’s product type: Fans (code 380), in Home Maintenance and Structures: Heating, Ventilation & Air Conditioning

By month

1 report from September 2024 to August 2025; the most in August 2025, 1.
The numbers, as a table
Reports to CPSC by the month each was made, newest first
MonthReports
August 20251

How badly anyone was hurt

  • No one hurt 1 CPSC: Incident, No Injury

As each report says it, in short words; CPSC’s own words are under each.

The reports, as CPSC published them

Reports people made to the U.S. Consumer Product Safety Commission. CPSC publishes each one after sending it to the company named, and doesn’t guarantee they’re accurate. A report isn’t a recall.

Each report is the words of the person who made it, as CPSC published them. The company’s comments, where CPSC published any, are set apart as the company’s own.

Source:

CPSC, SaferProducts.gov public database export. Released Oct 25, 2026. Updated daily.

  1. No one hurt

    Made Aug 6, 2025, sent to the company Aug 11, 2025, published by CPSC Aug 25, 2025

    The product, in the report: VAGKRI Wall Mount Fan, 16 Inch Wall Fan with 5 Blades, 5 Speeds, 8 Hour Timer, 90 Oscillating Quiet Fans with Remote for Home Office Bedroom Living through Amazon.

    I experienced a serious safety incident involving a dangerously defective VAGKRI 16-Inch Wall Mount Fan, which was purchased through a third-party seller on Amazon.

    While the fan was in normal operation, mounted on the wall and running at a standard speed, the blades suddenly broke apart and were forcefully ejected from the unit. One of the sharp, jagged blades struck me in the face. More important though, at the time of the incident, I was seated nearby, and my 1.5-month-old infant daughter was also present in the room, although she was not physically harmed, the loud noise and flying debris startled her significantly. Since the incident, she has shown signs of ongoing psychological distress, including a pronounced fear of loud sounds and frequent emotional outbursts. These symptoms may require professional evaluation and treatment. The debris came extremely close to hitting her, and it could have resulted in a severe injury.

    I initially contacted the seller on May 3, 2025, to report broken blades from the first unit. The seller sent a replacement. The incident described above occurred with the replacement fan. After reporting this to the seller on July 22, they offered only a refund and have taken no further action. Amazon instructed me to return the product, which I did, and I was informed that an investigation would be conducted. However, I have not received any report or follow-up from Amazon regarding the outcome.

    This situation represents a serious product safety concern. The fan appears to have a significant design or manufacturing flaw that presents an ongoing risk of injury to both adults and children. I am requesting that this matter be thoroughly investigated to prevent further harm to other consumers. I have also reached out to product-safety@amazon.com to which I received a “full mailbox” message and it could not be delivered. A full inbox at your product safety department raises serious concerns about Amazons ability to handle active and dangerous consumer safety threats.

    Model
    https://www.amazon.com/gp/product/B0C4HLJWH2?th=1
    Serial number
    https://www.amazon.com/gp/product/B0C4HLJWH2?th=1
    Bought from
    Amazon.com
    Bought
    May 5, 2025
    Where
    Lewisville, Texas: Home/Apartment/Condominium
    Who was involved
    Age 1, Female
    The reporter’s relation to them
    My Child
    As this report names them
    Brand VAGKRI, made or sold by SHENZHEN GUIYANG NETWORK TECHNOLOGY CO., LTD dba VAGKRI
    How badly, in CPSC’s words
    Incident, No Injury

CPSC’s disclaimer

Disclaimer: CPSC does not guarantee the accuracy, completeness, or adequacy of the contents of the Publicly Available Consumer Product Safety Information Database on SaferProducts.gov, particularly with respect to information submitted by people outside of CPSC.

Source:

Word for word, from the disclaimer in CPSC’s export.

Sources

Sources
  • U.S. Consumer Product Safety Commission, SaferProducts.gov public database export.

    Released Oct 25, 2026 and checked Oct 25, 2026. Updated daily. Public domain (U.S. Government work). CPSC asks to be credited, and that no endorsement be implied.

Source:

Reports of harm are from the U.S. Consumer Product Safety Commission (CPSC), on SaferProducts.gov. CPSC does not endorse Hearth Record.

Back to Fans

How to read a record

Four things every record does, shown on an example record made up for this guide.

An example record, made up for this guide

An example nursing home

Made up for this guide: no real place is shown

Not fully inspected in over two years (CMS flag)

11 health citations at the latest inspection cycle

The state average is 14.3.

Source:

CMS, State and US Averages and Health Deficiencies. Released Oct 8, 2026. Updated monthly.

From the homeNone yet. Replies and paid listings aren’t open, and when they open they will sit here, below the record.

1 of 4

Every fact names its source.

Who published it, when, and how often it changes sit beside each fact, with a link to the agency’s own file.

Sign in

A free account keeps your watch list, shortlists, comparisons and saved searches on every device, and can email you when something you watch changes. Browsing never needs one.