Knowledge Base/Where are Massive's servers located?

Where are Massive's servers located?

Our market data platform runs in Secaucus, New Jersey, which is where the US equities exchanges and their consolidated feeds are concentrated. Hosting your own service in the same metropolitan area is the single biggest thing you can do about latency.

Secaucus, New Jersey is not an arbitrary address: the US equities exchanges and the consolidated feeds that carry their data are concentrated in northern New Jersey, so being there is what keeps Massive's own ingestion path short. The practical consequence for you is that where you run your code outweighs anything you can tune inside it.

Applies to

  • Plans: all plans. Location affects latency, not entitlement.
  • Endpoints: the REST API at api.massive.com and the WebSocket clusters at socket.massive.com.
  • Asset classes: all.

What this means for your latency

What this means for your latency is that distance is the dominant term, and you cannot optimize around it:

Where your service runsWhat to expect
Northern New Jersey or New York metroThe shortest path available to you
Elsewhere in North AmericaTens of milliseconds added, one way
Another continentWell over a hundred milliseconds added, one way

After geography, the next largest cause is your own read loop rather than the network. A client that parses in the thread that reads adds its parse time to every event, and under a burst that can grow into the same range as a transatlantic hop.

How to measure rather than estimate

Every event carries the exchange timestamp, so you can measure your real end-to-end delay instead of reasoning about hops. Subscribe to a busy channel, subtract each event's timestamp from your own arrival time, and report percentiles. Check your clock first: if any result is negative, your machine's clock differs from the exchange's by at least that much and every figure carries the same offset.

If you need facility-level detail

If you need facility-level detail, for colocation, a cross-connect or a private link, start a chat at massive.com/contact and say what you are trying to build. The specific facilities we occupy change as we add capacity, so a current answer from a person is worth more than a list in an article, and there may be an option that suits you better than matching our location.

If you see an error

Latency that grows steadily through a session is usually a slow consumer rather than geography, which ends in a disconnect once the server-side buffer fills. Check your socket's receive queue to be sure: Why is my Massive WebSocket data running behind, and is it my client or Massive? shows how.

Latency that is stable but high is geography. Moving your service closer is the only fix.

Related


Was this article helpful?

Modernizing Wall St.

Reimagining financial market data for the 21st century.

Schedule a demo

Talk with our market data experts

Recommended

Can't find the answer you're looking for? Contact our team.
  • Title
    Are all indices available through the basic subscription tier?
    Data Coverage Category

    Data Coverage

    Indices Category

    Indices

    Description
    No, and the ones it withholds are the famous ones: SPX, DJI, RUT and VIX all need a paid Indices tier. Basic still reaches more than 10,000 of the 13,000-odd indices Massive publishes, and NDX and the Nasdaq Composite are among them.
  • Title
    Does Massive offer dark pool data?
    Data Coverage Category

    Data Coverage

    Stocks Category

    Stocks

    Description
    Yes. Off-exchange prints, which include dark pool executions, arrive on the ordinary trades feed and are identified by an exchange ID of 4. There is no separate dark pool endpoint, and no way to tell which individual venue a print came from.
  • Title
    Does Massive offer pre-market and after-hours data?
    FAQ Category

    FAQ

    Stocks Category

    Stocks

    Description
    Yes. Every extended-hours trade and quote is published, from 04:00 to 20:00 Eastern. There is no session parameter, so you select a session with timestamps, and expect far fewer aggregate bars outside regular hours because many extended-hours trades are odd lots that cannot set a price.