nam - Notice history

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🟡 SSD Array or one of its disks are in a degraded state. Assuming everything is working as it should, this should not have an effect on any of the nam services.

This incident was created by an automated monitoring service.

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🔴 Pool Mining Server cannot be accessed at the moment. This most likely means the nam Mining Pool is down! ☹️

This incident was created by an automated monitoring service. <@&901260893168488488>

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🟠 One of the automated tasks that backs up all server VM's, Databases, has failed to run.
Backups affected: Local fire-safe drive & Cloud copies