Summary

  • Imteaz Chowdhury’s APNIC account of Bangladesh’s July 2024 shutdown asks which locally delivered services still depend on infrastructure outside the economy.
  • Sumon Ahmed Sabir’s APNIC 62 slides identify foreign DNS, cloud components, remote APIs and time synchronisation as dependencies that can break local services during isolation.

Imteaz Chowdhury remembers the Bangladesh shutdown as a failure of ordinary tools, then asks a better question: what would have kept working? In his APNIC account, he writes that messages, websites and business tools stopped during the July 2024 disruption while an ordinary phone call still worked. The memory is personal; the operational test comes from an APNIC 62 presentation by Sumon Ahmed Sabir of Fibre@Home.

Sumon’s official slides list the dependencies that turn a local network into a remote service: DNS resolvers hosted abroad, cloud application components, remote APIs, time synchronisation and mobile payment systems. A local app can have a local user and still fail because one script, clock or payment call lives elsewhere. The outage exposes the dependency map only after the service has stopped.

APNIC’s author page identifies Chowdhury as a Dhaka-based writer who worked through the shutdown. His article’s useful move is to replace a capacity boast with a continuity question: how much of a network continues to work when international connectivity disappears? More bandwidth and another route can help. They do not tell an operator which functions require a foreign resolver or API.

The first audit is practical. List the local services, name every external dependency, run without the international link, and record which fallback is real rather than promised. The source does not provide a measured pass rate for Bangladeshi services. That missing test is the fact that would change the assessment.