Reported Outages

CHI@UC outage Feb 22-23

Resolved Posted by Jason Anderson on February 23, 2020
Outage start Saturday, February 22, 2020 10 a.m.
Expected end Sunday, February 23, 2020 12 p.m.

We experienced an outage starting at Februar 22, 10AM CT at CHI@UC due to its database going down. We have since recovered the database and restored all site functionality. No data loss occurred. This should not have affected connectivity to running experiments. However, CHI@UC and the Jupyter environment were effectively down.

KVM@TACC Outage

Resolved Posted by Cody Hammock on February 13, 2020
Outage start Thursday, February 13, 2020 8:30 a.m.
Expected end Thursday, February 13, 2020 10:57 a.m.

RESOLVED: Maintenance for KVM@TACC is complete.

The KVM system at TACC is undergoing some emergency maintenance, and will have limited availabilty. We expect the work to be completed later today.

Thank you for your patience.

CHI@TACC login outage Feb 5, 2020

Resolved Posted by Jason Anderson on February 05, 2020
Outage start Tuesday, February 04, 2020 11 p.m.
Expected end Thursday, February 06, 2020 10 a.m.

We have been experiencing an outage around logging in to CHI@TACC since around 11PM CT last night. We are working to fix the root cause. Logins to CHI@UC should still be possible; the link is here: https://chi.uc.chameleoncloud.org

System maintenance on Feb 4 2020

Resolved Posted by Jason Anderson on January 27, 2020
Outage start Tuesday, February 04, 2020 1 p.m.
Expected end Tuesday, February 04, 2020 2 p.m.

We will be performing system-wide maintenance on the CHI infrastructure on February 4, 2020. The maintenance is expected to take all day; while CHI@UC and CHI@TACC may be accessible for portions of the day, you should expect service interruptions as we apply upgrades to the various subsystems.

Network outage at TACC January 10th-13th

Resolved Posted by Jason Anderson on January 13, 2020
Outage start Friday, January 10, 2020 4 p.m.
Expected end Monday, January 13, 2020 9 a.m.

CHI@TACC experimental nodes were temporarily unreachable via SSH, though the Chameleon portal and user interfaces were still operational. CHI@UC was unaffected.

Planned network maintenance at CHI@UC

Resolved Posted by Jason Anderson on January 13, 2020
Outage start Monday, January 13, 2020 4 p.m.
Expected end Monday, January 13, 2020 4:20 p.m.

Apologies for the short notice, but we must perform a short maintenance on the CHI@UC network equipment today. This will cause a brief (10-20 minute) outage on the CHI@UC site, affecting external connectivity for all experiments as well as the Jupyter portal.

Network maintenance at TACC December 15 8am-4pm CDT

Resolved Posted by Cody Hammock on December 05, 2019
Outage start Sunday, December 15, 2019 8 a.m.
Expected end Sunday, December 15, 2019 12:40 p.m.
Update: This is a delayed message, the network maintenance has been completed as of 12:40 CST today.

Access to all TACC systems will be unavailable on Sunday, 15 December, 2019 from 8:00 AM CDT until 4:00 PM CDT. This is to allow for upgrades to the TACC core network hardware.During this upgrade, users will have no access to CHI@TACC and KVM@TACC services and instances, or the Chameleon Portal. CHI@UC and Jupyter will remain available.

Portal SSO Outage

Resolved Posted by Alejandro Rocha on October 04, 2019
Outage start Thursday, October 03, 2019 12:30 p.m.
Expected end Thursday, October 03, 2019 1:40 p.m.

SSO from Chameleon Portal to CHI@TACC and CHI@UC was unavailable for some users on 10/3/ 2019 from 12:30pm to 1:40pm.

Scheduled Outage for CHI@TACC

Resolved Posted by Alexander Barnes on September 23, 2019
Outage start Monday, October 07, 2019 8 a.m.
Expected end Monday, October 07, 2019 1 p.m.

There is a planned outage on October 7th for maintenance on CHI@TACC from 8am to 1pm CST.  

Networking Interruption for CHI@TACC

Resolved Posted by Cody Hammock on September 17, 2019
Outage start Monday, September 16, 2019 7:25 p.m.
Expected end Tuesday, September 17, 2019 8:30 a.m.

Networking for CHI@TACC started experiencing issues on Monday, September 16, at approximately 7:25pm Central Time.  The problem has been resolved as of 8:30am Central Time.  We apologize for any disruptions.