nam - Notice history

🔴 nam Explorer cannot be accessed at the moment.

This incident was created by an automated monitoring service.

🔴 The Cloudflare Tunnel has disconnected. If this tunnel stays down, mining and other services will be affected. This is bad… It's the main protected tunnel to the internet from the nam servers. 😥 Hopefully it’s only an internet glitch and the backup internet connection will bring the tunnel back online in just a minute!

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.

🔴 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.

🔴 Pool Height is different from Europe public nodes. Either the nam Pool is stuck, or Cloudflare Cache is stale. Mining is most likely broken or on a fork!

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

This heigh mismatch is due to one of the nam DB's being rebuilt from 0 right now, this will clear once db rebuild is complete.