Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsSoftLayer’s Asia-Pacific expansion began in 2011 with a data center in Singapore and network points of presence in Singapore, Tokyo and Hong Kong. IBM acquired SoftLayer in 2013, then committed $1.2 billion to expand its cloud footprint. A Tokyo data center followed in December 2014, turning an initial network presence in Japan into local cloud capacity.
How SoftLayer first entered Asia-Pacific
SoftLayer’s 2011 regional launch combined one data center—in Singapore—with network points of presence (PoPs) in Singapore, Tokyo and Hong Kong. A PoP is a network location that can improve connectivity; it is not, by itself, a data center offering local compute and storage.
The distinction matters when interpreting the early footprint: the 2011 announcement establishes a Tokyo PoP, not a Tokyo data center. SoftLayer said it had 23,000 customers across more than 140 countries at the time, with almost half outside the United States. Its CEO, Lance Crosby, described the launch as bringing SoftLayer’s hosting solutions to Asia-Pacific.
What changed after IBM acquired SoftLayer
IBM completed its SoftLayer acquisition on July 3, 2013, for $1.977 billion. It combined SoftLayer with IBM SmartCloud in a new cloud business, using SoftLayer as a foundation for IBM’s cloud infrastructure strategy.
IBM’s acquisition announcement described SoftLayer as having approximately 21,000 customers and 13 data centers before the acquisition. That figure is a separate company snapshot from SoftLayer’s 2011 launch announcement; the two customer counts are dated differently and should not be read as a like-for-like growth comparison.
In 2014 investor material, IBM described a $1.2 billion commitment to double SoftLayer’s data centers and a target of 40 cloud data centers in 15 countries. The $1.2 billion was an expansion commitment, not the acquisition price, and the 40-center figure was a target rather than proof that every planned site had opened.
Where the Asia-Pacific facilities were—and when
| Location | What the announcements establish | What that means |
|---|---|---|
| Singapore | SoftLayer’s 2011 announcement identified a data center and a network PoP. | It was the region’s initial confirmed data-center location. |
| Tokyo | A network PoP was part of the 2011 launch. IBM opened its first SoftLayer cloud data center in Japan in Tokyo in December 2014. | The PoP preceded the local cloud data center by several years; the two are distinct infrastructure milestones. |
| Hong Kong | A network PoP was identified in the 2011 announcement. IBM’s 2014 announcement listed Hong Kong among the locations complementing Tokyo. | The cited announcements establish network presence, but do not specify a Hong Kong SoftLayer data-center opening date. |
| Melbourne | IBM’s 2014 Tokyo announcement listed Melbourne among the locations complementing the new Tokyo facility. | The cited announcement establishes Melbourne as part of the regional footprint context, but does not give its opening date or facility details. |
IBM reported that its Japan cloud customer base grew by more than 600% from Q3 2013 to Q3 2014, and that it had more than 1,000 Japanese SoftLayer IaaS customers when it announced the Tokyo facility. These are IBM-reported figures for that historical period, not measures of current customer totals.
Why a Tokyo data center mattered beyond network speed
A Tokyo PoP could improve network connectivity without placing an application’s compute and storage in Japan. A local data center added the possibility of running workloads and storing data there. IBM presented the Tokyo site as a response to demand for local capacity, data residency, privacy, redundancy and security, particularly for sensitive workloads.
For a financial institution or another organization handling regulated or sensitive information, local infrastructure can be one part of a data-location strategy. It does not, on its own, establish that an application meets a law, regulator’s requirements, contractual obligations or a company’s security controls. Those conclusions depend on the specific workload, data flows, service terms and applicable rules; the historical announcements do not establish compliance for any particular customer.
IBM’s stated rationale also included geographic diversity and resiliency. A second location can support continuity planning, but a data-center count alone does not demonstrate that a workload is redundant: the design must account for replication, network paths, failover and recovery procedures.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How IBM described the infrastructure design
IBM’s design materials presented network, compute and storage as an integrated cloud platform rather than isolated facilities. They emphasized owned networking, visibility and control, automation, IPv4/IPv6 dual stack, DNS, DDoS mitigation and internet-exchange connectivity, alongside security and geographic diversity.
That integrated model helps explain why expansion involved both physical sites and network presence. A regional PoP can contribute connectivity; a data center can add local compute and storage; the platform’s network and management systems connect those resources. IBM’s materials describe the design goals, but do not provide a like-for-like cost comparison among Singapore, Tokyo, Hong Kong and Melbourne.
What the expansion does—and does not—tell us today
The documented milestones describe the 2011–2015 expansion period. They explain how SoftLayer established a regional foothold, how IBM repositioned it within its cloud business, and why IBM linked local infrastructure with residency, resiliency and security requirements.
They do not establish IBM Cloud’s current regional inventory, present-day branding or service terms. A historical announcement that a location was part of the footprint is not sufficient evidence that a particular service is available there today.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
