Ransomware Attack Doesn’t Qualify as Extenuating Circumstances?

My family booked a trip in the mountains for North Carolina. Three days before our trip, the Colonial Pipeline was hacked and held for ransomware. This lead to a gas shortage and state of emergency that was declared in the state. We contacted Airbnb customer service to see if we could cancel our trip due to the state of emergency and the fact that we wouldn’t be able to make it to our destination. They told us they would look into it.

We reached out to them every day for five days, and continued to be told they were looking into it. Finally, after our trip was scheduled to be over, they came back and said it wasn’t covered under the extenuating circumstances policy but wouldn’t tell us why, even though a government-declared state of emergency is clearly listed as part of the policy. We asked for a manager to give us a call, so that they could give us a better explanation.

Instead of a call, a manager that was based in Europe emailed us to let us know that the decision was final and that she couldn’t call us in the U.S. because of the time zone difference. We asked for a manager located in North America or more specifically in the eastern time zone. She came back and said if we want to talk to someone, we can call the customer service line again and start over with a new ambassador. We still believe that our claim falls under the extenuating circumstances policy and would really like to talk to someone that understands why the decision was made to deny the claim.