Incident Library
Applied filters ComponentNIC, cable and switch port linkSymptomLink flappingOrganisationZerodhaClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    On 12 April 2018 at about 12.12 pm, the primary leased line to the NSE exchange on one of Zerodha's CTCLs went down, and the backup leased line that took over went up and down many times over the next 60 minutes. Orders sent through that CTCL were not placed on the exchange and stayed in the states open pending, validation pending and modify pending, leaving a small group of clients with hanging orders and positions.

    Trigger

    The primary NSE leased line on one CTCL went down at about 12.12 pm, and the backup leased line then flapped repeatedly for about 60 minutes.

    Root cause
    Component
    Contributing factor
    –
    Detection

    Zerodha received emails from the NSE-approved leased line vendor when the lines failed.

    Remediation
    • Shut the affected CTCL down completely so no new orders could go through it
    • Lapsed the orders left in pending states and reconciled them with the exchange
    Action items
    • Release an option to exit bracket and cover orders directly from the open position, even when no counter leg open order is shown
Check your cluster for this

This case involves NIC, cable and switch port link. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1