Live / Lodgify / Incident
Lodgify: Issue affecting Booking.com's API
Lodgify · lodgify.comMajor incidentResolved2026-10-22 16:40 UTC
Public — what happened
Summary
Lodgify said it was monitoring a problem on Booking.com's side that began at 12:48 UTC on 2026-10-22 and touched several of Booking.com's connections to its system. The company reported that updates to rates and availability, along with messaging and reservations, were affected. Lodgify advised customers who received a reservation to check their calendar and add a closed period if needed. The incident is now marked resolved as of 16:40 UTC, and the company did not describe a specific cause beyond saying the problem was on Booking.com's end.
Timeline
- Started — 2026-10-22 12:48 UTC
- Monitoring — 2026-10-22 12:48 UTC
- Resolved — 2026-10-22 16:40 UTC · 3h 51m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Lodgify against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Lodgify: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Lodgify report →
More from Lodgify
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.