As a software person I can tell you that this is probably a database corruption problem. It may or may not be affecting anyone else. Checking if it is affecting others is a good first step, though. If a lot of people are experiencing it, Airbnb will be under more pressure to fix it. First-level customer service won’t have a clue about any sort of resolution, though, unless engineering determines the problem, and hopefully provides some kind of guidance on what to tell customers about the problem, when it will be fixed, etc.
I’ve seen various wacko things happen on the Airbnb platform over the past year, and I always call CS when it happens. Most of the time they have been aware of the problem, as others have already reported it. If that’s the case, they usually tell me it will be fixed soon, and it usually is.
If it’s a problem specific to your data in the database, though, you may have to try to get past the first-level CS. It’s important to keep your cool, and work with the first-level to get your case escalated. At the second or third level, they will be able to examine the DB, and at least provide some sort of temporary fix. Then comes the hard part for them of trying to determine what caused the problem in the first place.
Good luck, I hope your problem is fixed soon.