Resolved after 7 hours 52 minutes, affecting Travel, on January 4, 2016.
Travel was intermittently unavailable. Users experienced errors, slow processing or were logged out when performing administrative functions or attempting to search or book travel via Sabre. The cause of this issue was due to increased GDS logging volumes leading to contention on our servers and as an additional affect, an overload of requests to our vendors which triggered their systems to temporarily block those requests. To resolve the issue, we disabled GDS logging and the vendor took the necessary steps to restore access for our requests. We will continue to investigate more efficient logging methods.
Affected components
Update timeline
- investigating Jan 04, 2016, 07:53 PM UTC
Some users may experience errors or slow processing when performing administrative functions or attempting to search or book travel.
- investigating Jan 04, 2016, 08:21 PM UTC
Users are experiencing errors or slow processing when attempting to search or book travel. We appreciate your patience while we work to resolve this issue.
- investigating Jan 04, 2016, 10:21 PM UTC
We are continuing to investigate this issue. We will provide an update as more information becomes available.
- investigating Jan 05, 2016, 12:24 AM UTC
Worldspan is now the only impacted GDS. All other GDSs have returned to normal processing. We will provide an update as more information becomes available.
- investigating Jan 05, 2016, 01:56 AM UTC
We have resolved the issue and will provide the root cause analysis as soon as possible.
- investigating Jan 21, 2016, 09:42 PM UTC
Travel was intermittently unavailable. Users experienced errors, slow processing or were logged out when performing administrative functions or attempting to search or book travel via Sabre. The cause of this issue was due to increased GDS logging volumes leading to contention on our servers and as an additional affect, an overload of requests to our vendors which triggered their systems to temporarily block those requests. To resolve the issue, we disabled GDS logging and the vendor took the necessary steps to restore access for our requests. We will continue to investigate more efficient logging methods.
Your product runs on more than SAP Concur
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services