There are ongoing Incidents
Here you'll find the current status and incident history of NRIS - Norwegian Research Infrastructure Services.
High Performance Computing Minor incident
Betzy Minor incident
Saga Operational
Olivia Operational
90 days ago % Uptime Today
Storage Services Minor incident
National Infrastructure for Research Data
NIRD Data Peak Operational
NIRD Backup Operational
NIRD Data Lake Operational
NIRD Service Platform Minor incident
NIRD Research Data Archive Operational
NIRD Central Data Library Operational
Web services Operational
metacenter.no Operational
Administrative system for management of projects, users and quotas
puhuri.metacenter.no Operational
The portal for managing LUMI-projects.

Information notices


Information notice Change in how to request an S3 bucket
[Information]

The RequestS3Access command has been decommissioned and can no longer be used to request an S3 bucket.

To get an S3 bucket, email [email protected] with your account name and the bucket name you’d like to use. See the NIRD S3 documentation for details https://documentation.sigma2.no/files_storage/nird/s3.html.
Existing buckets are not affected.

Information notice Olivia: work area filling up
[Information]

The /cluster/work storage area on Olivia is filling up. Users have been asked to cleanup unused files, but some users might be experiencing issues with jobs getting No space left on device when trying to write data.

We see that some users have already started cleaning up, but it might take some time before this is fully in order. For the time being, please use the $SCRATCH area to write temporary job files (NB: the designated scratch area for a job is deleted when the job ends, so remember...

Information notice Issues with incoming support requests
[Information]

We have noticed an issue with incoming tickets to [email protected], where lines of text are “disappearing” upon arrival (either partially, or whole email - we receive empty mails). Based on some internal testing and testing from users (thank you!), we have discovered that it occurs when:

  1. Text is formatted before sending: Specifically text which is between lines of #####s, and even some markdown (though unpredictable interval) formatting.
  2. Email that is forwarded to us, alongside with new...
% Uptime
90 days ago Today
Incident & maintenance history
This page is automatically updated every 60 seconds