Fallback When a Channel Goes Down: Manual Blocks and Notices

A channel outage is not the moment to discover you have no manual fallback. Two habits keep a listing sellable while the connection is down.

Last updated: October 12, 2026

A channel can stop sending bookings and you'll keep taking them on the other three. The outage itself isn't the hard part. The hard part is the window where your calendar and a guest's expectation drift apart, and nobody's watching the gap. Two habits close it: block the nights by hand, and tell people before they travel.

Key Takeaways

• An outage stops the sync, not the stay. Your rooms still exist and guests still arrive; only the updates stop arriving.
• Block by hand as soon as you notice. A manual block keeps a night from selling twice while the connection is down.
• Tell guests before they travel, not after. A guest who hears about a change early can plan around it; one who hears late can't.
• Keep the blocks labelled. When the connection returns, you'll want to know which nights you closed and why.
• Reconcile before you relax. The outage ends when the two calendars match again, not when the connection comes back.

What an outage actually stops

A channel going down doesn't stop your guests. It stops the traffic between you and the channel. The listing still shows, the rooms still exist, and someone who booked last week still expects a key.

What stops is the sync. A reservation made on the channel might not reach you. A rate you set in your own system might not reach the channel. The calendar you're reading quietly stops matching the one a guest is booking from.

That gap is where the trouble lives. Two calendars that agree every other day of the year disagree today, and the person deciding whether to book sees only their side. Nothing announces it. There's no alarm and no banner that says the two views have drifted.

So the first thing an outage costs you isn't bookings. It's certainty. You can't trust the calendar you're reading, and you won't know how long that lasts. Treat the connection as unreliable until you've confirmed otherwise.

None of this is dramatic. An outage rarely arrives with a bang. Most hosts notice it a day late, from a guest message that mentions a booking they never saw, or from a calendar that looks a little too empty for the season.

It helps to picture the two sides as two people writing the same day into two notebooks. While the sync runs, both notebooks match. When it stops, each keeps writing, and neither sees the other's page. The longer the gap, the more the two pages disagree.

That's why the fallback matters more than the fix. You can't force a channel to come back, and you can't repair the connection yourself. What you can do is run your side by hand until the two notebooks agree again.

Blocking by hand before you are asked

Manual blocks are your fallback, and they're the reason an outage doesn't have to become a double booking. A manual block is a night you close yourself, directly, rather than trusting a channel to do it for you.

Start with the nights at risk. If a reservation arrived on the channel and you haven't seen it, that night is already spoken for on one side. Block it on the other side so a second guest can't take it. You're not cancelling anything; you're drawing the same night on two calendars until they agree again.

Work in the order the bookings arrived. The most recent reservation is the one most likely to be missing from your side, so check the recent ones first. Then move outward to the near dates, since those are the ones a guest can still book today.

Keep the blocks labelled. A block you can't explain in a week is a block you'll second-guess later. Write why each night is closed and which booking it's covering for. When the connection returns, that note is what tells you which blocks to lift and which to keep.

Don't block more than you have to. Every block is a night you can't sell, so close the ones a booking might already cover and leave the rest open. A cautious host who blocks the whole month has turned a sync problem into an empty calendar.

Set a reminder to review the blocks. An outage doesn't end when the connection returns; it ends when the two calendars match again, and that's a step you have to remember to take.

Write each block so you can undo it. A block with no note is a block you'll hesitate to lift, and hesitation is how a night stays closed for a week after the outage is over. The note is your undo button.

Telling guests before they travel

Guests hate a surprise at the door more than they hate a change. If a booking is at risk because of an outage, the message you send early is worth more than the one you send late.

Say what you know and what you don't. If a reservation is confirmed on the channel but missing from your side, tell the guest the booking stands and you're confirming the details. Don't invent a reason you can't verify. A short, plain note beats a confident one that turns out wrong.

Reach them where they'll see it. The platform's message thread may be the same channel that's down, so use the contact detail on the booking, and keep a copy of what you sent.

Don't wait for certainty before you reach out. A guest who knows a detail is being checked can plan around it. A guest who hears nothing until arrival can't. The message that buys you time is the one sent early.

Match the tone to the size of the problem. A missing confirmation is a note, not an apology. Save the fuller explanation for the case where a stay actually has to change.

Keep a single thread per booking. If two people reach the same guest on two channels, the guest hears two versions and trusts neither.

What to re-check once the channel is back

Coming back online isn't the end of the outage. It's the moment the two calendars have to be reconciled, and that's a job you do by hand.

Compare the nights you blocked by hand against the bookings that arrived. Lift the blocks that were covering for a booking, and keep the ones still protecting a night. A block left standing after the connection returns is a night you've lost.

Then run a plain check of the day: what's arriving today, who's in house, who's leaving, and what the calendar shows for each. LOCALSBNB shows each connected channel's own source price and status in one calendar, and its read-only assistant answers plain questions like today's arrivals, in-house guests, departures and the current state of the calendar. That's how you confirm the two sides agree. Start free at localsbnb.com.

Check the rates as well as the nights. A rate you changed during the outage may or may not have reached the channel, and the calendar will show you which figure is live now.

A rate that's right on your side and stale on the channel is worse than a night that's simply open. The guest sees a price you never meant to offer, and you find out when they book it.

Write down what you lifted and what you kept. A short note closes the loop, and it gives you something to compare against the next time a channel stutters.

FAQ

How do I know a channel is actually down?

The first sign is usually a calendar that stops matching. You'll see a rate or a reservation on one side and not the other. Confirm it against the platform's own status before you act on it.

Should I block every open night during an outage?

No. Block the nights at risk, not the whole month. Every block is a night you can't sell, so close the ones a booking might already cover and leave the rest open.

What if a guest booked during the outage and I can't find it?

Treat the booking as real until the platform tells you otherwise. Contact the guest, confirm the stay stands, and keep the details until the channel reopens and you can match the two records.

An outage is a short window, and the habits that carry you through it are the same ones that keep you calm on a normal day. Watch the calendar, close what you have to, tell people early, and reconcile on the way out. When you want reservations, rates and the calendar in one read, the LOCALSBNB calendar and assistant give you a single place to look — localsbnb.com.

---

This is general guidance for hosts, not legal, tax or insurance advice. How a channel handles an outage, its notices and its records changes by platform and over time, so check the current terms of each platform you use and the current position of your local authority.