Live / Lodgify / Incident
Lodgify: Issue affecting Booking.com's API
Lodgify · lodgify.comMajor incidentResolved2026-10-15 19:13 UTC
Public — what happened
Summary
Lodgify reported a major issue on October 15, 2026, starting at 13:20 UTC, in which reservations from Booking.com were not being retrieved properly. The company said the problem originated with an incident on Booking.com's side, and it advised customers who got a booking to review their Lodgify calendar and block off dates manually where necessary. Lodgify monitored the situation and marked it resolved at 19:13 the same day.
Timeline
- Started — 2026-10-15 13:20 UTC
- Monitoring — 2026-10-15 13:20 UTC
- Resolved — 2026-10-15 19:13 UTC · 5h 54m 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 43, 2026, our weekly internet health report.