First of all, we would like to apologize for all the problems this issue caused to you. This was our failure and we’ll do as much as we can to prevent anything similar from occurring again. Here is a full postmortem describing the root causes and solutions we will put in place.
A feature update to restrictions in Mews Commander at 11:45 UTC on 21st October introduced a restrictions bug that was fixed at 13:19 UTC on 22nd October. For 1 day, 1 hour, and 24 minutes any restrictions created in Mews were sent to the channel manager incorrectly.
At 10:31 UTC on 22nd October, the bug was reported by our Customer Care team. Our developers immediately built and deployed a fix. And resent correct restrictions to all channel managers for all properties.