Why Internet governance is a business risk
Working servers are not enough. Understand how address records, providers and administrative decisions become business dependencies.
Your servers are working. Your connections are working. Then a service you depend on changes its rules, becomes unavailable or refuses an essential update. Customers may feel the consequences even though none of your own equipment has failed.
That is why Internet governance belongs in a discussion about business continuity. The issue is who can change the conditions under which a business remains reachable, and what the business can do when those conditions change.
Which kind of risk are we talking about?
“Internet governance” covers several different relationships. Governments make laws within their jurisdictions. Platforms set conditions for using their services. Technical bodies develop standards. Registries coordinate names or numbers. A company may depend on all of them, but the source and limits of their authority differ.
Cross-border data rules, platform restrictions and cybersecurity obligations can affect a business. They do not explain every infrastructure dependency. A company can satisfy its legal obligations and still depend on one administrative service with no tested replacement.
How an address becomes a business dependency
Imagine a company whose customers have allowed its public IP addresses through their firewalls. Partners use the same addresses to recognize its systems. Over time, those identifiers become embedded in other people's configurations.
Changing an address is then more than changing a setting on one server. The company has to coordinate with customers and partners. Some will respond quickly; others may need a maintenance window or an internal approval. The cost comes from the relationships built around the address.
Now separate the dependencies. Who supplies the connectivity? Who holds the address resource? Who can update its registration? Who manages the routing authorization? A contract with one supplier does not necessarily give the company direct control over all four.
Why the incentives matter
Lu Heng's Note 32 describes an agency problem: the institution making an administrative decision may not bear the business losses it causes. An operator loses revenue when customers cannot connect; the administrator can continue following its procedure.
His criticism concerns the structure of power and responsibility. A rule should not be treated as harmless merely because it is called technical administration. Its effect on running networks matters, as does who carries the cost.
What can a business do now?
Start with one service customers cannot afford to lose. Trace the addresses, providers, registration records and security settings it depends on. Identify the people who can change each one, including any supplier acting on your behalf.
Then test a realistic interruption: a provider leaves, an administrative account becomes inaccessible or a required record cannot be updated. Distinguish what keeps working immediately from what becomes difficult at renewal, transfer or recovery. Not every registry interruption instantly stops every packet.
The useful result is a list of specific dependencies and recovery actions, with someone responsible for each. A broad statement that “the network is resilient” is not enough if nobody has checked the identity layer.
What should change in the system?
Individual preparation helps, but it does not create a missing replacement mechanism. Lu Heng argues for verifiable records and portable, replaceable coordination services so that protecting a network does not require preserving one administrator forever.
That is a different ambition from asking businesses to spend more time in policy meetings. Participation may help them notice a proposed change. A tested exit path changes their position when the relationship fails.
The longer customers and partners depend on an identifier, the harder an unplanned change can become. Understanding those dependencies before the next expansion gives a business more room to act.
Use the practical guide to examine one service step by step. To understand the institutional problem behind it, read Lu Heng's original argument on power and economic responsibility.