ProBackend
Cybersecurity
5 days ago7 min read

Should Dominant Tech Platforms Have Utility-Like Duties?

Should Dominant Tech Platforms Have Utility-Like Duties?

When major technology services become critical routes for users and businesses, narrowly tailored notice, appeal and continuity safeguards may be justified—without making every platform a utility.

Should dominant tech platforms have public duties?

When a technology provider controls a route that people rely on to distribute updates or keep essential services running, an account suspension can have consequences beyond one customer’s inconvenience. The question isn’t whether every large company should be forced to serve everyone. It’s whether a service with a genuinely critical public-facing role should owe users a few carefully limited procedural protections.

A Hacker News discussion offers a concrete starting point, but not proof of a general problem. One commenter said they had faced a Microsoft account suspension without warning and were in a 60-day appeal process; they worried hypothetically that this could prevent an urgent WireGuard update if a serious vulnerability were being exploited. That is an individual’s reported experience and a stated concern. Another participant argued that some providers should be regulated like utilities and should not deny service to customers in good standing. That is a commenter’s policy opinion, not a consensus or a description of existing law. Hacker News discussion

The concern is still worth examining. If a provider’s service is difficult to replace and an interruption can affect people who aren’t party to the account, a prompt explanation, usable appeal and continuity planning may be sensible. But “utility” is a blunt label. Services differ, and providers must retain the ability to respond to fraud, abuse, legal requirements and security threats. The strongest case is for narrow safeguards tied to demonstrated dependency—not unconditional access for every account.

What the thread does—and doesn’t—show

The original post in the discussion concerns Microsoft terminating an account used by VeraCrypt. A commenter then described a separate experience involving WireGuard, saying their account was suspended without warning and that they were undergoing an appeal process. Their concern about a hypothetical emergency update is explicitly framed as hypothetical. These are statements by participants in an online thread, not independently verified findings about the reasons for either account action or the prevalence of such cases. Hacker News discussion

The utility-regulation proposal appears in a reply. Its author named Microsoft, Google, Apple and payment providers, and argued that providers should not deny service to customers in good standing. Other participants offered differing views. The thread is useful as a record of concerns and opinions; it cannot establish which services are indispensable, whether a particular suspension was mistaken, or what legal duties should apply. Hacker News discussion

That distinction matters. A policy argument can take the reported experience seriously without turning it into a proven pattern. The right question is not “Did one suspension prove platforms abuse their power?” It did not. The better question is: if a service is a critical route to users, what process should apply when access is restricted?

Why the utility analogy appeals

Traditional utilities are associated with services people depend on and cannot readily replace. The analogy expresses a real worry: a private provider’s decision can have consequences well beyond an ordinary disagreement between a firm and one customer. But the comparison does not settle the remedy. Digital services have different roles and risks; search, cloud hosting, app distribution, identity services and payment networks aren’t interchangeable pipes.

Nor does size alone establish that every product is essential. Dependence may be concentrated in one service, market or use case. A provider can be a bottleneck for some users while alternatives remain practical for others. Regulation that treats an entire corporation as one uniform utility may miss that distinction.

A more useful approach identifies the service and the harm. If a particular account supports a widely used distribution channel, a suspension may warrant faster review than an ordinary consumer dispute. If the account is being used to distribute malware or commit fraud, rapid restriction may be necessary. Rules need to preserve both possibilities.

Existing rules target specific services

The European Commission describes the Digital Markets Act as a framework intended to make digital markets fairer and more contestable. It identifies gatekeepers through defined criteria and applies specified obligations and prohibitions to designated core platform services. The Commission’s Gatekeepers Portal reports service-level designations and changes, rather than treating every service offered by a large company as automatically covered. This is a targeted regulatory model, not a declaration that all large technology firms are traditional utilities. European Commission: Digital Markets Act Gatekeepers Portal

The point is not that the DMA supplies a ready-made account-appeal regime for every platform. Rather, its service-focused design illustrates why regulation can be directed at particular bottlenecks and conduct. Rules can be tailored to the function that creates dependency instead of attaching identical duties to every product under a corporate umbrella. European Commission: Digital Markets Act Gatekeepers Portal

A different example comes from the U.S. Department of Justice’s announcement about remedies in its Google search monopolization case. The department described measures addressing certain distribution agreements and access to specified search data and services. Those remedies address competition issues in search and distribution; they are not a general requirement to serve every account holder. The example reinforces a modest point: public intervention can focus on the identified market problem rather than impose a blanket utility model. U.S. Department of Justice: Google remedies

What narrowly tailored duties might look like

Where a service is demonstrably difficult to replace and interruption could create significant downstream harm, a limited procedural duty could require notice explaining the reason for a suspension when giving notice is safe and lawful. It could also provide a reachable appeal channel and timely review for high-impact cases. These are policy options, not claims that the cited sources establish a current legal entitlement to them.

Continuity deserves attention too. A process might allow a user to retrieve their own data or maintain a safe way to communicate with affected users while an appeal proceeds, where that can be done without extending harmful activity. For a provider responsible for a critical distribution route, an emergency review path could be valuable when a user says an urgent security fix or safety notice is blocked. The safeguard should be procedural; it should not guarantee that the provider must keep an account fully operational.

A workable rule needs exceptions. If advance notice would enable evasion, expose another user, or undermine an investigation, the provider may need to act first. If the suspension concerns credible abuse or a security threat, continued access could worsen the harm. A prompt review after action, with reasons supplied to the extent possible, may balance those interests better than a rigid no-suspension rule.

Why blanket obligations can backfire

A duty to serve anyone who pays could force a provider to maintain access for accounts involved in fraud, abuse or other serious harms. It could also create uncertainty about what “good standing” means, which services count as essential, and how quickly a provider must act. The Hacker News thread itself does not answer those questions; it presents an individual report and competing participant opinions, not a tested regulatory design. Hacker News discussion

Overbroad rules may also flatten meaningful differences between services. A payment network, a software hosting account and a consumer messaging product pose different operational and safety questions. The Commission’s service-level DMA approach is one reminder that the relevant unit of analysis can be narrower than the company as a whole. European Commission: Digital Markets Act Gatekeepers Portal

There is a risk on the other side, too: a vague duty of “fairness” can sound protective while leaving users uncertain about what process they can actually expect. Any regime should define its scope, preserve legitimate enforcement, and provide a review mechanism. Without those boundaries, regulation could be either ineffective or dangerously rigid.

A practical test for platform duties

Three questions make a better starting point than the word “utility.” Is the specific service a genuine bottleneck for a meaningful group of users? Could an interruption cause material harm beyond the account holder? Can a limited process—notice, appeal, continuity or review—reduce that harm without preventing action against real abuse?

If the answer is yes, targeted duties may be worth considering. If a service is readily replaceable or the proposed obligation would obstruct necessary security enforcement, a broad access mandate is harder to justify. Competition rules, portability or contractual remedies may be better suited to some problems; the DOJ’s case-specific remedies show one example of intervention directed at defined conduct rather than universal service obligations. U.S. Department of Justice: Google remedies

Organizations also shouldn’t build critical operations around the assumption that one vendor account can never be interrupted. Keep independent copies of release materials and documentation, maintain alternate ways to reach users, and understand the provider’s account-recovery process before an emergency. These are prudent resilience measures, not a substitute for fair procedures or evidence that any particular provider has acted improperly.

The thread does not settle the case for utility regulation. It makes one kind of dependence visible, through a participant’s reported suspension and concern about a hypothetical urgent update. The sensible response is neither to dismiss that concern nor to convert it into a rule that every company must serve every account. Identify the critical function, require proportionate process where the stakes justify it, and leave providers room to stop genuine abuse.

dominant tech platforms have public dutiesdominant tech platforms have public duties