Update OverviewLead
Booking.com B.V.'s release of version 68.1 for its iOS app on July 17, 2026, has prompted a sharp drop in user sentiment. The update coincides with a rise in complaints about unhonored cancellations and fraudulent listings, fueling concerns over platform safety and financial security.
Vague Release NotesRelease Summary
The official App Store release notes for version 68.1 offer little insight, stating only that the update contains "several bug fixes and performance improvements." No new features, redesigns, or specific removals were announced.[1] The publisher's API changelog for Q2 2026 similarly details backend fixes for reservations and payments but does not identify any front-facing change that would explain the sudden negative user reaction, suggesting the problems may stem from operational or policy enforcement issues rather than a software bug.
Cancellation FailuresBreaking Changes
The primary driver of the backlash appears to be a breakdown in core platform functions, particularly cancellations and listing integrity. Post-update reviews are dominated by themes of failed cancellations and unresolved financial disputes. One 1-star reviewer on v68.1 stated, "Upon arrival to the hotel I was charged for both rooms; hotel said they never received the cancellation. It’s been two months now, I’m short 600$." Another user reported, "The Booking people tell lies about contacting the property to cancel reservations. The property has not heard from Booking and had me as a no show!" These reports indicate a systemic failure in communication between the app, users, and hotel partners.
Fraud and SafetyRoot Cause
The surge in complaints about fraud and safety in v68.1 reviews appears connected to a wider security issue. In April 2026, Booking.com confirmed a data breach where hackers accessed customer reservation data by compromising its hotel partners' accounts.[3] This stolen information allows scammers to create highly convincing phishing attacks.
This context aligns with user experiences shared on community platforms. A discussion on Reddit shows one user identifying a fraudulent Milan listing by cross-referencing GPS coordinates, which pointed to a different part of Italy entirely. Archived.
This context aligns with user experiences shared on community platforms. A discussion on Reddit shows one user identifying a fraudulent Milan listing by cross-referencing GPS coordinates, which pointed to a different part of Italy entirely. Archived.
Sentiment ShiftUser Reception
The negative sentiment shift is stark when comparing reviews before and after the update. Prior to v68.1, many 5-star reviews praised the app's convenience, with one user on v68.0 noting, "Every booking I’ve made , I have had no issues with!" After the July 17 release, the tone soured dramatically. The average rating fell by 0.7 stars, from 3.73 to 3.03, based on an analysis of 66 reviews for each version period. This drop reflects the erosion of trust, as users report feeling unprotected from financial loss and safety risks.
Expert VerdictExpert Verdict
The issues highlighted by the v68.1 backlash pose a serious reputational risk for a platform with over 3.1 million US downloads in the last 30 days. The problem does not appear to be a simple app bug that a hotfix can resolve. Instead, it points to a deep-seated operational and security failure in vetting listings and managing partner access.
To restore trust, Booking.com will likely need to address these systemic issues publicly and implement more stringent verification and support protocols. Without a clear response, the platform may see continued negative reviews and a potential loss of users to competitors perceived as more reliable.
To restore trust, Booking.com will likely need to address these systemic issues publicly and implement more stringent verification and support protocols. Without a clear response, the platform may see continued negative reviews and a potential loss of users to competitors perceived as more reliable.