TNS Waypoint Trading Connectivity, Hosting and Market Data

Transaction Network Services (TNS) provides managed infrastructure for institutional trading through Waypoint Trading Solutions. Its offering brings together connectivity to venues and counterparties, managed hosting and market data delivery. For a broker, bank or proprietary trading firm, the main question is how much of that stack to buy together. A desk with an established gateway may want a single data feed or route. A team entering a new market may need a server footprint, separate order and data connections, and a support model that covers all three.

What Waypoint provides to trading teams

Waypoint is the financial markets business presented on the TNS website. The company also operates in payments and communications, so buyers should scope the trading product by name and specify the venue, asset class and service required. For an equities deployment, for example, the initial design can identify the execution gateway, real-time feed handlers, risk systems and downstream consumers before requesting circuits or hardware. The venue’s commercial and technical onboarding processes still need their own owners.

Start with three diagrams: the order path, the data path and the operational access path. The order path should show where a client message first encounters the broker’s risk controls, where it becomes a venue message and how acknowledgments come back. The data path should show multicast delivery, recovery and where a feed handler distributes updates internally. The access path should cover monitoring and maintenance, including how engineers reach servers when the production network is unavailable. Bundling services is useful when the provider can make the interfaces between these paths explicit.

Managed hosting inside exchange facilities

TNS announced a managed hosting presence in the Tier 1 area of Singapore Exchange’s data center in 2021, together with Layer 1 raw market data and order routing. In 2022 it announced direct connectivity from within the Johannesburg Stock Exchange colocation facility, alongside managed hosting, market data connectivity and Layer 1 order routing. These are examples of venue-specific footprints. For an active procurement, obtain current availability for the requested market segment, exact facility and installation window.

A hosted server near an exchange can reduce the number of components a trading team has to procure and maintain. It also places more weight on the operating agreement. Define who owns operating system updates, who can replace hardware, how engineers receive console access and what happens when a machine must be rebuilt during market hours. Ask how many independent power and network handoffs are included in the proposed installation. A firm that controls its own hardware may instead value facility access and predictable cross-connect lead times more than a bundled server service.

TNS website announcement on its SGX colocation offering

Layer 1 access and end-to-end timing

A Layer 1 service operates at the physical layer. Its value for a latency-sensitive deployment depends on which segment it replaces and on where the firm measures performance. A device-level delay is only one component of the time between an order decision and a venue acknowledgment. The path can also include a broker’s risk engine, order gateway, cross-connect, venue gateway and return route. Capture timestamps at agreed points and identify whether published or quoted values describe one-way delay, round-trip delay or device transit.

Test the primary and recovery routes under representative load. Record the distribution of latency rather than a single minimum. An order flow can experience short periods of congestion even when average delay looks acceptable, so include bursts and open or close conditions where relevant. When two routes are proposed, ask where they share a switch, meet-me room, carrier or venue handoff. A circuit redundancy claim has practical value when the failover behavior can be demonstrated with the actual gateway and sessions the desk uses.

LTSE market data and feed selection

TNS’s announcement about the Long-Term Stock Exchange describes support for multicast MEMOIR market data, including Depth, Last Sale and Top of Book feeds. The three feeds address different application requirements. A top-of-book view can supply the best displayed prices for monitoring, while a depth feed can support applications that use multiple levels of resting liquidity. A last-sale feed serves a different purpose when the main input is completed transactions. Buyers should map each application to its required feed and verify field definitions against venue specifications.

Feed delivery is only the first part of integration. A receiver needs to detect gaps, obtain recovery data and rebuild state when required. For a depth consumer, a lost update may invalidate the local order book until recovery finishes. Test that the application flags that state instead of continuing to publish stale data. Record the exchange permissions and any redistribution rights separately from the network service. Teams that share an internal feed across applications should also establish which downstream users and systems fall within the relevant data agreement.

Acceptance tests for order routing and operations

Start by checking that the venue and provider agree on circuit identifiers, handoff locations and production versus test endpoints. Then run a complete order session that covers login, new orders, amendments, cancellations and rejects, within the venue’s approved test environment. Check how the gateway handles a lost session and whether the operations team can reconstruct open orders from authoritative records after reconnecting. Routing, venue access and clearing arrangements should each appear in the deployment plan, with a named owner for every handoff.

For monitoring, agree which party can see link state, packet drops and server health. A trading desk needs a way to distinguish stale market data from a failed order session, because the two incidents call for different responses. Set out the evidence required to raise a ticket and run one escalation exercise before going live. A fault simulation is most informative when it includes the exchange or counterparty support procedure as well as the hosting and network provider.

When TNS belongs on the shortlist

TNS is a candidate when an institution needs managed trading infrastructure across more than one market or wants hosting, network access and data delivery scoped together for a new venue. A comparison should use the same endpoints, feed types, equipment responsibilities and support windows across bids. For a single-market pilot, a useful request is a written service design paired with a live test plan. That makes it possible to compare providers on session recovery, data integrity and operational ownership alongside latency and cost.