Orchestra: restart bookings with control over pending requests
An unavailable booking platform leaves requests in different states. The Orchestra case helps plan a restart with controls over access, confirmations and alternative channels.
Czytaj po portugalskuBy Pentesty
Define what needs to work again
The November 21 report on Orchestra prompted this analysis. In an interview with L’Écho touristique, a Travelsoft group publication, Travelsoft’s president reported unauthorized access, a precautionary shutdown and a gradual service restart. The consulted November 21 update still described recovery in progress. It did not confirm a data leak or fraudulent bookings.
For an agency or business connected to a central platform, choose a concrete task for assessing its return: checking an offer, confirming a booking or receiving its result. Separate those functions, identify their dependencies and name who can authorize each one. An accessible website may represent only part of the work your team needs to perform.
Classify requests before trying again
Build a list of operations affected during the window agreed with the team. Distinguish a request not yet sent, a transmitted request without a response and a confirmed booking. Connect the internal identifier to the partner’s identifier when available, without copying passenger information beyond what the authorized review needs. Assign an owner to resolve each unknown state.
Agree with the provider on how to check the result of an unanswered request. Avoid treating a repeated action automatically as a new order. Record the decision and the confirmation received. This proposed procedure makes operational uncertainty visible before another team tries to resolve the same case through a different channel.
Run a small test of the recovered integration
In an authorized environment, use synthetic data and an operation agreed with the platform administrator. Define the expected result beforehand and choose a scenario that produces no charge or real booking. Check the identity used, the integration’s response and the records produced by the components within scope.
Compare that result with a check at the authorized destination. Retain identifiers, times and the owner’s confirmation while keeping credentials out of the record. The review of continuity during a management outage offers another way to examine access and ownership while a central service is unavailable. A successful test covers that sample; record what remains unassessed.
Approve the restart with open items visible
Bring together the provider confirmation available, test results and requests whose outcomes remain unknown. Separate technical integration recovery from resolution of each interrupted operation. Record which functions were released, by whom and under which limits, including tasks that still depend on manual assistance.
Give that record to the operations owner. Agree on when exceptions will be reviewed and how the team will learn about another interruption. Then reconcile requests handled through alternative channels with the main system. Closure should explain what resumed, which operations were confirmed and who remains responsible for discrepancies.
Frequently asked questions
Does the website’s return confirm every pending booking?
Obtain confirmation for each operation included in the review. Page availability alone does not resolve unanswered requests or discrepancies between records.
Does this case confirm a data leak or booking fraud?
The interview did not confirm either; it described risks and recovery still in progress.
How can a team test recovery without creating a real booking?
Agree on an authorized sample using synthetic data and a result without commercial effect. Connect the response to the destination record and document limitations.
Who should approve an alternative channel?
The operations owner and administrators involved should define scope, access and confirmation. Preserve the connection to the original request for later reconciliation.
Sources and references
- Cyberattaque.org: November 21 report on Orchestra
- L’Écho touristique: interview published November 20 and updated November 21
Original Pentesty analysis, published November 21, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.