NSE Co-Location Case: SEBI’s September 2024 Order and Market-Fairness Lessons
Co-location reduces latency by placing trading servers near exchange systems. The regulatory question is whether access architecture and controls provide fair and transparent opportunity.
Current position
On 13 September 2024, SEBI issued an order in the matter of NSE and others concerning co-location. The order dismissed the notices in that proceeding because the alleged violations were not established on the available record, while discussing policy and system-design concerns. It should not be rewritten as proof that every historical issue or separate proceeding vanished.
Key facts at a glance
| Order date | 13 September 2024 |
|---|---|
| Outcome in that proceeding | Specified charges were not established and notices were disposed of |
| Subject | Co-location access and alleged unfair advantage |
| Nuance | A case-specific dismissal is not a universal approval of every practice |
What this means in practice
Speed is a market input
Professional traders value microseconds because queue position and execution probability can affect returns. Exchanges therefore need transparent access rules and monitoring.
Evidence must match the allegation
A fairness concern does not automatically prove that a named person received an unlawful advantage. Orders turn on rules, data, causation and evidence.
Policy can improve after a case
Even where charges are dismissed, regulators and exchanges can strengthen architecture, randomisation, audit trails and equal-access processes.
Practical example
Two members pay the same co-location fee, but one repeatedly connects earlier because server allocation and dissemination sequences are not controlled. The exchange should test architecture and equal opportunity before a legal dispute arises.
A practical decision framework
1. Define the exact claim
Identify the entity, product, transaction, period and legal forum. Do not apply a headline about one company, order or market event to a different fact pattern.
2. Reconcile the economics
Trace the claim to cash flow, balance-sheet exposure, contractual rights and the measurement definition. Separate revenue from transaction value, profit from liquidity and allegation from final outcome.
3. Check the operative record
Read the latest primary document and note whether it is a policy paper, interim order, final order, judgment, agreement, filing or historical report.
4. Convert the lesson into a control
Assign an owner, deadline, evidence requirement and escalation threshold. A lesson is useful only when it changes a decision or control.
Action checklist
- Read the September 2024 order and its defined scope.
- Separate technology design issues from proved misconduct.
- Maintain equal-access and latency monitoring.
- Preserve complete connection and dissemination logs.
- Track separate appeals or proceedings independently.
Evidence and document checklist
- SEBI and appellate orders
- Exchange architecture and access policies
- Connection, multicast and tick-by-tick logs
- Member allocation and complaint records
- Independent system audits
Common mistakes and red flags
Common mistakes
- Calling the order a finding that no co-location concern ever existed
- Treating milliseconds as economically irrelevant
- Ignoring the evidentiary standard for named parties
- Combining different proceedings into one outcome
Red flags
- Architecture changes lack documented testing
- Logs cannot reconstruct member access
- Policy exceptions favour selected participants
- Article cites only a news summary, not the order
Escalation route
For regulated products or proceedings, start with the responsible entity’s grievance or compliance channel and preserve written records. Use the relevant regulator, exchange, court or tribunal process where applicable. Obtain specialist advice before a limitation period, filing deadline, tax position or material right is affected.