Root cause:
Memory shortage on one of the servers caused bookings from OTAs not to be created on the internal booking system.

What happened:
Bookings from OTAs were taken by the channel manager but were not translated into bookings on TrekkSoft.

What we did:
Our developers pinpointed the specific services that were affected and were not performing correctly. These services were restarted and this solved the issue.

The consequences:
Most bookings taken during the down time were created on TrekkSoft after the issue was resolved. Only bookings for activities that already took place, or have meanwhile run out of seats, were not created on TrekkSoft. Providers receive email notifications about these failed bookings and should check their email inboxes. Refunds for failed bookings through the OTAs should be made by providers through the OTAs.

We apologize for the inconvenience.