The 48 Hours After a Channel Outage

The outage itself is rarely the expensive part. The two days after it are, because that is when double bookings and missed cancellations surface.

Last updated: November 2, 2026

A channel outage doesn't usually cost you the hour it happens. It costs you the two days after, when a night still reads open on one channel and is already sold on another, or a cancellation that never arrived turns into a guest at a door. The work in those days is comparison and paperwork, not panic: read what each channel says, write the times down, and capture the screen before you correct it.

Key Takeaways

• The expensive hours come after the fix. A connection that's back isn't a calendar that's correct, and the gap between the two is where double bookings live.
• Work from status, not memory. Each channel shows its own rate and status beside the night, so a night that looks open in one column can be sold in another.
• Write the times down as you go. A timestamp is the one detail nobody can reconstruct later, and it's the only thing that turns a list into a sequence.
• Two records cover it. A running log of what you saw and when, plus screenshots with a clock in them, taken while the state is still wrong.
• "Connected" is a starting point. It tells you the pipe is open. It doesn't tell you the two sides agree, and only a night-by-night pass does.

What actually goes wrong after an outage

The outage itself is quiet. Screens load, the calendar looks like a calendar, and on the channel side bookings keep arriving. Then the connection comes back, and the trouble starts — because a reconnected pipe doesn't restore the truth. It restores the pipe.

Three failures surface in the next two days, and all three share a shape: one side moved while the other was blind.

The first is a booking that never landed. A guest books on one channel during the window. The reservation exists there and nowhere else, so the night still reads open everywhere else, and it will sell again. You hear about it from the second guest, usually by message, usually late in the evening.

The second is a cancellation that went the wrong way. Either the night stays blocked after the guest cancelled, and you lose a sellable night, or it reopens on one side and not the other. The first costs money quietly. The second costs money loudly.

The third is a rate that snaps back. You changed a weekend rate during the outage. When the connection resumed, the channel picked up the calendar's older value and overwrote yours. Nothing warns you. The night sells at the old price and the guest is delighted.

None of these is visible from a single screen, and that's the whole point. You're no longer looking for a broken connection. You're looking for a disagreement between two records of the same night.

Hour by hour, in order

Resist the first instinct, which is to fix something. The state you're about to overwrite is the only evidence you'll ever have of what went wrong, so spend the first hour reading.

Hour one: read and capture. Open the calendar and go channel by channel across the window the outage covered. For each night, note what each one says: booked, open, blocked. Take a screenshot with the system clock visible. Do all of that before you touch a rate or block a date.

Hours two to four: reconcile, one night at a time. Four combinations matter. Sold on two channels is a double booking and it jumps the queue. Sold on one and open on another is invisible until it isn't. Blocked on one and open on another costs you a night you could have sold. Same night at different rates on two channels is the quiet one, and the one you'll forget.

That comparison is the whole job, and it goes faster when each channel's own rate and status sits beside the night instead of behind a separate login. localsbnb.com connects Airbnb, Booking.com, Agoda and Trip.com to one calendar, so the night you're checking has four columns next to it rather than four browser tabs.

Then the calls. A double booking needs a person inside the hour, because one of the two guests may already be travelling. A lost cancellation can wait until you've confirmed it's actually lost. A rate mismatch can wait for the morning, as long as you've written it down.

Day two: watch the arrivals, not the screens. The failures that hurt are the ones that reach a doorstep. Two guests with the same code for the same lock is a five-minute problem while they're still in the hall and a much longer one once bags are inside.

The two records to keep

First, a log. Not a long one. Time, channel, night, what you saw, what you did, who you told. Twelve lines will usually cover a two-day incident, and the value isn't the prose — it's the order. When somebody later asks why a night sold twice, "the connection dropped on Tuesday and came back on Wednesday" isn't an answer. "At 09:14 the channel showed the night open; at 09:20 it showed it booked" is.

Second, screenshots with a clock in them. Take them while the state is wrong. A screenshot taken after the repair shows a system that looks fine, which in a disagreement is worse than useless: it's evidence for the other side. Name each file with the date, the channel and the night it covers, and keep the original as it came out of the device.

The two records do different jobs. The log gives sequence, screenshots give state. A log without screenshots is your account of events. A screenshot without a log is a picture with no order. Either alone is thin; together they answer almost every question that arrives afterwards, including the ones from your own guest.

Keep both until the stays involved are finished and any claim you've raised is closed. Keep them longer if the channel's terms allow a longer window, and check those terms rather than assuming them.

How to stop it repeating

Three habits, none of which needs new software.

Check one date, weekly. Pick a night two weeks out and confirm three things: the night reads the same on every channel, the rate matches, and the blocked nights are blocked everywhere. Four minutes, and it catches most drift before a guest does.

Freeze rate changes around an outage. If a connection drops, leave rates alone until the state is clean. Otherwise you're writing into a system that's about to overwrite you, and you'll spend the next morning not knowing which version is live.

Treat "connected" as a starting point, not an all-clear. A status that says connected tells you the pipe is open. It doesn't tell you the two sides agree, and only the night-by-night pass tells you that.

FAQ

How do I know if a night was actually double booked?

Two confirmed reservations for the same night in the same unit. Check both channels' reservation lists rather than the calendar alone, because the calendar shows the status a channel reports — a booking that never landed won't appear there at all. Compare arrival dates and guest names, then write the times down.

Should I cancel one of the two bookings straight away?

Only after you've compared both. One guest may already be travelling; the other may be days out. Which booking you keep is your commercial decision, and the terms attached to each one set out your options. What matters is that the guest hears it from you before they reach the door, not from a lock that won't open.

How long do I keep the screenshots?

Until the stays involved are over and any claim you've opened is closed, and longer if the channel accepts evidence for longer. Those windows differ by platform and they change, so read the current terms instead of relying on what applied last year.

An outage is a bad hour. The two days after it are a reading exercise: four channels, one night at a time, with a clock in the corner of every screenshot. localsbnb.com holds those four channels in a single calendar; the reading, and the calls, stay with you.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Connection behaviour, platform terms and the evidence each channel accepts change without notice. Confirm the current rules and the current terms of each platform you use before you act.