{"id":15292,"date":"2023-04-06T09:33:45","date_gmt":"2023-04-06T14:33:45","guid":{"rendered":"https:\/\/www.wisconsin.edu\/travel\/?page_id=15292"},"modified":"2023-04-06T09:38:49","modified_gmt":"2023-04-06T14:38:49","slug":"sap-concur-real-time-status","status":"publish","type":"page","link":"https:\/\/www.wisconsin.edu\/travel\/support\/sap-concur-real-time-status\/","title":{"rendered":"SAP Concur Real Time Status"},"content":{"rendered":"\n\t\t\t\t\t<div id=\"cfct-build-15292\" class=\"cfct-build grid\">\n\t\t\t\t\t\t<div class=\"row\"><div class=\"col-md-3 cfct-block\">\n\t\t\t<div class=\"cfct-module cfct-module-loop-subpages\">\n\t\t\t\t<div class=\"\"><div class=\"cfct-mod-content menu-cfct-module-6474230c2f2911b666ebc0ea260c809f-container\">\n    <nav >\n        \n\t\t\t\t\t<ul class=\"cfct-module-loop-subpages menu nav\">\t\t\t<li ><a href=\"https:\/\/www.wisconsin.edu\/travel\/support\/\">Resources<\/a><\/li>\n\t\t\t\t\t\t<li ><a href=\"https:\/\/www.wisconsin.edu\/travel\/support\/concur-support\/\">Concur Support &amp; User Guides<\/a><\/li>\n\t\t\t\t\t\t<li ><a href=\"https:\/\/www.wisconsin.edu\/travel\/support\/travel-frequently-asked-questions\/\">Frequently Asked Questions<\/a><\/li>\n\t\t\t\t\t\t<li ><a href=\"https:\/\/www.wisconsin.edu\/travel\/support\/travel-manager-resources\/\">Resources for Travel Managers<\/a><\/li>\n\t\t\t\t\t\t<li ><a href=\"https:\/\/www.wisconsin.edu\/travel\/support\/sap-concur-real-time-status\/\">SAP Concur Real Time Status<\/a><\/li>\n\t\t\t\t\t\t<li ><a href=\"https:\/\/www.wisconsin.edu\/travel\/support\/user-guides-and-reference-materials\/\">Traveler User Guides &amp; Webinars<\/a><\/li>\n\t\t\t\t\t\t<li ><a href=\"https:\/\/www.wisconsin.edu\/travel\/support\/uw-whitewater\/\">UW- Whitewater<\/a><\/li>\n\t\t\t\t\t\t<li ><a href=\"https:\/\/www.wisconsin.edu\/travel\/support\/uw-la-crosse\/\">UW-La Crosse Travel<\/a><\/li>\n\t\t\t\t\t\t<li ><a href=\"https:\/\/www.wisconsin.edu\/travel\/support\/uw-platteville-travel\/\">UW-Platteville Travel<\/a><\/li>\n\t\t\t\t\t\t<li ><a href=\"https:\/\/www.wisconsin.edu\/travel\/support\/webinars\/\">Webinars<\/a><\/li>\n\t\t\t\n\t\t\t\t\t<\/ul><!-- \/cfct-module-loop-subpages menu nav -->    <\/nav>\n<\/div>\n<\/div>\n\t\t\t<\/div><\/div><div class=\"col-md-9 cfct-block\">\n\t\t\t<div class=\"cfct-module uwsa-feed\">\n\t\t\t\t<div class=\"listing-module post-list \">\n        <div class=\"header\">\n            \n            <h3><a href=\"https:\/\/open.concur.com\/pco\/\">Personalized SAP Concur Open Updates<\/a><\/h3>\n                        <p>Personalized up-to-the-minute service availability and performance information<\/p>\n            \n        <\/div>\n        \n        \n        \n            <div class=\"row\">\n                <ol class=\"post-archive small-with-photos \">\n                    <li class=\"col-md-12 post-excerpt \">\n                        <h2><a href=\"https:\/\/open.concur.com\/details\/p1\/?incident=OPI-6257695\">OPI-6257695 : US2 | EU2 | CONCUR CLOUD FOR PUBLIC SECTOR | APJ1 : Travel : Issue Identified and Resolved<\/a><\/h2>\n                        <article >\n                            <p class=\"post-date\">30 June 2026 | 8:55 am<\/p>\n                            <p>All Travelport customers in the US2, EU2, Concur Cloud for Public Sector, and APJ1 Data Centers experienced functional disruption when trying to search for car rentals with corporate rates. After entering search details and clicking the Search button, all travellers received a \u2018No rates found\u2019 message. Non corporate rates were available during the outage.\n\nAs the Incident Response Team gathered, the service was restored. We have verified that service performance is stable and will now resolve this incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.<\/p>\n                        <\/article>\n                    <\/li>\n                <\/ol>\n            <\/div>\n\n        \n            <div class=\"row\">\n                <ol class=\"post-archive small-with-photos \">\n                    <li class=\"col-md-12 post-excerpt \">\n                        <h2><a href=\"https:\/\/open.concur.com\/details\/p1\/?incident=OPI-6254432\">OPI-6254432 : US2 | EU2 | CONCUR CLOUD FOR PUBLIC SECTOR : Travel : Root Cause Analysis<\/a><\/h2>\n                        <article >\n                            <p class=\"post-date\">29 June 2026 | 7:33 am<\/p>\n                            <p>Impact as Reported:\nAll Sabre customers in the US2,EU2 and Concur Cloud for Public Sector Data Centers experienced approximately 95% functional degradation when attempting to book Hilton properties. At the Review and Book stage, users may have encountered the error: \u201cWe are unable to complete your booking at this time. Please wait and try again later.\u201d This error occurred after selecting Book and Continue, preventing completion of the reservation.\n\nRoot cause:\nThe root cause of the incident has been identified to be a service disruption at our third party GDS partner Sabre.\n\nCorrective Actions:\nN\/A<\/p>\n                        <\/article>\n                    <\/li>\n                <\/ol>\n            <\/div>\n\n        \n            <div class=\"row\">\n                <ol class=\"post-archive small-with-photos \">\n                    <li class=\"col-md-12 post-excerpt \">\n                        <h2><a href=\"https:\/\/open.concur.com\/details\/p1\/?incident=OPI-6254432\">OPI-6254432 : US2 | EU2 | CONCUR CLOUD FOR PUBLIC SECTOR : Travel : Issue Resolved<\/a><\/h2>\n                        <article >\n                            <p class=\"post-date\">23 June 2026 | 10:54 am<\/p>\n                            <p>We identified a functional disruption affecting Hilton hotel searches through the Sabre Global Distribution System (GDS), which impacted 100% of Hilton search requests. When performing a hotel search that specified only Hilton properties, New Concur Travel users received the error \u201cNot Able to Display Searched Hotel.\u201d Legacy Travel users were presented with a list of Hilton properties; however, all results were marked as \u201cNot Available.\u201d These errors completely prevented successful Hilton hotel bookings via the Sabre GDS. Hotel searches and bookings for other hotel chains were unaffected.\n\nWorkaround: Unfortunately, there was no way for you to workaround the issue during the time of impact.\n\nThe Incident Response Team (IRT) has received confirmation from Sabre that the issue has been resolved. We have also validated that performance metrics for successful hotel bookings indicate stable service levels. The incident will now be closed.<\/p>\n                        <\/article>\n                    <\/li>\n                <\/ol>\n            <\/div>\n\n        \n            <div class=\"row\">\n                <ol class=\"post-archive small-with-photos \">\n                    <li class=\"col-md-12 post-excerpt \">\n                        <h2><a href=\"https:\/\/open.concur.com\/details\/p1\/?incident=OPI-6254432\">OPI-6254432 : US2 | EU2 | CONCUR CLOUD FOR PUBLIC SECTOR : Travel : Issue Status Update<\/a><\/h2>\n                        <article >\n                            <p class=\"post-date\">22 June 2026 | 8:05 pm<\/p>\n                            <p>We had identified a functional disruption affecting Hilton hotel searches through the Sabre Global Distribution System (GDS), which impacted 100% of Hilton search requests. When performing a hotel search that specified only Hilton properties, New Concur Travel users received the error \u201cNot Able to Display Searched Hotel.\u201d Legacy Travel users were presented with a list of Hilton properties; however, all results were marked as \u201cNot Available.\u201d These errors prevented successful Hilton hotel bookings. At that time, hotel searches and bookings for other hotel chains remained unaffected and could be completed successfully.\n\nService recovery has been observed, and we have started a mandatory post-recovery monitoring period to validate service performance stability prior to declaring the incident resolved.\n\nThe Incident Response Team (IRT) will continue monitoring Hilton hotel booking transactions for 24 hours and coordinate with the Sabre Team to confirm the resolution of the issue. The incident will only be fully resolved once the Sabre Team confirms that the service has been fully restored, no further booking errors are observed, and preventive measures are in place to avoid recurrence.\n\nThe next incident communication will be provided within 24 hours. We will share an update sooner once confirmation is received from the Sabre Team.<\/p>\n                        <\/article>\n                    <\/li>\n                <\/ol>\n            <\/div>\n\n        \n            <div class=\"row\">\n                <ol class=\"post-archive small-with-photos \">\n                    <li class=\"col-md-12 post-excerpt \">\n                        <h2><a href=\"https:\/\/open.concur.com\/details\/p1\/?incident=OPI-6254432\">OPI-6254432 : US2 | EU2 | CONCUR CLOUD FOR PUBLIC SECTOR : Travel : Issue Status Update<\/a><\/h2>\n                        <article >\n                            <p class=\"post-date\">22 June 2026 | 3:19 pm<\/p>\n                            <p>We have identified a functional disruption affecting Hilton hotel searches through the Sabre Global Distribution System (GDS), impacting 100% of Hilton search requests. When performing a hotel search that specifies only Hilton properties, New Concur Travel users receive the error \u201cNot Able to Display Searched Hotel.\u201d Legacy Travel users are presented with a list of Hilton properties; however, all results are marked as \u201cNot Available.\u201d These errors prevent successful Hilton hotel bookings. At this time, hotel searches and bookings for other hotel chains remain unaffected and can be completed successfully.\n\nWorkaround:\nUnfortunately, there is no workaround that will allow you to successfully search and book a Hilton Hotel via the Sabre Global Distribution System.\n\nSabre Teams are continuing to work with Hilton to provide a resolution. Current indications from the Sabre Team is that our next update will be in 24 hours. We will set our next communication for 24 hours, but will provide a status update sooner should a significant change occur.<\/p>\n                        <\/article>\n                    <\/li>\n                <\/ol>\n            <\/div>\n\n            <\/div>\n\n\t\t\t<\/div><\/div><\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t","protected":false},"excerpt":{"rendered":"","protected":false},"author":3346,"featured_media":0,"parent":3555,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-15292","page","type-page","status-publish","hentry","cfct-can-haz-build"],"_links":{"self":[{"href":"https:\/\/www.wisconsin.edu\/travel\/wp-json\/wp\/v2\/pages\/15292","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wisconsin.edu\/travel\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.wisconsin.edu\/travel\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.wisconsin.edu\/travel\/wp-json\/wp\/v2\/users\/3346"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wisconsin.edu\/travel\/wp-json\/wp\/v2\/comments?post=15292"}],"version-history":[{"count":6,"href":"https:\/\/www.wisconsin.edu\/travel\/wp-json\/wp\/v2\/pages\/15292\/revisions"}],"predecessor-version":[{"id":15308,"href":"https:\/\/www.wisconsin.edu\/travel\/wp-json\/wp\/v2\/pages\/15292\/revisions\/15308"}],"up":[{"embeddable":true,"href":"https:\/\/www.wisconsin.edu\/travel\/wp-json\/wp\/v2\/pages\/3555"}],"wp:attachment":[{"href":"https:\/\/www.wisconsin.edu\/travel\/wp-json\/wp\/v2\/media?parent=15292"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}