HFTFeed.Client 1.1.2: the feed has a stable host name

HFTFeed.Client 1.1.2 is on NuGet. It changes one thing: the default host is the name fix-server.hftfeed.com instead of the IP address that 1.1.0 and 1.1.1 had built in.

dotnet add package HFTFeed.Client --version 1.1.2

The API, the ports, the FIX session behaviour and everything else are unchanged from 1.1.1. Upgrading is a version bump and a rebuild.

What changed

HFTFeedClient.DefaultHost is now "fix-server.hftfeed.com". The two-argument constructor uses it, so this connects to the name:

using var client = new HFTFeedClient("you@example.com", "your_password");

The name is resolved on every connect. Two consequences for your deployment:

• The machine running your client needs DNS in addition to outbound TCP on port 9030 (or 9031).
• In your firewall, allow the name, not an address. An address allow-list will keep working only until the address changes.

If you pass an explicit endpoint with new HFTFeedClient(email, password, host, port), pass the name there too.

Why it matters

Until now the feed's address was compiled into the SDK. That is fine while the address never changes, and a problem on the day it does: every customer would need a new build to reach the feed again, and nothing we could do on our side would help them in the meantime.

With a name, moving the feed to another address is a DNS change. Clients pick it up on their next connect, and nobody has to rebuild, redeploy or edit a configuration file.

There is history behind this. Between 11 and 17 September 2026 fix-server.hftfeed.com had no record of its own and was answered by our *.hftfeed.com wildcard with the website's address, which refuses FIX connections. That is why 1.1.0 and 1.1.1 shipped the address instead. The name has had its own record since 17 September 2026, and it is again the only endpoint we publish.

If you wrote your own FIX client

Nothing about the protocol changed, but the same advice applies: set the host in your FIX engine's session settings to fix-server.hftfeed.com. The connection details in the FIX protocol reference and on your Connection page show the name, and the rest of the session is as it was: port 9030 (9031 is the alternate), FIX.4.4, TargetCompID FixServer, SenderSubID and TargetSubID QUOTE, and one live session per account.

Upgrade

dotnet add package HFTFeed.Client --version 1.1.2

Then rebuild. There is no code change to make, and no behaviour to re-test: 1.1.2 is 1.1.1 with a different default host. If you are still on 1.1.0, read the 1.1.1 post first: it describes the connection pacing and the Stop() change that came with that release. Versions 1.0.x remain unsupported.

Check what the feed carries

The instruments we stream are now listed publicly at hftfeed.com/symbols, with no sign-in: the tag 55 key you subscribe with, the symbol name, the asset class and the number of price decimals. The page is generated from the feed server's own live configuration, so it cannot list a symbol the feed does not carry.

In your own code, GetSymbols() returns the same list for your session after Start().

Get it

• Package: HFTFeed.Client on nuget.org
• Guide: Connect with the .NET SDK
• Reference: HFTFeed.Client API reference