Clemson Computing & Information Technology Outage History

Started Oct 30, 2026, 06:46 PM UTC· resolved Oct 30, 2026, 07:13 PM UTC

1. investigating Oct 30, 2026, 06:46 PM UTC

   Greenville One is experiencing a network outage. Our network team is working to resolve the issue, and we will provide updates as they become available.

2. resolved Oct 30, 2026, 07:13 PM UTC

   All Services have been restored. If you continue to experience issues, please contact the CCIT Service Desk at 864-656-3494 or [email protected].

Read the full incident report →

Started Oct 26, 2026, 07:18 PM UTC· resolved Oct 26, 2026, 09:15 PM UTC

1. investigating Oct 26, 2026, 07:18 PM UTC

   Dear Customer, We have identified a disruption affecting your service. We are working to determine the user impact and will provide information as it becomes available. Impact: We are working to determine the user impact and will provide information as it becomes available. Product Name Affected Service SAP Concur Travel

2. identified Oct 26, 2026, 07:47 PM UTC

   Dear Customer, As previously reported, we identified a degradation affecting your service. Impact Prior to Resolution: 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. Start Time: 18:45 UTC on 26 October 2026 Status Update: 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. We appreciate your patience as we work to resolve this issue. We will keep you updated until the issue is resolved. Product Name Affected Service SAP Concur Travel

3. resolved Oct 26, 2026, 09:15 PM UTC

   Dear Customer, The degradation affecting your service has now been resolved. Impact Prior to Resolution: 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. Start Time:18:45 UTC on 26 October 2026 End Time: 20:22 UTC on 26 October 2026 Solution: 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. We are sorry for any inconvenience this may have caused. Thank you for your patience. Product Name Affected Service SAP Concur Travel

Read the full incident report →

Started Oct 26, 2026, 02:46 PM UTC· resolved Oct 26, 2026, 06:14 PM UTC

1. identified Oct 26, 2026, 02:46 PM UTC

   CU Navigate is experiencing login issues. We are working with the vendor to resolve the issue. We will post updates as we get them. Thank you for your patience.

2. resolved Oct 26, 2026, 06:14 PM UTC

   All Services have been restored. If you continue to experience issues, please contact the CCIT Service Desk at 864-656-3494 or [email protected].

Read the full incident report →

Started Oct 23, 2026, 04:09 PM UTC· resolved Oct 24, 2026, 01:36 PM UTC

1. identified Oct 23, 2026, 04:09 PM UTC

   Incident status: Identified We have identified an issue with our external vendor where users are experiencing issues with Multiple Zoom Services. We are actively working with our vendor partner to resolve this issue. We will share updates as soon as they become available. Components affected Degraded Performance Zoom Chat - Zoom Chat Degraded Performance Zoom CX - Global - Zoom Contact Center Degraded Performance Zoom Meetings - Zoom Meetings Degraded Performance ZoomMate

2. resolved Oct 24, 2026, 01:36 PM UTC

   Zoom reports that the affected services are operational. We are resolving this incident. If you continue to experience issues, please contact CCIT Support.

Read the full incident report →

Started Oct 23, 2026, 03:34 PM UTC· resolved Oct 23, 2026, 07:05 PM UTC

1. investigating Oct 23, 2026, 03:34 PM UTC

   Dear Customer, We have identified a degradation affecting your service. We are working to determine the user impact and will provide information as it becomes available. Impact: We are working to determine the user impact and will provide information as it becomes available. Product Name Affected Service SAP Concur Travel

2. identified Oct 23, 2026, 06:22 PM UTC

   Dear Customer, As previously reported, we identified a degradation affecting your service. 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. Status Update: 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.

3. resolved Oct 23, 2026, 07:05 PM UTC

   All Services have been restored. If you continue to experience issues, please contact the CCIT Service Desk at 864-656-3494 or [email protected].

Read the full incident report →

Started Oct 22, 2026, 12:10 PM UTC· resolved Oct 22, 2026, 01:13 PM UTC

1. investigating Oct 22, 2026, 12:10 PM UTC

   Hello Admins, We are upgrading SCORM to the Rustici Engine v24 within the IAD region starting on Friday, October 30, at 10:00 PM ET. What you need to know: When: Friday, October 30 at 10:00 PM ET to Saturday, October 31 at 12:00 PM ET (14 hours total). The Impact: During this 14-hour window, users in the IAD region will be unable to import new SCORM packages. What remains active: All other platform functionality, including launching and completing existing SCORM packages, recording scores in the gradebook, and general navigation, will remain fully operational. What you need to do: No action required. Why the window is 14 hours: The SCORM database is large, so the migration needs to run in one continuous pass. We've scheduled 14 hours to give it the time it needs. Why we’re doing this: The Rustici Engine v24 is the most current available version of the SCORM engine. Upgrading from v20 keeps the service on a supported, maintainable foundation, and lets us add new capabilities. What the upgrade adds: Support for implementing cookie-based authentication for SCORM content Support for new SCORM standards Improved stability An updated player If you would like to read more about the Rustici Engine and what it has to offer please see the following link: Rustici Engine We appreciate your cooperation during this scheduled maintenance window. Best regards, Canvas Team

2. resolved Oct 22, 2026, 01:13 PM UTC

   Some users may be experiencing slow load times or errors when previewing files in Canvas Investigating We are currently investigating this issue. Posted 16 minutes ago. Oct 22, 2026 - 03:43 MDT Monitoring - A fix has been implemented and we are monitoring the results. Oct 22, 07:16 MDT Resolved - This incident has been resolved. Oct 22, 07:23 MDT

Read the full incident report →

Started Oct 16, 2026, 06:00 AM UTC· resolved Oct 16, 2026, 12:52 PM UTC

1. investigating Oct 16, 2026, 06:00 AM UTC

   The network at PSA Baruch is currently unavailable. The NOC is aware and investigating. We’ve contacted the service providers, who report that their connections are working. We’re checking whether a power issue at the site may be affecting service and will share an update when we learn more.

2. resolved Oct 16, 2026, 12:52 PM UTC

   The network outage at PSA Baruch has been resolved, and service is back online. The issue appears to have been caused by a power interruption. The NOC will continue normal monitoring.

Read the full incident report →

Started Oct 08, 2026, 03:41 PM UTC· resolved Oct 08, 2026, 04:19 PM UTC

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.

Read the full incident report →