ArbicsxPedia
···

What to do if the broker slows down

Diagnosis and solutions for performance issues. Learn how to recognize delays and which checks to perform.

Updated 16/07/2026 · 2 min read

A broker may exhibit temporary slowdowns: orders taking longer than usual, slightly delayed price updates, or non-immediate synchronization with the dashboard. In most cases, the phenomenon is temporary, but it is worth knowing how to proceed.

Riconoscere il rallentamento

Typical signs include:

  • perceived latency on orders compared to the norm;
  • delays in updating dashboard metrics;
  • temporary misalignment between what you see on the broker and what you see in the Arbicsx platform.

Not every delay indicates a structural problem: particularly active market phases, broker updates, or local network conditions can be contributing factors.

Controlli lato utente

Before taking action, perform some simple checks:

  1. verify the stability of your internet connection (speed, latency);
  2. close unnecessary browser tabs that consume resources;
  3. try an updated browser or incognito mode;
  4. restart the device if you suspect a local issue;
  5. check if other online services show slowdowns (to rule out general network problems).

If the delay is due to the local network, reducing tabs and disabling background downloads helps more than any broker-side configuration.

Controlli lato broker

If local checks do not solve it, verify on the broker side:

  • the status page or official broker announcements;
  • the presence of required updates on the broker client;
  • any technical messages visible in the operational area.

Some brokers publish real-time status indicators on their official channels. Consulting them first avoids attributing a problem to the Arbicsx platform that is occurring upstream.

Controlli lato piattaforma

If the broker seems fine but the dashboard shows delays:

Come reagire senza aggravare la situazione

The worst reaction to a slowdown is trying to force operations with repeated actions in rapid sequence. In moments of latency, every action takes longer than usual: overlapping them does not speed anything up and often makes the reading even more confusing. It is better to stop for a few minutes, verify local checks, and wait for a return to normality.

Remember that a slowdown is not a dramatic event if managed calmly. Modern platforms are designed to be tolerant of small latencies; the operational experience of long-term users also consists of knowing how to distinguish a temporary delay from a real problem.

Regola d'oro

  • Do not repeat the same actions in rapid sequence.
  • Wait a few minutes before reacting.
  • Document the occurrence if recurring.

Quando aprire un ticket

If the slowdown is not transient, or occurs repeatedly, open a ticket from support with:

  • approximate time and duration of the slowdown;
  • broker involved and setup used;
  • checks already performed;
  • any screenshots of technical messages displayed.

Remember that order execution times and the operational stability of the broker ultimately depend on the broker itself: the Arbicsx platform reads what the broker communicates to it.

Feedback

Was this guide helpful?

Need help?

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