MLink Stripes

MLinkStream allows users to stripe their connections based on pre-defined sets of tickers (tk), indexes, or exchanges (ts) in order to either balance the load on the receiving end and/or segment. This is especially useful if you are trying to distribute the incoming message load, or are interested in tickers within specific stripes. An example of striped connections (1 Stripe = 1 WebSocket connection) can be found here.

Native OPRA / NMS Stripes (EQT)

Stripe	startTicker	endTicker
A1	A	AMZN
A2	AMZN	COIN
B1	COIN	ENQZZ
B2	ENQZZ	GOOGL
C1	GOOGLE	IWM
C2	IWM	LRCX
D1	LRCX	METAA
D2	METAA	NFLX
E1	NFLX	NVDA
E2	NVDA	NVDAA
F1	NVDAA	QQQ
F2	QQQ	QIQA
G1	QIQA	SPY
G2	SPY	SPYA
H1	SPYA	TSLAA
H2	TSLAA	ZZZZZZ

Compound OPRA / NMS Stripes (EQT)

Stripe	Start Stripe	End Stripe
A	A1	A2
B	B1	B2
C	C1	C2
D	D1	D2
E	E1	E2
F	F1	F2
G	G1	G2
H	H1	H2

Index Source Stripes

Stripe	Ticker Source
I1	CDIX
I2	DJI
I3	RUT
I4	MIAX

Compound Index Source Stripe

Stripe	Ticker Source
I	I1:I4

OTC / Mutual Fund / Other Source Stripes

Stripe	Ticker Source
J1	OTC
J2	MFQS
J3	CUSIP
J4	ISIN
J5	SR

Compound OTC / Mutual Fund / Other Source Stripe

Stripe	Ticker Source
J	J1:J4

Market Indexes Stripes

Stripe	Tickers
M1	NDX,NDXP,RUT,RUTW,MRUT
M2	SPY, VXX
M3	QQQ
M4	IWM

Compound Market Indexes Stripe

Stripe	Tickers
M	M1:M4

SPX Stripe

Stripe	Tickers
S	SPX,SPXW,XSP,VIX,VIXW

GTH Stripes

Stripe	Ticker Source
V	CFE
X1	CME
X2	CBOT
X3	NYMEX
X4	COMEX

Compound GTH Stripe

Stripe	Ticker Source
X	X1:X4

Note that stripes are exclusive. If a ticker is found within a specific stripe, it will not be available in another.