The exchanges do send the information to the SIP at the same time that they publish it on their own direct feed. NYSE actually got in trouble for not doing this properly. This isn't actually an easy problem, because there is a TCP interconnect with the SIP, and if it gets bogged down, then the SIP packets can be backed up.<p>The real issue is that since the SIP (CQS/UQDF) are cheap; and big/sophisticated players don't actually use them, no one cares about them. Beyond that the performance is necessarily slower than a direct feed, because if I wanted to learn the price of a NYSE listed-security on NASDAQ the path that the SIP would take is far less direct. Specifically, if I have a machine sitting in Carteret (Nasdaq), listening to the proprietary Nasdaq feed, the data from Nasdaq will be sent to me and the SIP at the same time. But to get it from the SIP it has to go to Mahwah and then back, instead of staying local to the data center.<p>Nasdaq makes its feed available to everyone, for a cost. Someone who is providing execution services, or market making, needs the direct feeds so they can provide good execution and know when to get out of the way. A small investor looking at a screen doesn't care about the SIP or a direct feed. They are going to submit their order, and their broker is responsible for executing it.