Pawsey Supercomputing Research Centre Status

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Resolved: Nimbus systems are now fully restored. If you are still experiencing issues with specific Nimbus instances, please contact the Pawsey Helpdesk.

Monitoring: With the back-end storage incident under control, we have returned to addressing the remaining instances affected by this network change. This includes public access to the Data Portal, and access to Setonix and to Acacia (Projects and Ingest) from Nimbus instances.

Monitoring: Access to Setonix and to Acacia (Projects and Ingest) from Nimbus instances is currently impacted.

In addition, the Data Portal is currently not publicly accessible.

Monitoring: All main Nimbus services have been returned to service. Specific instances still require attention and we will respond to each in turn. Please raise any further issues with a ticket to help@pawsey.org.au

Investigating: We are continuing to investigate this issue.

Investigating: We are aware of network issues between Nimbus instances and some other Pawsey services, and are continuing to investigate. Also, creating instances is not reliably working. If a specific issue with regards to any of this is affecting you, please send email to help@pawsey.org.au to raise a ticket and we will ensure it is handled in due course.

All of this investigation work will continue tomorrow.

Investigating: We are continuing to investigate this issue.

Investigating: Instance and dashboard access has been restored. We are continuing to work on the APIs, so some dashboard functionality will not yet work reliably.

Investigating: We have encountered further issues after the network maintenance. At present this is affecting both access to running instances, and access to the Nimbus dashboard. The instances themselves are still running, it is only the access to them that is affected by this outage.

Unfortunately, as we have not been able to restore services today, we will continue to work on this tomorrow morning.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Access to existing instances is now restored. However, the Nimbus dashboard is still currently unavailable. We are continuing to address this, and will update you when all services are returned to operation.

Resolved: Nimbus systems are now fully restored. If you are still experiencing issues with specific Nimbus instances, please contact the Pawsey Helpdesk.

Monitoring: Nimbus services are now available again, which includes access to Nimbus instances. Please note that performance will be partially degraded as the back-end storage continues to recover. If you are having issues accessing any of your instances after this incident, please contact the Pawsey helpdesk and we will follow it up. Please note, if you still have a Helpdesk ticket open from last week's incident, that is a separate issue that we are continuing to follow up.

Identified: The underlying cause of the storage system outage has been found and addressed. The storage system is now stabilising. We will provide further updates when we begin reinstating Nimbus services.

Investigating: The condition of the back-end storage has worsened, so we have paused the cluster for the time being. You will be unable to read or write any data to local disks or attached volumes on all Nimbus instances. We will let you know further information once we have a solution, but for now consider all Nimbus instances to be inaccessible.

Investigating: Please be aware we are currently experiencing an issue with the back-end storage for Nimbus. This will be impacting the operation of numerous instances, as well as the ability to read and write data to local disks and attached volumes of instances. We are currently investigating the issue.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Resolved: Nimbus systems are now fully restored. If you are still experiencing issues with specific Nimbus instances, please contact the Pawsey Helpdesk.

Monitoring: Nimbus services are now available again, which includes access to Nimbus instances. Please note that performance will be partially degraded as the back-end storage continues to recover. If you are having issues accessing any of your instances after this incident, please contact the Pawsey helpdesk and we will follow it up. Please note, if you still have a Helpdesk ticket open from last week's incident, that is a separate issue that we are continuing to follow up.

Identified: The underlying cause of the storage system outage has been found and addressed. The storage system is now stabilising. We will provide further updates when we begin reinstating Nimbus services.

Investigating: The condition of the back-end storage has worsened, so we have paused the cluster for the time being. You will be unable to read or write any data to local disks or attached volumes on all Nimbus instances. We will let you know further information once we have a solution, but for now consider all Nimbus instances to be inaccessible.

Investigating: Please be aware we are currently experiencing an issue with the back-end storage for Nimbus. This will be impacting the operation of numerous instances, as well as the ability to read and write data to local disks and attached volumes of instances. We are currently investigating the issue.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Resolved: Nimbus systems are now fully restored. If you are still experiencing issues with specific Nimbus instances, please contact the Pawsey Helpdesk.

Monitoring: With the back-end storage incident under control, we have returned to addressing the remaining instances affected by this network change. This includes public access to the Data Portal, and access to Setonix and to Acacia (Projects and Ingest) from Nimbus instances.

Monitoring: Access to Setonix and to Acacia (Projects and Ingest) from Nimbus instances is currently impacted.

In addition, the Data Portal is currently not publicly accessible.

Monitoring: All main Nimbus services have been returned to service. Specific instances still require attention and we will respond to each in turn. Please raise any further issues with a ticket to help@pawsey.org.au

Investigating: We are continuing to investigate this issue.

Investigating: We are aware of network issues between Nimbus instances and some other Pawsey services, and are continuing to investigate. Also, creating instances is not reliably working. If a specific issue with regards to any of this is affecting you, please send email to help@pawsey.org.au to raise a ticket and we will ensure it is handled in due course.

All of this investigation work will continue tomorrow.

Investigating: We are continuing to investigate this issue.

Investigating: Instance and dashboard access has been restored. We are continuing to work on the APIs, so some dashboard functionality will not yet work reliably.

Investigating: We have encountered further issues after the network maintenance. At present this is affecting both access to running instances, and access to the Nimbus dashboard. The instances themselves are still running, it is only the access to them that is affected by this outage.

Unfortunately, as we have not been able to restore services today, we will continue to work on this tomorrow morning.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Access to existing instances is now restored. However, the Nimbus dashboard is still currently unavailable. We are continuing to address this, and will update you when all services are returned to operation.

Resolved: Nimbus systems are now fully restored. If you are still experiencing issues with specific Nimbus instances, please contact the Pawsey Helpdesk.

Monitoring: Nimbus services are now available again, which includes access to Nimbus instances. Please note that performance will be partially degraded as the back-end storage continues to recover. If you are having issues accessing any of your instances after this incident, please contact the Pawsey helpdesk and we will follow it up. Please note, if you still have a Helpdesk ticket open from last week's incident, that is a separate issue that we are continuing to follow up.

Identified: The underlying cause of the storage system outage has been found and addressed. The storage system is now stabilising. We will provide further updates when we begin reinstating Nimbus services.

Investigating: The condition of the back-end storage has worsened, so we have paused the cluster for the time being. You will be unable to read or write any data to local disks or attached volumes on all Nimbus instances. We will let you know further information once we have a solution, but for now consider all Nimbus instances to be inaccessible.

Investigating: Please be aware we are currently experiencing an issue with the back-end storage for Nimbus. This will be impacting the operation of numerous instances, as well as the ability to read and write data to local disks and attached volumes of instances. We are currently investigating the issue.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Resolved: Nimbus systems are now fully restored. If you are still experiencing issues with specific Nimbus instances, please contact the Pawsey Helpdesk.

Monitoring: With the back-end storage incident under control, we have returned to addressing the remaining instances affected by this network change. This includes public access to the Data Portal, and access to Setonix and to Acacia (Projects and Ingest) from Nimbus instances.

Monitoring: Access to Setonix and to Acacia (Projects and Ingest) from Nimbus instances is currently impacted.

In addition, the Data Portal is currently not publicly accessible.

Monitoring: All main Nimbus services have been returned to service. Specific instances still require attention and we will respond to each in turn. Please raise any further issues with a ticket to help@pawsey.org.au

Investigating: We are continuing to investigate this issue.

Investigating: We are aware of network issues between Nimbus instances and some other Pawsey services, and are continuing to investigate. Also, creating instances is not reliably working. If a specific issue with regards to any of this is affecting you, please send email to help@pawsey.org.au to raise a ticket and we will ensure it is handled in due course.

All of this investigation work will continue tomorrow.

Investigating: We are continuing to investigate this issue.

Investigating: Instance and dashboard access has been restored. We are continuing to work on the APIs, so some dashboard functionality will not yet work reliably.

Investigating: We have encountered further issues after the network maintenance. At present this is affecting both access to running instances, and access to the Nimbus dashboard. The instances themselves are still running, it is only the access to them that is affected by this outage.

Unfortunately, as we have not been able to restore services today, we will continue to work on this tomorrow morning.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Access to existing instances is now restored. However, the Nimbus dashboard is still currently unavailable. We are continuing to address this, and will update you when all services are returned to operation.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Resolved: Nimbus systems are now fully restored. If you are still experiencing issues with specific Nimbus instances, please contact the Pawsey Helpdesk.

Monitoring: With the back-end storage incident under control, we have returned to addressing the remaining instances affected by this network change. This includes public access to the Data Portal, and access to Setonix and to Acacia (Projects and Ingest) from Nimbus instances.

Monitoring: Access to Setonix and to Acacia (Projects and Ingest) from Nimbus instances is currently impacted.

In addition, the Data Portal is currently not publicly accessible.

Monitoring: All main Nimbus services have been returned to service. Specific instances still require attention and we will respond to each in turn. Please raise any further issues with a ticket to help@pawsey.org.au

Investigating: We are continuing to investigate this issue.

Investigating: We are aware of network issues between Nimbus instances and some other Pawsey services, and are continuing to investigate. Also, creating instances is not reliably working. If a specific issue with regards to any of this is affecting you, please send email to help@pawsey.org.au to raise a ticket and we will ensure it is handled in due course.

All of this investigation work will continue tomorrow.

Investigating: We are continuing to investigate this issue.

Investigating: Instance and dashboard access has been restored. We are continuing to work on the APIs, so some dashboard functionality will not yet work reliably.

Investigating: We have encountered further issues after the network maintenance. At present this is affecting both access to running instances, and access to the Nimbus dashboard. The instances themselves are still running, it is only the access to them that is affected by this outage.

Unfortunately, as we have not been able to restore services today, we will continue to work on this tomorrow morning.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Access to existing instances is now restored. However, the Nimbus dashboard is still currently unavailable. We are continuing to address this, and will update you when all services are returned to operation.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.

Investigating: We have identified that transfer speeds are very slow at the moment. We are looking into this issue and will provide updates as soon as possible.