hosthatch的新加坡网络被调整了

pqpq

叼,确实联通现在没法用了,搞什么鬼...

yywudi

不知道在干啥，到azsg都tm 300多ms

烟火

阿三这难道不是基操么?

pqpq

hh 这操作无语了,线路直接给废了!

xiaodongus

废了

PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=50 time=2760 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=50 time=2703 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=50 time=2330 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=50 time=2395 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=50 time=2769 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=50 time=2547 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=50 time=2221 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=50 time=1945 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=50 time=1742 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=50 time=1825 ms
^C
--- 1.1.1.1 ping statistics ---
13 packets transmitted, 10 received, 23% packet loss, time 12000ms
rtt min/avg/max/mdev = 1742.935/2324.247/2769.144/364.359 ms, pipe 3

xayle

这, 玩蛋
ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=49 time=1377 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=49 time=1307 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=49 time=1256 ms

ping cdn.jsdelivr.net -4
PING  (151.101.193.229) 56(84) bytes of data.
64 bytes from 151.101.193.229 (151.101.193.229): icmp_seq=1 ttl=61 time=2494 ms
64 bytes from 151.101.193.229 (151.101.193.229): icmp_seq=2 ttl=61 time=2067 ms
64 bytes from 151.101.193.229 (151.101.193.229): icmp_seq=3 ttl=61 time=1619 ms

ping cdn.jsdelivr.net -4
PING  (151.101.193.229) 56(84) bytes of data.
64 bytes from 151.101.193.229 (151.101.193.229): icmp_seq=1 ttl=61 time=2494 ms
64 bytes from 151.101.193.229 (151.101.193.229): icmp_seq=2 ttl=61 time=2067 ms
64 bytes from 151.101.193.229 (151.101.193.229): icmp_seq=3 ttl=61 time=1619 ms

ping -4 sg.gs
PING sg.gs (75.2.70.75) 56(84) bytes of data.
64 bytes from aacb0a264e514dd48.awsglobalaccelerator.com (75.2.70.75): icmp_seq=1 ttl=123 time=422 ms
64 bytes from aacb0a264e514dd48.awsglobalaccelerator.com (75.2.70.75): icmp_seq=2 ttl=123 time=0.907 ms
64 bytes from aacb0a264e514dd48.awsglobalaccelerator.com (75.2.70.75): icmp_seq=3 ttl=123 time=0.934 ms

ping -4 fast.com
PING  (118.215.38.206) 56(84) bytes of data.
64 bytes from a118-215-38-206.deploy.static.akamaitechnologies.com (118.215.38.206): icmp_seq=1 ttl=43 time=3598 ms
64 bytes from a118-215-38-206.deploy.static.akamaitechnologies.com (118.215.38.206): icmp_seq=2 ttl=43 time=3518 ms
64 bytes from a118-215-38-206.deploy.static.akamaitechnologies.com (118.215.38.206): icmp_seq=3 ttl=43 time=3364 ms

ping -4 d3888oxgux3fey.cloudfront.net
PING  (65.8.11.67) 56(84) bytes of data.
64 bytes from server-65-8-11-67.kul50.r.cloudfront.net (65.8.11.67): icmp_seq=1 ttl=243 time=1550 ms
64 bytes from server-65-8-11-67.kul50.r.cloudfront.net (65.8.11.67): icmp_seq=2 ttl=243 time=1515 ms
64 bytes from server-65-8-11-67.kul50.r.cloudfront.net (65.8.11.67): icmp_seq=3 ttl=243 time=1251 ms

ping -4 any.pops.fastly-analytics.com
PING any.pops.fastly-analytics.com (151.101.192.207) 56(84) bytes of data.
64 bytes from 151.101.192.207 (151.101.192.207): icmp_seq=1 ttl=61 time=1388 ms
64 bytes from 151.101.192.207 (151.101.192.207): icmp_seq=2 ttl=61 time=1959 ms
64 bytes from 151.101.192.207 (151.101.192.207): icmp_seq=3 ttl=61 time=1770 ms

ping -4 cdnperf.cachefly.net
PING rvip1.g.cachefly.net (205.234.175.175) 56(84) bytes of data.
64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_seq=1 ttl=56 time=1414 ms
64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_seq=2 ttl=56 time=1327 ms
64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_seq=3 ttl=56 time=1285 ms

ping google.com -4
PING  (74.125.24.102) 56(84) bytes of data.
64 bytes from sf-in-f102.1e100.net (74.125.24.102): icmp_seq=1 ttl=61 time=38.8 ms
64 bytes from sf-in-f102.1e100.net (74.125.24.102): icmp_seq=2 ttl=61 time=42.2 ms
64 bytes from sf-in-f102.1e100.net (74.125.24.102): icmp_seq=3 ttl=61 time=28.4 ms

ping -4 media-edge.1e100cdn.net
PING  (34.104.36.46) 56(84) bytes of data.
64 bytes from 46.36.104.34.bc.googleusercontent.com (34.104.36.46): icmp_seq=1 ttl=61 time=39.4 ms
64 bytes from 46.36.104.34.bc.googleusercontent.com (34.104.36.46): icmp_seq=2 ttl=61 time=44.0 ms
64 bytes from 46.36.104.34.bc.googleusercontent.com (34.104.36.46): icmp_seq=3 ttl=61 time=56.4 ms
64 bytes from 46.36.104.34.bc.googleusercontent.com (34.104.36.46): icmp_seq=4 ttl=61 time=44.0 m

pqpq

不知道会不会改回来!!!

yywudi

估计维护崩了，肯定得改回来，这线路这么烂，不怕客户捶死

hardwar

马上发工单开喷

我爱囡囡

hardwar 发表于 2023-5-19 18:33
马上发工单开喷

我都发了几次了