Is SAP Concur down?
Last checked 4m agoNo incidents right now.
SAP Concur is operational right now. Last checked 4m ago; the most recent incident resolved 2d ago.
Real-time SAP Concur status, recent outages, and incident history: pulled directly from SAP Concur's official status page at open.concur.com every 5 minutes. Pingoru tracks 10 SAP Concur services and has captured 27 incidents in the last 90 days (88.89% uptime). Get email, Slack, Discord, or webhook alerts the moment SAP Concur reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Travel
Timeline · 4 updates
- investigating · Oct 26, 2026, 07:11 PM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved · Oct 26, 2026, 07:46 PM UTC
We have identified a service degradation affecting the Concur Travel service. The extent of the customer impact is currently under investigation. Additional details regarding customer impact will be provided as they become available. This issue is intermittently affecting travel searches in New Concur Travel. After entering search criteria and clicking the Search button, users may receive the error message: "Sorry, something went wrong." When this error occurs, search results are not returned. Legacy Travel is not impacted by this issue. Workaround: We have identified a potential workaround. Because the issue is intermittent, users may be able to successfully complete their travel searches after making multiple attempts. The Incident Response Team (IRT) has engaged additional support teams and is currently reviewing internal logs to determine the root cause. In parallel, the team is restarting service pods in an effort to restore normal functionality. Our next scheduled update will be provided within one hour, or sooner if a significant change in status occurs.
- resolved · Oct 26, 2026, 08:41 PM UTC
We identified and resolved a service degradation affecting the Concur Travel service. Full Customer Base Impact will be provided when available. This issue was intermittently affecting travel searches in New Concur Travel. After entering search criteria and clicking the Search button, users may have received the error message: "Sorry, something went wrong." When this error occurred, search results were not returned. Legacy Travel was not impacted by this issue. Workaround: We identified a potential workaround. Because the impact was intermittent, users may have been able to successfully complete their travel searches after making multiple attempts. Services have returned to normal operating levels. We will continue to monitor for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.
- resolved · Oct 26, 2026, 09:12 PM UTC
We identified and resolved a service degradation affecting the Concur Travel service. Full Customer Base Impact will be provided when available. This issue was intermittently affecting travel searches in New Concur Travel. After entering search criteria and clicking the Search button, users may have received the error message: "Sorry, something went wrong." When this error occurred, search results were not returned. Legacy Travel was not impacted by this issue. Workaround: We identified a potential workaround. Because the impact was intermittent, users may have been able to successfully complete their travel searches after making multiple attempts. The Incident Response Team took action to to upgrade an instance type to restore service. We have verified that service performance is stable and will now resolve the incident. An investigation into the root cause of this incident will be conducted, and a root cause analysis report provided when that investigation is complete.
Latest: We identified and resolved a service degradation affecting the Concur Travel service. Full Customer Base Impact will be provided when available. This issue was intermittently affec…
-
- Travel
Timeline · 5 updates
- investigating · Oct 23, 2026, 03:57 PM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved · Oct 23, 2026, 04:33 PM UTC
We have identified a service degradation impacting Concur Travel. This issue is impacting all air, car, and hotel booking submissions via the Sabre Global Distribution System (GDS) in all Data Centers. Air, car, and hotel searches can be successfully performed. However, when attempting to finalize and submit the booking, an error is presented. This error is preventing the successful submission of travel bookings. Additionally, attempts to modify or cancel existing bookings cannot be successfully executed. Important: Should an error be encountered while finalizing a hotel booking, please do not re-attempt the booking, as it is possible this could result in duplicate bookings. Please reach out to the hotel directly to prevent potential no show charges. Workaround: Unfortunately, there is no available workaround for you at this time. The Incident Response Team (IRT) is working with Sabre to provide resolution. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved · Oct 23, 2026, 05:29 PM UTC
User impact is unchanged. We have identified a service degradation impacting Concur Travel. This issue is impacting all air, car, and hotel booking submissions via the Sabre Global Distribution System (GDS) in all Data Centers. Air, car, and hotel searches can be successfully performed. However, when attempting to finalize and submit the booking, an error is presented. This error is preventing the successful submission of travel bookings. Additionally, attempts to modify or cancel existing bookings cannot be successfully executed. Important: Should an error be encountered while finalizing a hotel booking, please do not re-attempt the booking, as it is possible this could result in duplicate bookings. Please reach out to the hotel directly to prevent potential no show charges. Workaround: Unfortunately, there is no available workaround for you at this time. The Incident Response Team (IRT) is continuing to work with Sabre to provide resolution. Our next scheduled update will be in two hours or sooner should a significant change occur.
- resolved · Oct 23, 2026, 06:53 PM UTC
We have observed recovery of a service degradation impacting Concur Travel. This issue was impacting all air, car, and hotel booking submissions via the Sabre Global Distribution System (GDS) in all Data Centers. Air, car, and hotel searches could be successfully performed. However, when attempting to finalize and submit the booking, an error was presented. This error prevented the successful submission of travel bookings. Additionally, attempts to modify or cancel existing bookings could not be successfully executed. Important: Should an error have been encountered while finalizing a hotel booking, it was important to refrain from re-attempting the booking, as it was possible this could have resulted in duplicate bookings. Please reach out to the hotel directly to prevent potential no show charges if hotel bookings were re-attempted during the time of impact. Workaround: Unfortunately, there was no available workaround for you during the time of impact. Services have returned to normal operating levels. We will continue to monitor for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.
- resolved · Oct 23, 2026, 07:02 PM UTC
We have observed recovery of a service degradation impacting Concur Travel. This issue was impacting all air, car, and hotel booking submissions via the Sabre Global Distribution System (GDS) in all Data Centers. Air, car, and hotel searches could be successfully performed. However, when attempting to finalize and submit the booking, an error was presented. This error prevented the successful submission of travel bookings. Additionally, attempts to modify or cancel existing bookings could not be successfully executed. Important: Should an error have been encountered while finalizing a hotel booking, it was important to refrain from re-attempting the booking, as it was possible this could have resulted in duplicate bookings. Please reach out to the hotel directly to prevent potential no show charges if hotel bookings were re-attempted during the time of impact. Workaround: Unfortunately, there was no available workaround for you during the time of impact. The Incident Response Team worked with Sabre to restore service. We have verified that service performance is stable and will now resolve the incident. An investigation into the root cause of this incident will be conducted , and a root cause analysis report provided when that investigation is complete.
Latest: We have observed recovery of a service degradation impacting Concur Travel. This issue was impacting all air, car, and hotel booking submissions via the Sabre Global Distribution S…
-
- Request
Timeline · 1 update
- resolved · Oct 21, 2026, 09:42 PM UTC
We identified and resolved a service disruption impacting approximately 70 Concur Requests. This issue affected a single go.gov customer in the Concur Cloud for Public Sector Data Center. The impacted documents were in Pending External Validation status with no forward progress. These documents have now been fully processed, and no further action is necessary. Workaround: Unfortunately, a workaround was not available during the time of impact. The IRT performed an authentication configuration update to restore service. 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.
Latest: We identified and resolved a service disruption impacting approximately 70 Concur Requests. This issue affected a single go.gov customer in the Concur Cloud for Public Sector Data …
-
- Travel
Timeline · 1 update
- resolved · Oct 16, 2026, 04:36 PM UTC
A service disruption has been identified and resolved affecting travel search functionality for Legacy Travel customers in the US2 Data Center. Affected users encountered the error message "We're Sorry… We encountered an issue that prevented us from completing your request" upon submitting search criteria in the travel wizard. The disruption impacted searches for air, hotel, and car travel segments across all Global Distribution Systems (GDSs). New Concur Travel customers were not affected and retained full search and booking functionality throughout the incident period. A workaround for this issue was not available during service disruption. As the Incident Response Team (IRT) was gathering, the service self-recovered. We have verified that service performance is stable and will now resolve the 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.
Latest: A service disruption has been identified and resolved affecting travel search functionality for Legacy Travel customers in the US2 Data Center. Affected users encountered the error…
-
- Travel
Timeline · 3 updates
- resolved · Oct 15, 2026, 11:54 AM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved · Oct 15, 2026, 12:19 PM UTC
We have identified a degradation affecting Travel Service in the APJ1 Data Center. When users tried to search for Air, Car or Hotel and populate their search in From and To field, the fields were not populating. Service has been restored to a normal operating level, and we have started mandatory monitoring period while we are observing recovery. We will post the next incident communication at or 01:00 PM UTC on 15 October 2026.
- resolved · Oct 15, 2026, 12:29 PM UTC
We have identified a degradation affecting Travel Service in the APJ1 Data Center. When users tried to search for Air, Car or Hotel and populate their search in From and To field, the fields were not populating. The Incident Response Team has identified a deployment which has caused the issue and promptly reverted it to restore the service. We have completed the post recovery stability monitoring period and confirmed that service is operating at a normal and stable level and will now resolve this incident. We are sorry for any inconvenience this may have caused. Thank you for your patience.
Latest: We have identified a degradation affecting Travel Service in the APJ1 Data Center. When users tried to search for Air, Car or Hotel and populate their search in From and To field, …
-
See the full SAP Concur outage history
22 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse SAP Concur outage history →Or sign up free to get alerts when SAP Concur breaks · 10 free monitors · No credit card
Incident record
Since April 2026 · Sap Concur Json · 10 components checked every 5 minutesThe longest incident in the last year, Analysis/Intelligence: P1 on May 14, 2026, ran for 47 days.
Most affected components, last 12 months
- Travel72
- Expense40
- Analysis/Intelligence28
- Request27
- Invoice20
Latest incidents
- Travel: P1
We are working to determine the user impact and will provide information as it becomes available.
- Travel: P1
We are working to determine the user impact and will provide information as it becomes available.
- Request: P1
We identified and resolved a service disruption impacting approximately 70 Concur Requests. This issue affected a single go.gov customer in the Concur Cloud…
- Travel: P1 ResolvedStarted Oct 26, 2026, 06:45 PM UTC · Resolved Oct 26, 2026, 08:22 PM UTC · 1h 37m
- Travel: P1 ResolvedStarted Oct 23, 2026, 03:34 PM UTC · Resolved Oct 23, 2026, 06:35 PM UTC · 3h 1m
- Request: P1 ResolvedStarted Oct 20, 2026, 03:34 PM UTC · Resolved Oct 20, 2026, 10:20 PM UTC · 6h 46m
- Travel: P1 ResolvedStarted Oct 16, 2026, 02:03 PM UTC · Resolved Oct 16, 2026, 04:21 PM UTC · 2h 18m
- Travel: P1 ResolvedStarted Oct 15, 2026, 11:32 AM UTC · Resolved Oct 15, 2026, 12:00 PM UTC · 28m
- Started Oct 13, 2026, 08:41 PM UTC · Resolved Oct 13, 2026, 09:20 PM UTC · 39m
- Mobile: P1 ResolvedStarted Oct 08, 2026, 02:20 PM UTC · Resolved Oct 08, 2026, 03:50 PM UTC · 1h 30m
- Expense, Invoice: P1 ResolvedStarted Sep 28, 2026, 10:46 PM UTC · Resolved Sep 28, 2026, 10:56 PM UTC · 10m