Purpose: The purpose of this article is to help you to find out which server you are connected to. This information could be useful in case you (or any client) experience problems and you need to find out if the issue is server-specific or if the issue extends to multiple servers.
Before you get started: Depending on which type window and instrument you are looking at, this process might differ. That said, the most important thing here is to figure out which feed (feeds are usually named after the marketplace they relate to) you are connected to. More specifically, in the example below, you can tell which feed code (and thus feed) “Hennes & Mauritz” is listed on:
Note: If you look at the abbreviation that is listed after the name of the company (highlighted in yellow), you can see that the feed code in this example is “SSE.” If you do a manual search for the feed code “SSE” in the “Find Anything” search bar, you can see that “SSE” translates to “Stockholm, Equities/ETFs/Indices”:
Step 1. Navigate to the three vertical dots in the top right corner:
Step 2. Locate the “Tools” option:
Step 3. Press on the “Communication Status” alternative:
Step 4. In this newly populated window, try to locate the corresponding feed that you are connected to (where you’re experiencing issues):
Note: All the feeds that you are connected to (via graphs, market lists, news windows, etc.) will be listed here. What you want to look for here is the IP address that will be located under “IP Address” in the middle of the communication status window.
Important: In case something is red here, that means that you cannot properly connect to a specific server. When this happens the underlying reason often has to do with your proxy settings. However, the best thing is always to reach out to our support so that we (Infront) can determine what the underlying cause for the issue is.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article