3 ms·
No they knew it but this particular feed having the issue is an older NASDAQ feed. NASDAQ's newer feed doesn't have this issue but a lot of major institutions
by Kranar 5y ago
No they knew it but this particular feed having the issue is an older NASDAQ feed.
NASDAQ's newer feed doesn't have this issue but a lot of major institutions don't like updating their infrastructure so they stick to the older feed.
To be honest, it's not nearly as big of a deal as it's being made out to be. It's not a situation where NASDAQ was ignorant of this issue or neglectful, it's a situation where NASDAQ has to balance support for legacy systems by not doing a binary incompatible update to a protocol that has worked well for many users for 20 years... versus pushing older institutions to update to their newer technology which doesn't have these issues.
- jeffbee 5y agoThe fact that it only affects the old protocol might not comfort its users. Users have this crazy habit of not migrating. I remember when Reuters bought Bridge and they tried to announce they were deprecating the bridge feed protocol, twenty years ago, but it looks like you can still get Bridge feeds and Bridge Station to this very day.