Check if it's actually broken
If you have not set up this connection yet, start with the Airbnb and Booking.com calendar sync guide; this page assumes the connection already exists and has stopped behaving as expected. In the Extranet, open Rates & Availability, sometimes shown as Calendar & pricing depending on your account, then Sync calendars, per Booking.com for Partners' own help article on syncing calendars to third-party calendars. Each imported calendar has its own Refresh option next to it, use it to force an immediate pull instead of waiting for the automatic cycle, and check the status reads OK rather than Activating or an error.
Re-export the link from the source platform, Airbnb calls it Sync calendars under Calendar, then Availability, Vrbo calls it Export calendar under Calendar, then Settings, and re-import the fresh URL into Booking.com. If the old link had expired, been replaced, or was only partially copied (a common mistake on mobile, since the full .ics URL is long), this fixes it immediately. Full steps for the Booking.com side are in the Booking.com export-link guide.
Check how recently the booking or block happened elsewhere. If it was within the last few hours, give Booking.com's next automatic fetch time to catch up before assuming the connection is broken; this is the most common false alarm.
- 9:00 PMGuest books on AirbnbAirbnb calendar updates instantly
- 9:00 PM to 11:00 PMLag windowBooking.com has not pulled the change yet
- 11:00 PMSecond guest books on Booking.comSame room, same night, still shown open
- Next refreshBooking.com finally updatesToo late. Both bookings already exist.
Free iCal sync refreshes on each platform's own schedule, typically every few hours, not instantly. Real-time sync closes this window to seconds.
Three causes that look like a broken sync but are not
A stale export URL. If you deleted and recreated a listing, merged room types, or a platform regenerated the link for security reasons, the old URL other platforms are still importing stops updating, silently. Every destination that imported it needs the new one re-pasted in, not just the one you noticed the mismatch on.
A feed pointed at the wrong room or rate. If your property has more than one room type on Booking.com, each can have its own export calendar; importing the wrong one means one room stays perfectly in sync while another looks broken, which reads as "sync is not working" when only one room actually is.
Fetch-interval lag mistaken for breakage. This is the most common one: nothing is actually wrong, Booking.com just has not run its next automatic pull yet. Airbnb states in its own Help Center that a connected calendar updates roughly every three hours (Airbnb Help article 99, more detail in the how-often-does-Airbnb-sync-iCal guide); Booking.com's Extranet help articles describe the fetch as automatic without naming a fixed interval, so there is no published number to check your wait time against on that side.
If it keeps happening
A one-off delay right after a recent booking is normal for free iCal sync on any platform, not just Booking.com. A recurring gap, nights staying open on Booking.com well after being booked elsewhere, week after week, is the structural lag of iCal-based sync, not something re-pasting the link fixes again each time.
At that point, the fix is real-time sync through a channel manager, which connects to Booking.com through its direct API instead of a pulled calendar file, closing a booking on every platform within seconds rather than on Booking.com's next fetch cycle. That is a paid step up from iCal sync; getfursat's free tier stays iCal-based, book one, block the rest, across Airbnb, Booking.com and Agoda for up to 2 listings per property, at no cost, no card, no subscription.