Deno Deploy dropped from 35 regions to just 12

Hi there - Kevin from the Deno team here. Thanks for starting this conversation - the recent reduction in regions is part of an ongoing effort to drive down the cost of the platform for customers. We are still learning and iterating as we figure out how to operate the service efficiently. If the new region configuration is causing major problems for you, or might prevent you from considering the service, definitely let us know by sending a message to support at Deno dot com.

Also, we can do better at proactively communicating these changes and releasing doc updates at the same time as rolling out the changes. We will document the current region list ASAP, and revisit how we communicate these changes in the future, so infrastructure configuration changes won’t be surprising.

EDIT: The docs should now have the full list of regions - https://docs.deno.com/deploy/manual/regions

The new list is not available in their documentation: https://docs.deno.com/deploy/manual/regions

This is a huge reduction in availability and quality!

For example, Seoul moved to Tokyo, response times went from 8ms to 42ms!

3x smaller network

5x slower responses

---

We hope they respond promptly, and update their documentation.

We have lost 23 cherished red dots on https://RTEdge.net (click on dots / lines for exploration), and we don't quite know which ones!

They still have the only online playground that allows WASM imports by URL!

We use Deno DOM WASM when a user deploys code on https://RTCode.io.

The deployed code is then served by the larger Cloudflare network using Workers for Platforms.

Cutting costs I presume. Should have been announced, but I'm okay with this for my hobby projects; still better than just us-east or whatever.

(Note that if you use KV, for the free tier, it's in a single region.)

I planned on using them for my next project. Now I am not even sure if they have a server in my country (Germany). Sad.

I wonder why, did they respond?