Website

Singapore Passes the Digital Infrastructure Bill: What Cloud and Colocation Customers Can Ask For

November 13, 2026 · 5 min read · Etzal Group Team

Singapore's Parliament passed the Digital Infrastructure Bill on 7 October 2026. According to a summary by law firm Baker McKenzie published on 30 October 2026, large data centres and large cloud providers will have to be licensed, manage operational resilience risk and report incidents to the Infocomm Media Development Authority (IMDA), with fines of up to S$1 million or 10% of annual turnover in Singapore.

Two limits should be clear from the start. First, the Bill has been passed by Parliament but its commencement date has not been announced. Second, the duties fall on large providers, not on customers. A mid-sized company hosting systems in a Singapore cloud or colocation facility does not become a licensee. What changes is what you can reasonably ask your provider.

What the law contains

Based on the Baker McKenzie summary:

  • The Ministry of Digital Development and Information (MDDI) introduced the Bill on 8 September 2026, and Parliament passed it on 7 October 2026.
  • IMDA administers two separate licensing regimes.
LicenceWho needs itMain duties
Foundational digital infrastructureLarge colocation and cloud data centres with a critical IT load of at least 10 MW, excluding those used only for internal purposes. Also large cloud providers whose IaaS and PaaS services earned an average of at least S$100 million a year from Singapore users over the previous three yearsAddress operational resilience risk, physical security risk management, business continuity and disaster recovery plans, report specified incidents and disruptions to IMDA
Data centre (sustainability)All operators with a critical IT load of at least 3 MWThe first step is facility-level energy efficiency requirements, including Power Usage Effectiveness (PUE)

The operational resilience risks named include technical failure, power or cooling problems, and fire.

Fines run up to the higher of S$1 million or 10% of the licensee's annual turnover in Singapore.

What is not yet available: the commencement date, the required PUE value, and incident reporting deadlines. According to the summary, details will be set in subsidiary legislation. Our source does not say which providers are caught, and we will not guess. Check the latest official announcements from IMDA and MDDI before relying on these details in a contract or internal document.

For context, the e-Conomy SEA 2026 report published by Google on 21 October 2026 refers to the binding PUE rules in the Singapore Digital Infrastructure Bill as a regional reference point for energy efficiency.

What it means for customers

The law does not hand customers new rights directly, at least not in the source we read. What it gives you is a shared vocabulary. Business continuity plans, disaster recovery, physical security and incident reporting are now things the law expects large providers to have. Asking about them no longer sounds excessive.

There is a limit too. The law targets the resilience of the provider's facilities and services. It does not make your application resilient. If your system runs in one zone with backups that have never been test-restored, a fully compliant provider will not save it.

Questions for your provider

The list below is our suggestion, arranged around the duties named in the summary.

Status

  1. Do you expect the service or facility we use to fall under this licensing regime?
  2. If so, what is your readiness plan, and will there be changes to service or pricing?

Operational resilience

  1. How are power and cooling backed up at the facility where our systems sit?
  2. When was the disaster recovery plan last tested, and may we see a summary of the result?
  3. If a facility becomes unusable, where does the load move, and is that automatic or does it need action from us?

Incidents

  1. Which kinds of incident will you notify us about, through which channel, and how quickly?
  2. Will we receive a written post-incident report?
  3. Who is our contact during an incident if the support portal is also affected?

Physical security and energy

  1. Who can enter the space where our equipment sits, and how is that recorded?
  2. What is the facility's current PUE, and will the cost of energy efficiency upgrades be passed on to customers?

Written answers are worth more than answers given in a meeting. File them with the contract.

What remains your responsibility

The shared responsibility model does not change because of this law. Several things stay with the customer:

  • Application architecture. Whether you run in more than one zone is your decision, and so is the cost.
  • Backups and restore tests. The provider looks after its facility. Your data, and proof that it can be restored, are yours to manage.
  • Access and configuration. Permission and configuration mistakes sit on the customer side.
  • The working plan for an outage. Who updates customers, which processes run manually.
  • Notifying your own parties. If a provider incident affects your customers' data, the duty to tell them is yours.

Trade-offs to anticipate

New duties on providers cut two ways for customers. On the good side, resilience and reporting discipline become more uniform among large providers. On the other, compliance costs money, and it is reasonable to expect some of that cost may reach customers. That is our expectation, not a statement from the source.

Note the thresholds as well. A provider below 10 MW, or below the cloud revenue threshold, is outside the foundational regime according to the summary. If you use a smaller provider, the questions above still deserve asking, precisely because no licence compels the answers.

Steps for this week

  1. Record which systems sit in Singapore cloud or colocation, and with which provider.
  2. Open the contract and find the clauses on incident notification, service continuity and price changes.
  3. Send the ten questions above to your account manager, with a reply date.
  4. Check when your own backup restore was last tested.
  5. Set a reminder to watch for the commencement date and the subsidiary legislation.

Contract and compliance matters depend on your own case. Confirm them with your legal counsel or the relevant authority.

If the review shows your architecture depends on a single facility, Etzal Group's enterprise software team can help assess it. You can also contact us to talk it through.

Sources

Frequently asked questions

Does a mid-sized company need a licence under this law?

No. According to Baker McKenzie's summary, licensing applies to data centre operators and large cloud providers above set thresholds, not to their customers.

When does it take effect?

Parliament passed it on 7 October 2026, but the commencement date has not been announced and details will be set out in subsidiary legislation.

How is it useful to cloud and colocation customers?

The providers' duties on operational resilience, business continuity and incident reporting can be turned into questions and contract clauses.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Website Development

Fast, SEO-ready websites that turn visitors into customers.