Next steps
Policy prescription · Tier 1
Grounding verified
Jul-Aug 2024 ~10 days; mobile + broadband simultaneously
The risk is not theoretical. As the note records, in July to August 2024 Bangladesh experienced a shutdown of roughly 10 days in which mobile and broadband were cut simultaneously. That detail matters: a simultaneous cut of both rails removes the usual fallback (when mobile data fails, fixed broadband often holds, and vice versa), so a joint shutdown is a near-total information blackout rather than a degradation. It severs banking and mobile financial services, freight and export documentation, telemedicine, e-government, remittance inflows, and the ordinary commerce of a digitized economy, all at once.
The deeper problem is institutional, not technical. The shutdown was feasible because the legal and procedural path to ordering one is short, opaque, and reversible only by the same hand that imposed it. There is no published trigger, no independent check, no fixed expiry, and no requirement to disclose who ordered what and why. Until that process is constrained, the next blackout is a phone call away. The lead responsible body is the ICT Division (ICTD), which owns the connectivity continuity mandate and convenes the supporting bodies (Bangladesh Computer Council, Bangladesh Hi-Tech Park Authority, Ministry of Science and Technology).
Start with action 1: the due-process circular is low-cost, needs no new agency, and immediately converts an unconstrained power into a documented, time-bound, reviewable one. That unlocks action 3 (the review panel and public register have something concrete to police) and action 2 (the dual-rail ban becomes an enforceable rule rather than an aspiration). Action 4 builds in parallel, since the resilience unit and dashboard take longest to stand up. Action 5 follows once the rules exist, because parks can only be held to a standard that has been written down.
The binding constraint is political: a sitting executive rarely surrenders a fast, deniable lever willingly, so the reform must be framed as protecting commerce, payments, and exports rather than as curbing authority. The fiscal constraint is modest but real: the resilience unit and dashboard need a standing budget line, not a one-off grant, or they decay. Operator compliance is the third risk; the critical-services whitelist must be negotiated, not decreed, to be honored under pressure.
The July to August 2024 episode showed that a roughly 10-day simultaneous mobile-and-broadband blackout is procedurally easy, which is precisely why it is dangerous. The fix is to make blackouts legally hard, time-bound, reviewable, and dual-rail-prohibited, led by the ICT Division through circular, rule, and a funded resilience unit, before the next crisis tempts the next order.
The figures and responsible bodies cited in this prescription are drawn from the platform's own data and the GovTwin registry listed below.
Drafted by an Opus writer grounded in the facts above. Where the prescription cites a figure, it is drawn from those facts. The diagnosis derives from the BDPolicyLab crisis taxonomy; the responsible body and budget from the GovTwin registry. Recommended actions are the think tank's policy judgment.
Source: BDPolicyLab crisis taxonomy, cited primary facts, and GovTwin registryAs of 2026-06-07T09:07:36.836788+00:00Verified