"Airbnb (Not available)" dates: what your exported calendar carries without telling you

What is happening to you

Dates are blocked on Booking, Abritel or your diary, with a mention such as "Airbnb" or "Airbnb (Not available)". You open your Airbnb calendar: no booking on those dates. You look for a block you might have placed: nothing visible. Yet the dates really are closed to sale on the other side, sometimes for whole months.

The mystery has a simple explanation: the calendar Airbnb exports answers one question only, "can this day be booked?". Everything that makes a day unbookable appears in it as a block, whether it is a genuine booking or a mere setting. The platforms that import this calendar make no distinction whatsoever: they block everything they receive.

The good news: you can see exactly what Airbnb exports, in two minutes, with no tool at all.

What to do now: read your own export

1. Open your Airbnb calendar link in a browser

Get the calendar link of your listing (calendar connection section, "Export calendar") and open it in a new tab. You get plain text. Do not be put off: each period takes up a small block of a few lines, like this one.

BEGIN:VEVENT
DTSTART;VALUE=DATE:20260901
DTEND;VALUE=DATE:20270301
SUMMARY:Airbnb (Not available)
END:VEVENT

In plain English: the DTSTART line gives the first day, the DTEND line gives the day after the last day, and the SUMMARY line gives the title of the period. That is all you need to be able to read.

2. Tell the two families of titles apart

As you go through the text, you will see only two large families:

• "Reserved": a genuine booking. It is sometimes accompanied by a booking code and the address of a guest record, never by a name or an amount.
• "Airbnb (Not available)": everything else. A day that cannot be booked and is not a booking. These are what English-speaking forums sometimes call "non-reservation events": events that block without selling anything.

Each date blocked opposite on Booking or Abritel matches one of these blocks. You now know which ones are stays and which ones are parasites.

3. Identify each "Not available" block

Three origins cover almost every case:

The booking window. If your listing limits bookings to 6, 9 or 12 months, Airbnb exports everything beyond that as one single long unavailable period: the behaviour is documented by several syncing tools that read these exports daily (Beds24, Cloudbeds, observed in August 2026). It is suspect number one when a block runs over whole months, of the "from March to September next year" kind. It is not a fault: it is your own setting, sent out as it is to every platform that reads you.

Your manual blocks. The dates you closed yourself (building work, family, a weekend kept for direct sales) leave in the export under the same title. That is usually intentional: those dates must be closed everywhere. But a block placed a year ago and forgotten stands out very clearly in this text.

Airbnb's automatic blocks. Airbnb's policy provides that the dates of a stay cancelled by the host remain blocked in the calendar, unless the platform accepts the circumstances. Hosts also report dates frozen around a pending or expired booking request, or during certain checks (cases reported on help forums, consulted in August 2026). All of that leaves in the export like any other block. If a block matches neither your window nor a block you placed, that trail goes through Airbnb support.

4. The Abritel cousin: provisional bookings

Abritel has its own parasite, and that one is documented in black and white by the platform. When exporting the calendar, Abritel/Vrbo offers an option to "include provisional bookings": if it is ticked, pending requests with no confirmed payment appear in the exported calendar as blocked dates. The official Vrbo help even recommends keeping that option for private diaries, not for other booking sites (observed in August 2026). The reading principle is the same: open the Abritel calendar link in the browser (replace webcal:// with https:// if needed) and look at the title of the periods. If blocked dates match requests that were never confirmed, deal with those requests on the Abritel side, or recreate an export link without the option: the block will disappear at the next cycle. The case of a calendar massively blocked by Abritel has its own guide: Abritel or Vrbo blocking dates wrongly.

5. Fix it at source, then wait for one cycle

Once each block has been identified: adjust the booking window if it is the cause (and apply the same length everywhere), lift expired manual blocks, deal with provisional requests, contact support for the automatic blocks. Platforms re-read calendars in cycles of the order of 2 to 3 hours: Booking announces a re-reading every 2 hours and Airbnb an update every 3 hours (official help pages, consulted in August 2026). Conclude nothing before that. If your set-up between platforms is recent or improvised, take the opportunity to redo it properly with the guide on connecting Airbnb and Booking.

Why Airbnb exports these blocks

This is not a defect, it is a design choice. The exported calendar serves one purpose: preventing a day that cannot be booked on Airbnb from being sold elsewhere. For that purpose, putting everything in the same bag is efficient: booking, setting or freeze, it does not matter, the day is closed. What is lost along the way is the why. The title "Airbnb (Not available)" is the only trace left, and it distinguishes nothing.

The format itself does not help: it carries dates and titles only. No reason, no status, no shade of difference between "sold", "closed by choice" and "frozen by the platform". The other blind spots of the same format (rates, minimum stay, limited horizon) are listed in what iCal will never sync. And when these vague blocks start circulating between platforms that re-import one another, they can come back as an echo: that is the loop of Airbnb and Vrbo calendar conflicts.

How to avoid going through this again

You now know how to read an export, and that is genuine diagnostic power. But reading it again every week to watch what travels between your platforms is no way to live.

Two things change the situation for good. First, a central view that reads all your calendars and shows each period with its origin and its title: you see at a glance which calendar is blocking which dates, without opening a single plain text file. Then, and above all, outputs filtered by recipient: that is the difference with a free merging tool, which forwards everything it receives exactly as it comes, parasite blocks included. A central calendar builds an output for each platform that contains only what that platform needs to know, and never sends a platform back its own bookings or the blocks it exported itself. Ghost blocks stop spreading from one neighbour to the next. Add an automatic check every 30 minutes with an alert in the event of an outage or an overlap, and the content of your exports stops being a mystery to be solved.