WazirX Went Offline as Record Indian Crypto Volume Overwhelmed Its Servers

WazirX became inaccessible on April 4, 2021 after a surge in traffic overwhelmed the Indian cryptocurrency exchange’s ability to add server capacity. The disruption began as intermittent access problems at around 10:00 p.m. India Standard Time and expanded until both the application and website were unavailable, according to the company’s post-incident report.

The outage mattered beyond one venue. WazirX was handling a record burst of activity during a period when cryptocurrency participation in India was accelerating, yet its inability to scale prevented customers from viewing balances or trading normally at the moment demand was greatest. The event exposed a basic market-structure risk: a continuously traded asset does not guarantee continuous access through every intermediary.

Record demand met an infrastructure limit

Before the failure, founder and chief executive Nischal Shetty said on April 4 that WazirX had exceeded $270 million in trailing 24-hour trading volume, which he described as a record for an Indian cryptocurrency exchange. That was a company claim, not an independently audited industry ranking. The measurement was also a rolling window, so it should not be read as an April 4 calendar-day total.

WazirX’s later postmortem said the platform had recorded $350 million in 24-hour volume and that its WRX exchange token had reached an all-time high. The postmortem did not specify the exact cutoff, venue set, price pair or methodology for either claim. Contemporaneous reporting indicates the $350 million figure was reached on April 5, after the earlier $270 million reading on April 4. The two numbers therefore appear to describe different rolling windows rather than a single event-day total.

The company attributed the failure to an internal rate limit imposed by a third-party service provider used by its automatic-scaling system. When that component stopped allowing new server instances, existing servers had to absorb both established and incoming users. WazirX said the load eventually clogged the servers and made the service completely inaccessible.

That explanation is directly attributable to WazirX; the company did not identify the provider or publish server logs, capacity metrics or an independent technical audit. The surviving record supports the occurrence and reported mechanism of the outage, but not an outside reconstruction of every system failure.

Trading returned after the date changed in India

WazirX said its team worked through the night and brought the product back at 5:30 a.m. IST on April 5. Measured from the approximately 10:00 p.m. first reports, that is roughly seven and a half hours, although the beginning was gradual and reports after restoration still described intermittent errors. It should not be treated as a precise interval of uniform, systemwide downtime.

During the disruption, users reported zero balances and delayed or missing trade displays. Shetty said the zero readings resulted from failed display services and assured customers that wallets and funds were safe. That was the exchange operator’s contemporaneous assurance; the cited records do not include a third-party proof-of-reserves review, wallet audit or complete reconciliation of affected orders.

Why April 4 mattered

The episode paired evidence of rapidly expanding Indian demand with evidence that market access had not scaled at the same pace. A record-volume claim could signal commercial growth, but an outage during that volume also demonstrated concentration and operational risk for customers dependent on a single exchange interface.

What was verified on April 4 was a demand-driven service failure, not a hack or reported loss of customer assets. The causes, recovery time and safety statements came principally from WazirX and were corroborated by contemporaneous Indian press reports. No claim about later ownership disputes, security incidents, legal outcomes or customer recoveries belongs in the event-day record.