en.wikipedia.org/wiki/DigitalOcean
2 corrections found
with 15 globally distributed data centers.
This count is outdated. DigitalOcean’s own current documentation says it has 16 datacenters across 13 regions, and its infrastructure page says 20 distributed datacenters.
Full reasoning
DigitalOcean’s current official documentation contradicts the article’s count of 15 data centers.
- DigitalOcean’s Regional Availability documentation, last verified on August 10, 2026, says: “DigitalOcean has 16 datacenters across 13 regions.” It then lists NYC1, NYC2, NYC3, AMS3, SFO2, SFO3, SGP1, LON1, FRA1, TOR1, BLR1, SYD1, ATL1, RIC1, MKC1, and MEM1.
- DigitalOcean’s Global Infrastructure page likewise says the company has 20 distributed data centers in 12 regions.
Either way, DigitalOcean’s own current materials show the company has more than 15 data centers, so the statement in the article is no longer accurate.
2 sources
- Regional Availability | DigitalOcean Documentation
Last verified 10 Aug 2026 ... DigitalOcean has 16 datacenters across 13 regions.
- Global Infrastructure | DigitalOcean
DigitalOcean provides robust infrastructure and reliable network connectivity to businesses around the globe, with a growing list of 20 distributed data centers in 12 regions.
This law led to a temporary block in April 2018 of Google, Amazon, Azure, and DigitalOcean, among others, in Russia by Roskomnadzor as a hosting provider for Telegram Messenger and VPS services.
The 2018 blocking was tied to Telegram’s refusal to hand over encryption keys, not to Russia’s personal-data-localization law.
Full reasoning
This sentence misstates why Russia blocked those cloud providers’ IP addresses in April 2018.
Freedom House’s 2018 Russia report says that in April 2018 authorities blocked Telegram “for refusing to provide encryption keys to the Federal Security Service.” It then explains that when Telegram worked around the ban, Roskomnadzor targeted additional IP ranges, including cloud services such as Amazon Web Services, Google Cloud, Microsoft Azure, and Alibaba Cloud, causing broad collateral blocking.
A contemporaneous Reuters report says Roskomnadzor began blocking Telegram after it refused to comply with a court order to grant state security services access to users’ encrypted messages, and then blocked Google and Amazon IP addresses because they were being used by Telegram.
So the April 2018 blocking did not happen because of Russia’s data-localization law; it happened as part of the campaign to enforce the Telegram ban over encryption-key access.
2 sources
- Russia: Freedom on the Net 2018 Country Report | Freedom House
In April 2018, authorities blocked the communication app Telegram for refusing to provide encryption keys to the Federal Security Service ... Roskomnadzor then targeted these other hosting sites, which included Amazon Web Services, Google Cloud, Fiber, Microsoft Azure, and Alibaba Cloud, resulting in extensive collateral blocking.
- Russia blocks Google, Amazon IP addresses in bid to ban Telegram
Russia's Roskomnadzor watchdog began blocking Telegram ... after it refused to comply with a court order to grant state security services access to its users' encrypted messages.