Scheduled maintenance consists of technical interventions planned in advance that may involve short windows of reduced availability or targeted slowdowns. They are a standard operational tool to keep the platform efficient over time.
Why they are necessary
Certain interventions cannot be performed live without compromising stability: major infrastructure updates, critical component migrations, and extensive checks requiring a more controlled environment. We prefer to plan them in low-impact windows rather than risking unannounced interruptions.
How they are announced
- notification in the reserved area with reasonable notice;
- possible informational banner in the dashboard in the days immediately preceding;
- dedicated page in the Updates section with date, time, and scope of the intervention.
What to expect during the window
During a maintenance window, it may happen that certain functions are temporarily unavailable, a screen displays a dedicated message, or synchronization with brokers is suspended. These effects are expected and fall within the declared window. Your operations on the broker side, when applicable, do not depend on this window: the platform is a monitoring and management tool, not the order execution channel.
What to do before
If you know in advance that there will be maintenance, avoid scheduling activities particularly sensitive to real-time dashboard access during that window: manual renewals, configuration changes, or initial readings of important metrics. Postponing by a few hours when possible is the safest choice.
Scheduled maintenance is planned and communicated. An unforeseen interruption is different and is handled as an incident, with specific communications as soon as they are available.
What to do during
During the window, avoid opening a ticket to report the same maintenance already announced: it would increase the support queue without producing any useful result. If you observe something that goes beyond what was announced, in that case a ticket is useful: describe it as indicated in How to send an effective request.
What to do after
At the end of the window, the platform returns to full availability. If you had postponed sensitive activities, resume them with a check of the main dashboard views. A quick comparison between pre- and post-maintenance data will confirm that everything is back in line.
Transparency on timing
Announced windows have a tolerance margin: they may close earlier than expected or require a few extra minutes. In the rare case that maintenance exceeds the scheduled window, an update is issued in the Important communications.
Scope
Maintenance concerns the technology. Arbicsx provides software in accordance with D.Lgs. 58/1998 (TUF); no returns are promised nor do they depend on the instantaneous availability of our monitoring tools.
Was this guide helpful?
If this guide wasn't enough, our team is available.
Every request is routed to the correct channel. Contact us and receive a structured reply as quickly as possible.
Go to support