Clemson Computing & Information Technology incident

SAP/Concur Outage, Issue Identified - OPI-6312724

Minor Resolved View vendor source →

Clemson Computing & Information Technology experienced a minor incident on October 8, 2026 affecting SAP/Concur, lasting 38m. The incident has been resolved; the full update timeline is below.

Started
Oct 08, 2026, 03:41 PM UTC
Resolved
Oct 08, 2026, 04:19 PM UTC
Duration
38m
Detected by Pingoru
Oct 08, 2026, 03:41 PM UTC

Affected components

SAP/Concur

Update timeline

  1. identified Oct 08, 2026, 03:41 PM UTC

  2. monitoring Oct 08, 2026, 04:02 PM UTC

    Dear Customer, As previously reported, we identified a degradation affecting your service. Impact Prior to Resolution: We have identified an intermittent service degradation affecting logins via mobile device. This issue is currently impacting approximately 1% of customers in the US2 Data Center. When attempting to access the SAP Concur site via mobile device, users may receive the error message, "Sorry, something went wrong," after entering their login credentials. When this error occurs, the login attempt cannot be completed during that session. Additionally, it is possible some users may experience increased latency after entering their username and password. Users who are already logged in can continue working without interruption. Workaround: We have identified a workaround for you. If you encounter an error message after entering your user name and password, you may be able to successfully sign in by retrying your login attempt. Additionally, it is possible to login via web without issue.

  3. monitoring Oct 08, 2026, 04:09 PM UTC

    Status Update: Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.

  4. resolved Oct 08, 2026, 04:19 PM UTC

    Solution: The IRT isolated an underperforming server and took action to perform a failover 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.