iCal sync delay on Airbnb: why your calendar is hours late

A guest books your villa on Booking.com at 10:05. You get the email, you relax, and you assume Airbnb now shows those nights as taken. It does not. Not yet. Until Airbnb next reads your Booking.com calendar link, the same nights are still open to anyone searching Airbnb. That gap is the whole story of iCal sync delay on Airbnb and every other site that imports calendar links.

Most hosts know iCal is "a bit slow". Few know how slow each platform says it is, who decides the timing, or why pressing a sync button on one site often does nothing for the other. This guide uses the platforms' own help pages, checked on 16 October 2026, to answer those questions with real numbers where they exist.

If you are still deciding between calendar links and a direct connection, read iCal vs channel manager first. This post assumes you already use iCal and want to understand, and shrink, the delay.

How often each platform refreshes an imported iCal feed

The key rule: the site that imports the link sets the schedule. Your Booking.com feed can be perfectly up to date, but Airbnb only learns about a new booking when Airbnb decides to fetch it. Here is what each platform publishes about its own imports.

Sources: Airbnb Help, article 99, Booking.com Partner Help on calendar sync, Agoda Partner Hub on calendar connections.

A few details from those pages matter in practice:

• Airbnb says that if you connect several calendars, they may update at different times, and it shows the last update time for each one. It also says it can only request updates from the other website so many times. Go over that limit and you wait for the next automatic update.
• Booking.com states plainly that calendar sync does not happen as bookings come in, and that reservations made elsewhere "won't sync immediately". Its FAQ names double bookings as a possible result.
• Agoda does not give an interval at all. If a room type goes from one room to several, Agoda says the calendar connection may be deactivated automatically.

Other sites have their own schedules. If a platform does not publish one, treat it as unknown and test it yourself (see below), rather than assuming it matches Airbnb.

Why "sync now" doesn't fix the other side

This is a common misunderstanding. A booking lands on Airbnb. You open the Airbnb calendar and press Refresh, expecting Booking.com to update. Nothing changes on Booking.com.

That is because each button only pulls into the site you are on:

• Airbnb's Refresh pulls other calendars into Airbnb.
• Booking.com's Import now pulls other calendars into Booking.com.
• Agoda's Refresh connections pulls into Agoda.

No button pushes your new booking out. Your exported link is just a file waiting to be read. So the rule is simple: when a booking arrives on site A, go to site B and C and press their import buttons. Pressing anything on site A does nothing for the others.

Two more traps:

• Airbnb limits refreshes. If you hammer Refresh on a busy day, Airbnb may stop accepting manual requests until the next automatic update.
• Chains are unreliable. Import each site's link directly into every other site. Do not count on a block travelling from A to B and then on to C. The platforms don't document that a site re-exports dates it imported, and Airbnb itself says blocks you set on another calendar "may or may not" appear.

iCal sync delay on Airbnb: the risk window in numbers

Here is the math for one hypothetical two-bedroom villa in Canggu, listed on Airbnb and Booking.com, linked by iCal both ways.

A guest books on Booking.com at 10:05. Airbnb's last automatic pull of your Booking.com feed was at 09:00, so the next one is due around 12:00. From 10:05 to 12:00, nearly two hours, Airbnb still sells those nights. If Airbnb had pulled at 10:00, the window would be almost three hours.

Now reverse it. A booking lands on Airbnb. Booking.com imports every two hours, so the window there is up to two hours.

Three things follow from this:

• The worst case equals the importer's interval. Up to 3 hours open on Airbnb, up to 2 hours on Booking.com, unknown on Agoda.
• On average you are exposed for about half the interval, because a booking lands at a random point between two pulls. Half of three hours is still ninety minutes.
• Every extra channel adds its own window. With three sites, each booking opens a gap on two other sites at once, each on its own clock.

The window only hurts when someone else books the same nights inside it. That is why the same setup feels fine in May and fails in late December, during Songkran in Phuket, or on a long weekend in Da Nang, when last-minute searches for the same dates pile up.

How to shrink the window

You can't change a platform's schedule. You can change what you do inside it.

What about buffer nights? A blocked night between stays protects your turnover, not your calendar. It does not stop two guests booking the same night inside the iCal window. Airbnb's help page notes that nights blocked by preparation time and advance notice are included in what it exports, so those settings travel. But they don't make anything arrive sooner.

When to switch to an API channel manager

iCal stays workable for one or two single-unit listings on two channels in a quiet season. Consider a direct connection when:

• You sell more than one identical unit. Booking.com and Agoda calendar sync is only available for one unit per room type, so iCal is not even an option there.
• You sell on three or more sites, so each booking opens two or more windows.
• Peak season brings same-week bookings and you can't watch every email.
• A double booking has already cost you a day of apologies and rebooking.

A direct connection does not wait for the other site's pull. Your software sends the change to each channel through that channel's own connection. There is still a short processing gap, so it is not perfect, but you are no longer waiting hours for someone else's schedule. Our guides to the Airbnb channel manager and Booking.com channel manager explain how those connections work on each site.

How Santara AI handles calendar delay

Santara AI replaces both the PMS and the channel manager, and it uses direct connections to channels, not iCal feeds. It does not offer iCal import or export as a feature.

• One calendar per room is the source of truth. Every connected channel is fed from it. See how the calendar works.
• Bookings come in, availability goes out. New bookings, modifications and cancellations from every connected channel land on the same calendar, and a booking on one channel lowers availability on all the others. Nobody has to press an import button.
• More than dates is sent. Availability, nightly rate, minimum stay, maximum stay, closed to arrival, closed to departure and stop sell go to connected channels.
• Updates are queued with retries. If a channel rejects an update, it is recorded, not silently dropped.
• Unit count caps availability. A one-unit room can never be offered as two.

Airbnb, Booking.com, Agoda, Expedia, Trip.com, Traveloka, Tiket.com, Google Vacation Rentals and the rest of the 54 channels connect from the app. See all integrations.

FAQ

Keep reading

• Airbnb and Booking.com without double bookings
• Switch channel manager without losing bookings
• Agoda channel manager guide

Your first 3 months are free.