Your Booking.com bookings now showing as cancelled: rest assured, they are not
You have just connected a calendar, and your forthcoming Booking.com bookings are showing as cancelled. Take a breath: nothing has changed for your guests. Here is what is really on the screen, and how to put things back in order.
By the 1calendrier team · Updated 11/08/2026
What is happening to you
Let us start with the essential point: your bookings are not cancelled. No guest has received a cancellation email, no refund has gone out, no stay is lost. What you are looking at is a display problem in your schedule, not a problem with your bookings.
The scenario is always the same. You have just connected calendars, often between Airbnb and Booking.com. You open the Booking.com schedule to check, and there they are: your forthcoming bookings showing as cancelled, or slipping into a section where they have no business being. The panic is immediate, and understandable: on screen, it all looks like a disaster.
At the time of writing (August 2026), several hosts report exactly this behaviour on help forums, just after connecting their calendars. In the cases reported, the bookings were intact. Here is how to check that in two minutes, and then how to set the display straight.
What to do now, in order
1. Look for the truth in the right place: the reservations list
The calendar view is a view, not the reference. The reference is the reservations list in the Booking.com extranet. Open it and check the status of every forthcoming stay: if they show as confirmed, all is well. Open the message thread with one of the guests concerned as well: a real cancellation always leaves a dated trace there. No trace, no cancellation.
If a doubt remains about one particular stay, ring the partner support line and ask them to confirm the status. But in almost every reported case, this step is where it ends: the bookings are healthy.
2. Identify what you have just connected
The trigger is nearly always an import added recently. In the Booking.com extranet, open the calendar synchronisation section and note every imported calendar: which one, added when. If the display went wrong in the hours following an addition, you have your suspect.
3. Open the imported calendar in a browser
Copy the link of the calendar that Booking.com is importing and open it in a new tab. You will get plain text: every held period appears there with its dates and a title. Look for your own Booking.com bookings: the same arrival and departure dates as the stays that are displaying badly.
If you find them, the cause is established: Booking.com is importing a calendar that contains its own bookings. This happens when the imported calendar was itself built from the Booking.com calendar: a Google Calendar that gathers everything, a personal website, or another platform that exports again what it imports. Booking.com then receives its own bookings as an echo, and the schedule lays two versions of the same stay on top of each other. That loop is taken apart in calendar conflicts between Airbnb and Vrbo: it is exactly the same one.
4. Disconnect the import at fault
Remove the import that is sending Booking.com its own bookings back. Wait for one reading cycle: Booking.com states that it reads imported calendars again every 2 hours (official partner help pages, consulted in August 2026), and the Import now button in the extranet lets you force that reading without waiting. Then check the schedule again. In the reported cases, the display returns to normal once the echo is cut.
Do this at a quiet moment: while the import is off, the held dates coming from that calendar disappear, and those dates become bookable again on Booking.com until you reconnect.
5. Reconnect properly
The rule for a sound set-up fits in one sentence: each platform imports the calendars of the others, and never a calendar that contains its own bookings. In practice: Booking.com imports the Airbnb calendar (the one from Airbnb directly, not an intermediate calendar that mixes everything together), and Airbnb imports the Booking.com calendar. The full step-by-step is in synchronising Airbnb and Booking.com.
6. If no import is to blame
There remain rarer cases where the display goes wrong without any echo: a passing incident on the platform, a booking moved by the guest, a unit reconfigured. If the reservations list is healthy and no imported calendar contains your Booking.com stays, wait 24 hours. If the display is still wrong, contact partner support with your screenshots: at the time of writing, this sort of incident is settled on the platform's side.
Why it happened
A platform's schedule lays two things on top of each other: what it sells itself, and what it imports from other calendars. When the same dates arrive through both channels, the platform has to choose how to display them. Judging by how Booking.com behaves at the time of writing, that duplicate can show up as a misleading reshuffle on screen, including the famous impression of cancelled bookings.
The important point: at no moment is the booking itself touched. An imported calendar cannot cancel a stay. All it carries is dates held or free. That is also why the panic, legitimate though it is, can subside quickly: the worst this incident can produce is a false display, and a false display can be repaired.
A confused display can nevertheless hide a real outage alongside it: a link that has stopped answering, an import switched off. If your calendars are showing other signs of weakness, the seven classic causes are in why your Airbnb calendar has stopped synchronising.
How to avoid going through it again
This incident carries a lesson: a calendar set-up can send a platform its own bookings back, and nobody warns you. Free calendar mergers change nothing: most of them send on everything they receive, in a single calendar identical for everyone. The structural answer is to go through a central calendar that produces one output per platform: the output meant for Booking.com leaves out the Booking.com bookings, and the one meant for Airbnb leaves out the Airbnb bookings. The echo becomes impossible by design, however many calendars are connected.
That leaves the question of trust: how do you know that everything is travelling properly, today and next month? The manual test is in how to check that your calendars are really synchronised. Continuous watching does it for you every 30 minutes, alerts you when a link stops answering or when two bookings overlap, and shows you on a health screen when each calendar was last read. You will no longer have to guess what your schedule is trying to tell you.
Frequently asked questions
Should I warn my guests?
No. As long as the reservations list in the extranet shows them as confirmed, they have received nothing and see nothing unusual. Warning them would only worry them about a display problem that does not concern them.
Can removing a calendar import cancel something for real?
No. A calendar import neither creates nor cancels a booking. It adds or removes held dates in the display. Bookings stay on the platform where they were taken.
Can the same thing happen on Airbnb?
The mechanism exists on every platform: an imported calendar containing the same dates as the local bookings can confuse the display. What you see varies: dates held twice, greyed-out mentions, conflicts flagged. The way to diagnose it stays the same.
How long before the display looks normal again?
Allow at least one reading cycle after the correction: Booking.com states that imported calendars are read again every 2 hours (official help pages, consulted in August 2026), but give it up to 24 hours before drawing conclusions. The Import now button on the extranet's synchronisation page forces a fresh reading without waiting.