Error message

Dedicated IP did not respond: the request went out through this account's dedicated IP and no reply came back in time

Last updated 6 August 2026

Dedicated IP did not respond (no reply in time)

In short

This message means the connection through your account's dedicated IP was made, but no reply came back before time ran out. This one is different from the other IP errors in an important way: we cannot tell you whether the request reached your broker or not. It may have been a slow moment at the IP, or a slow reply from the broker. So before you try the same order again, open your order book and check whether it is already there. If it is, do not place it a second time. If it is not there, wait a few moments and try again. You do not need to change any setting, password or API key. If this keeps happening, contact our support team with the account name and roughly when it happened.

When this happens

  1. 1 The dedicated IP was slow or briefly overloaded, so the reply did not come back in time.
  2. 2 The broker's own system was slow to reply, and the wait ran out before the answer arrived.
  3. 3 Your own IP (BYOIP) is dropping some traffic, so replies are lost on the way back.

What this message means

Your account’s requests go out through a dedicated IP. This message means the connection to that IP was made, the request went out, and then no reply came back before the waiting time ran out.

That is the whole difference between this message and the other IP errors. In the others, the request clearly stopped at the IP and never reached your broker. Here, it went out — and we cannot tell you how far it got.

Dedicated IP did not respond: the request went out through this account’s dedicated IP and no reply came back in time.

Important: check your order book first

Because we cannot tell how far the request got, the order may already be at your broker.

Before you place the same order again:

  1. Open your order book and refresh it.
  2. Look for the order you were trying to place.
  3. If it is there, the request did reach your broker. Do not place it again.
  4. If it is not there, nothing went through. Wait a few moments and try again.

This is the one IP message where placing the order a second time can give you two orders instead of one. The other IP errors stop the request before the broker sees it, so with those it is always safe to retry.

Why we do not name a single cause

An honest answer is more useful here than a confident one. Once the connection is made and the request has gone out, a missing reply can come from either side:

  • the dedicated IP was slow, busy, or losing some traffic, or
  • your broker’s own system was slow to answer.

Both look exactly the same from where we sit. So this message tells you what we actually saw — no reply in time — instead of blaming your IP or your broker for something we cannot prove.

How to fix it

  1. Check the order book first, as above. This matters more than anything else on this page.
  2. Try again after a few moments. A one-off slow reply is common and usually clears by itself.
  3. Do not change your settings. Your broker login, API credentials and IP details are not the cause, so changing them will not help.
  4. If it keeps happening, look at how often. A single message now and then is normal on any network. The same message again and again, on the same account, points at a real fault.
  5. If you use your own IP (BYOIP), open Settings → My IPs, go to the Proxy pool tab, and ask the vendor you bought the IP from whether it is dropping traffic. A proxy that loses some packets — rather than failing outright — produces exactly this pattern: mostly working, with regular timeouts mixed in.
  6. If it keeps happening, contact us. Reach our support team with the account name and roughly when it happened. If the IP came from our pool, this one is ours to chase.

How this is different from other IP errors

The four messages below look similar but mean different things. This one is the only one where the broker may have seen your request.

  • “Dedicated IP did not respond” (this page) — the request went out, no reply came back. Check your order book before retrying.
  • “Dedicated IP not reachable” / “Connect timed out” — nothing answered at the IP at all, so the request never went out. Safe to retry. See Connect timed out to your own IP.
  • “Dedicated IP gateway error” — the IP answered with an error page of its own instead of passing the request on. The broker never saw it. Safe to retry. See Dedicated IP gateway error.
  • “Proxy Authentication Required” (407) — the IP answered and refused you, usually over a wrong username or password. Here you do need to check your IP details. See Dedicated IP authentication failed.
Did this solve your problem?
Contact support