dns - Softlayer ISP 阻止网络在连接到 wp_remote_post Wordpress 时丢失

Question

我们确实正在向社区寻求帮助，我们遇到了客户网站无法再访问我的 API 并超时的问题。

Connection timed out after 10001 milliseconds. 

我们已经联系了我们的主办方媒体圣殿，他们无法给我任何解决方案，我们确实需要一些帮助。

这是我们遇到的问题的视频。

http://bit.ly/1CEIYOH

这是我们 api 的跟踪路由，它对我们的许多用户来说工作正常，但有些用户现在遇到了如下问题。

1  50.23.120.193-static.reverse.softlayer.com (50.23.120.193)  0.513 ms  0.491 ms  0.481 ms
2  ae0.dar02.sr01.sjc01.networklayer.com (50.23.118.132)  0.366 ms ae0.dar01.sr01.sjc01.networklayer.com (50.23.118.130)  0.406 ms ae0.dar02.sr01.sjc01.networklayer.com (50.23.118.132)  0.302 ms
3  50.97.19.164-static.reverse.softlayer.com (50.97.19.164)  0.775 ms  0.701 ms ae8.bbr01.eq01.sjc02.networklayer.com (173.192.18.248)  0.803 ms
4  equinix-ix.sjc1.us.voxel.net (206.223.116.4)  0.741 ms  0.794 ms  0.868 ms
5  173.231.161.193 (173.231.161.193)  48.109 ms  44.392 ms  44.397 ms
6  0.te1-2.tsr1.dal2.us.voxel.net (107.6.99.249)  79.040 ms  79.065 ms  80.685 ms
7  0.te2-2.tsr3.iad1.us.voxel.net (173.231.161.189)  78.472 ms  78.438 ms  78.414 ms
8  173.231.160.90 (173.231.160.90)  81.183 ms  81.158 ms 173.231.160.82 (173.231.160.82)  78.348 ms
9  internap.iad1.us.voxel.net (173.231.161.74)  78.815 ms  78.794 ms  78.751 ms
10  border2.te4-1-bbnet1.wdc012.pnap.net (216.52.127.39)  78.455 ms border2.pc2-bbnet2.wdc012.pnap.net (216.52.127.76)  78.282 ms  78.261 ms
11  net2ez-3.border2.wdc012.pnap.net (64.94.31.142)  79.218 ms  79.159 ms  79.094 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *

网络刚刚退出，这是媒体圣殿的回应。

We have received feedback from our provider's network engineer and he asked if your clients or the customers of softlayer open a ticket with softlayer. From what testing they have done it appears that there are some routing peering issues between various ISPs and softlayer.

新更新

From your traceroutes the commonality appears to be either Softlayer, Internap or NetDC ISPs. I've spoken with NetDC and they claim they are not filtering anything. We have also reached out to softlayer but have not heard back from them. What would help narrow this down if we can run another script like you did earlier:

另一个更新

Ok, I've reached out to Softlayer (your customer's ISP), Internap (Intermediary ISP), and NetDC (Intermediary ISP). One of them is filtering things, and I'm hoping I get a quick response from them. It is out of our control at this moment, but hopefully these ISPs will be responsive and allow us to track down whatever is blocking your customers from reaching you.

最新更新

Good news, I got a response from Softlayer just as I sent you that last correspondence.  They are seeing the same issue from their end

and they believe the issue is within Internap. They have looped in Internap as well since they are direct customers of Internap so hopefully something will be discovered.

I was able to determine that there are some ip subnets of ours that are accessible by the Softlayer router that was having issues connecting to your IP. I need to verify that we can actually migrate you to one of those IPs.

I'm having an internet routing change made so Internap will hopefully not have the preferred route to your server and thus be bypassed, I believe the issue is not limited to just your IP which is why I'm taking this more extreme step.

有人可以帮忙吗

最终更新。

最终的解决方案是完全放弃 Media Temple，在我们的客户遇到无法提供解决方案的问题 3 周后，当他们向他们提出这个明确的问题时，他们的托管确实让我们失望了。

how come i can post to any other server but media temple from the ip thats having the issue?

即使是支持人员也只是将我转移到另一个支持人员，因为他们无法回答问题。

令我担心的是，托管服务提供商为何无法修复此类问题？由于这个问题，我失去了很多付费客户。

解决方案是将所有内容移至 Amazon 并将其安装到 EC2 实例上，这是我在一天内完成的，我希望我从一开始就完成了我还安装了 3 美元的 ssl 证书，而 Media Temple 上的证书是75 美元，我还为他们的 Cloudtech 服务支付了 100 美元。

亚马逊的伟大之处在于，即使再次发生这样的错误，我也可以创建一个 AMI，然后启动一个新的 EC2 并完成工作。

每个人都要小心第三方托管的此类问题，如果您的服务依赖于 API 并且您遇到了 ISP 问题，那么如果您的托管在 3 周的尝试后找不到解决方案，那么您的业务可能会很快破产，相信我您的用户不想听到(哦，我只是在等待 Media Temple 的回复)。

因此解决方案使用 Amazon Web Service 灵活强大且完全由您控制，咆哮结束

Media Temple let us down massively.

Answer 1

您希望从社区获得什么帮助，我确信这只是 ISP 的调整，与部署或托管无关。

如果您首先检查本地的内容，然后使用虚拟程序来检查 ISP 上的不同配置，以便确认被阻止的具体内容，那就太好了。

那么您将能够轻松解决您的问题..

根据您的问题和我的知识，这是我可以提供的最佳答案