Current System Load
The plot below shows the status of the CPU nodes on the current Cirrus service for the past day.
A description of each of the status types is provided below the plot.
Node State
- alloc, mix, comp, drng: Nodes running user jobs
- idle, plnd: Nodes available for user jobs
- resv: Nodes in reservation and not available for standard user jobs
- down, drain, maint, boot: Nodes unavailable for user jobs
Core Allocation
Service Alerts
No open service alertsRecently Resolved Service Alerts
This table lists the last five resolved service alerts A full list of historical resolved service alerts is available.
| Status | Start | End | Scope | Impact | Reason |
|---|---|---|---|---|---|
| Resolved | 2026-11-04 13:00 | 2026-11-04 18:00 | Slurm | Small risk of interruption to Slurm. | Slurm prolog and epilog location being updated. |
| Resolved | 2026-10-24 21:00 | 2026-10-25 21:00 | Service availability | Increased risk to service availability. Users may find access or jobs interrupted. | Amber weather warning for high winds from Storm Boelo. |
| Resolved | 2026-10-22 17:50 | 2026-10-27 11:50 | Login access still 'At Risk' | Users were unable to log on to Cirrus - an error message relating to 'Error connecting to MFA endpoint' is displayed. A temporary workaround has been put in place. | The temporary remediation to address the issues has been removed as upstream service has returned to normal. |
| Resolved | 2026-10-22 14:30 | 2026-10-23 18:00 | Connectivity to all EPCC hosted services | Risk of interruption to connectivity to ACF services – most likely to be in the order of seconds. Running work will not be impacted. | Essential firewall maintenance. |
| Resolved | 2026-10-21 08:00 | 2026-10-23 18:00 | Login and compute nodes | Users logged in when login nodes are rebooted may be requested to log in again on 21 and 22 October (they will be able to do so immediately). No other impact expected as compute nodes rolling reboot as they finish running work. | Essential operating system updates to all Cirrus nodes. |
Service Maintenance Sessions
We keep maintenance downtime to a minimum on the service but do occasionally need to perform essential work on the system. Maintenance sessions are used to ensure that:
- software versions are kept up to date;
- firmware levels on HPE and third-party peripheral equipment are kept up to date; essential security patches are applied;
- failed/suspect hardware can be replaced;
- new software can be installed; periodic essential maintenance on HPE electrical and mechanical support equipment (refrigeration systems, air blowers and power distribution units) can be undertaken safely.
Additional maintenance sessions can be scheduled for major hardware or software updates; major upgrades to facility plant and infrastructure; acceptance testing following major service upgrades and statutory electrical testing.
No upcoming or ongoing maintenance sessionsA list of all previous maintenance sessions.