根据Hetzner官方在Reddit发的帖子中我们得到了确切的信息,德国知名数据中心服务器运营商Hetzner现已正式推出美国西部地区(位于Hillsboro, OR)的运营服务,与Hetzner美东地区一样,Hetzner 美西只提供虚拟服务器的运营,并没有像德国本土及芬兰有提供独立服务器销售。
官方的说法是:
Are the servers in Hetzner-owned DCs?
Hetzner owns and operates three data center parks that are in Nuremberg, Falkenstein and Helsinki. We do not have our own data center parks in the USA. There, we are using colocation space at other data centers.
目前已经可以在Hetzner Cloud中创建云服务器,当前只允许创建共享型云服务器,独占CPU资源的暂时不可创建。而根据披露的公开数据,我们可以知道Hetzner在美西是租了nwax的100G端口的资源,目前正式通告的IPv4段就三个/24,一个/22,还有一个/16在路上。AS号:AS212317。peer成员比较多,其中不乏一些大公司,比如cloudflare有100G,Google有150G,微软有200G,CNservers 有20G。还有xTom 还租了1G呢。
服务器应该托管在这里:https://www.qtsdatacenters.com/
更新!Hetzner官网已经发布公告,原文如下:
HETZNER CONTINUES ITS GROWTH IN THE US WITH A NEW LOCATION
West Coast – Here we come: Today, we officially launched our second location in the USA for cloud products in Hillsboro, Oregon, just outside of Portland, a location ripe for future expansion. Clients in the region can now benefit from the lower latency, and thus experience even speedier cloud performance. The region surrounding Hillsboro is nicknamed the “Silicon Forest” because so many respected international IT companies call it home.
The strategic location of Hillsboro is very exciting for us. In addition to the first location on the East Coast, this new West Coast location will allow us to provide better connections, including important links to submarine cables located in Hillsboro, which connect North America to Asia. The network connection is currently an impressive 400 Gbit/s to ensure rapid data exchange, and we will gradually improve this connection in the future.
You will now have your choice of five locations in Europe and North America, allowing you to make your cloud data geo-redundant, and thereby make your IT infrastructure more robust.
Just one year ago in Ashburn, Virginia, Hetzner launched its first location outside of Europe.
The new location at Hillsboro will host Hetzner Cloud servers mounted with AMD processors, and naturally, you will have access to all of the Hetzner Cloud features you already know and love, and at prices that are kind to your wallets.
With just a few clicks, you can configure and deploy new cloud instances, access handy features around the clock, mount or remove other resources such as block storage and snapshots, and scale your cloud resources up or down to meet your hourly needs.
GO WEST, CLOUD FANS!
原文链接:https://www.hetzner.com/news/12-22-cloud-usa/
测试地址:https://hil-speed.hetzner.com/
粗略看一下路由,国内路由过去延迟较理想,160ms前后,非优化线路有这个延迟可以了。
您也可以联系文章作者本人进行修改,若内容侵权或非法,可以联系我们进行处理。
任何个人或组织,转载、发布本站文章到任何网站、书籍等各类媒体平台,必须在文末署名文章出处并链接到本站相应文章的URL地址。
本站文章如转载自其他网站,会在文末署名原文出处及原文URL的跳转链接,如有遗漏,烦请告知修正。
如若本站文章侵犯了原著者的合法权益,亦可联系我们进行处理。
hi6个月前0
请问有详细一点的自己搭建的教程吗你好7个月前0
你好,可以再帮我看看吗? 我已经按照你的方法设定了,还是一样,wordpress后台的 Purge Varnish Cache 插件还是清除不到cache,依旧显示 the varnish control terminal is not responding at。谢谢https://mjj.today/i/Srk2Tz https://mjj.today/i/Srkcoi你好7个月前0
对,你说的没错,我配置的时候改了一些东西,现在我按照你的教学,可以启动了,网页可以缓存了,不过wordpress 清除cache 那个插件没用的,我输入本地回环地址127.0.0.1 :6082 ,再输入API key ,插件显示the varnish control terminal is not responding at 127.0.0.1:6082,就你图片那样,然后试一下点击清除cache 那里,他显示error,研究了一天,还是没有不行。你好7个月前1
你好,为啥我按照你的方法,到第三部分,去到真正后源的服务器设定Varnish 部分,我填了真正后源的IP跟端口跟域名,然后重启 Varnish ,就出现这样了? 这是怎么回事? 谢谢[Linux] AMH 7.1 https://amh.sh[varnish-6.6 start] ================================================== =========== [OK] varnish-6.6 is already installed. Could not delete 'vcl_boot.1713549650.959259/vgc.sym': No such file or directory Error: Message from VCC-compiler: VCL version declaration missing Update your VCL to Version 4 syntax, and add vcl 4.1; on the first line of the VCL files. ('/home/usrdata/varnish/default.conf' Line 1 Pos 1) ...#---Running VCC-compiler failed, exited with 2 VCL compilation failedchu7个月前0
很完善的教程‘hu7个月前0
我用gmail EMAIL_SERVER="smtp://********@gmail.com:bpyfv*********chry@smtp.gmail.com:587"叽喳7个月前0
MAIL_SERVER="smtp://no-reply@vort.me:password123@wednesday.mxrouting.net:587"大佬 这个使用outlook 或者gmail 是什么样子的格式? 邮寄已经开启smtp了hu7个月前0
输入框的问题解决了,我没有设置反代,NEXTAUTH_URL改为域名+端口就好了