北京联通宽带的朋友们连 linode 东京机房有问题吗？

V2EX = way to explore

V2EX 是一个关于分享和探索的地方

已注册用户请登录

通过以下 Referral 链接购买 DigitalOcean 主机，你将可以帮助 V2EX 持续发展

这是一个创建于 2420 天前的主题，其中的信息可能已经有所发展或是发生改变。

从昨晚开始就不正常了，丢包太严重

ping speedtest.tokyo.linode.com
PING speedtest.tokyo.linode.com (106.187.96.148): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 106.187.96.148: icmp_seq=1 ttl=52 time=81.051 ms
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 106.187.96.148: icmp_seq=5 ttl=52 time=81.657 ms
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
64 bytes from 106.187.96.148: icmp_seq=8 ttl=52 time=81.525 ms
64 bytes from 106.187.96.148: icmp_seq=9 ttl=52 time=82.260 ms
Request timeout for icmp_seq 10
64 bytes from 106.187.96.148: icmp_seq=11 ttl=52 time=80.916 ms
64 bytes from 106.187.96.148: icmp_seq=12 ttl=52 time=81.205 ms
Request timeout for icmp_seq 13
64 bytes from 106.187.96.148: icmp_seq=14 ttl=52 time=81.720 ms
Request timeout for icmp_seq 15
64 bytes from 106.187.96.148: icmp_seq=16 ttl=52 time=82.190 ms
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19

4 条回复 • 2017-10-04 23:52:35 +08:00

344511554

2017-09-29 14:46:32 +08:00

杭州一样

ggwp

2017-09-29 20:19:13 +08:00

最近联通炸的厉害

mxi1

2017-09-29 21:31:55 +08:00

PING 106.187.96.148 (106.187.96.148) 56(84) bytes of data.
64 bytes from 106.187.96.148: icmp_seq=1 ttl=52 time=129 ms
64 bytes from 106.187.96.148: icmp_seq=2 ttl=52 time=109 ms
64 bytes from 106.187.96.148: icmp_seq=3 ttl=52 time=116 ms
64 bytes from 106.187.96.148: icmp_seq=4 ttl=52 time=120 ms
64 bytes from 106.187.96.148: icmp_seq=5 ttl=52 time=126 ms
64 bytes from 106.187.96.148: icmp_seq=6 ttl=52 time=121 ms
64 bytes from 106.187.96.148: icmp_seq=7 ttl=52 time=125 ms
64 bytes from 106.187.96.148: icmp_seq=8 ttl=52 time=113 ms
64 bytes from 106.187.96.148: icmp_seq=9 ttl=52 time=127 ms
^C
--- 106.187.96.148 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8008ms
rtt min/avg/max/mdev = 109.800/121.090/129.093/6.182 ms

hadoop

2017-10-04 23:52:35 +08:00

kddi 线路是不是会炸