Live / Lodgify / Incident
Lodgify: Booking.com incident affecting the connection
Lodgify · lodgify.comCritical outageResolved2026-11-04 13:36 UTC
Public — what happened
Summary
Lodgify said an ongoing problem on Booking.com's side began affecting its whole Booking.com connection at 11:13 UTC on 2026-11-04, covering reservations, rates, availability and messaging. It advised customers who received a reservation during this time to check their calendar and add a closed period if needed. At 13:01 UTC Lodgify said Booking.com had confirmed its issue was resolved, and that it was refreshing the connection so exported data would be fully synchronized. The incident was marked resolved at 13:36.
Timeline
- Started — 2026-11-04 11:13 UTC
- Investigating — 2026-11-04 11:13 UTC
- Monitoring — 2026-11-04 13:01 UTC
- Resolved — 2026-11-04 13:36 UTC · 2h 23m 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 46, 2026, our weekly internet health report.