Given we have a passionate community I wanted to preemptively answer two questions:
Why is Nash under maintenance? Is this expected?
Nash as a platform is in heavy development, as such we deploy constant improvements on several different areas, from admin features, interface updates, matching engine or settlement improvements to support tooling. Most of this updates are of a type called zero-downtime. A zero-downtime update is an update that is rolled into production on a manner that allows the systems to just continue to work, therefore this updates require no special communication.
Unfortunately not all updates can be zero-downtime. For those, we have the maintenance mode. During maintenance mode the system is split in two, one static page showing the maintenance notification and a parallel version running the new system in production. After quality assurance (QA) tests the new version comes online.
To decrease disruption we choose to perform the planned maintenance on a recurring time window when we have the least amount of visitors in the platform, as seen on the image below:
Our planned maintenance for the near term will be recurring on:
18:00 Wednesday, Central European Time (CET), which is:
17:00 Wednesday, Coordinated Universal Time (UTC),
22:30 Wednesday, in New Delhi, Delhi, India,
14:00 Wednesday, in Brasilia - Federal District, Brazil,
12:00 Wednesday, Eastern Time (ET),
11:00 Wednesday, Central Time (CT),
09:00 Wednesday, Pacific Time (PT)
This doesn’t mean the platform will always be unavailable on this time, as this is a floating target. We will communicate any unplanned action.