FAS Research Computing - Globus.org maintenance Saturday June 18, 9am-10am – Maintenance details
All systems operational
Status page for the Harvard FAS Research Computing cluster and other resources.
Cluster Utilization (VPN and FASRC login required): Cannon | FASSE
Please scroll down to see details on any Incidents or maintenance notices.
Monthly maintenance occurs on the first Monday of the month (except holidays).
The colors shown in the bars below were chosen to increase visibility for color-blind visitors. For higher contrast, switch to light mode at the bottom of this page if the background is dark and colors are muted.
Globus.org maintenance Saturday June 18, 9am-10am
Completed
Scheduled for June 18, 2022 at 1:00 PM – 2:00 PM
Affects
Storage
Under maintenance from 1:00 PM to 2:00 PM
Globus Data Transfer
Under maintenance from 1:00 PM to 2:00 PM
Updates
Completed
June 18, 2022 at 2:00 PM
Completed
June 18, 2022 at 2:00 PM
Maintenance has completed successfully
Update
June 18, 2022 at 1:00 PM
Update
June 18, 2022 at 1:00 PM
Maintenance is now in progress
In progress
June 18, 2022 at 1:00 PM
In progress
June 18, 2022 at 1:00 PM
Maintenance is now in progress
Planned
June 18, 2022 at 1:00 PM
Planned
June 18, 2022 at 1:00 PM
Globus has informed us that they will be performing maintenance
Saturday June 18th 9am-10am
```
During the downtime, the following will be impacted:
All services in the Globus ecosystem that use Auth, including Flows, Search, and Timer, will be unavailable.
Users will be unable to initiate new transfers. Transfers that are inflight when the downtime begins will resume at the last checkpoint when the services are restored at the end of the maintenance period.
Users will not be able to log into applications that rely on Globus Auth, including Globus webapp and command line interface.
All third party applications and services that rely on Globus Auth will be impacted, and users will not be able to login/authenticate.
Users will be unable to initiate new flow runs. Flow runs that attempt to start a new step during the downtime will fail. We recommend that users check the state of their flow runs after services have resumed.
```