江苏电信到 aws 东京炸的很厉害啊

This topic created in 2666 days ago, the information mentioned may be changed or developed.

不是直连么。。。。光缆又断了么

PING 54.150.0.255 (54.150.0.255): 56 data bytes
64 bytes from 54.150.0.255: icmp_seq=0 ttl=229 time=160.566 ms
64 bytes from 54.150.0.255: icmp_seq=1 ttl=229 time=160.391 ms
64 bytes from 54.150.0.255: icmp_seq=2 ttl=229 time=160.389 ms
64 bytes from 54.150.0.255: icmp_seq=3 ttl=229 time=160.242 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
64 bytes from 54.150.0.255: icmp_seq=11 ttl=229 time=256.605 ms
Request timeout for icmp_seq 12
64 bytes from 54.150.0.255: icmp_seq=13 ttl=229 time=225.067 ms
Request timeout for icmp_seq 14
64 bytes from 54.150.0.255: icmp_seq=15 ttl=229 time=233.080 ms
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
^C
--- 54.150.0.255 ping statistics ---
21 packets transmitted, 7 packets received, 66.7% packet loss
round-trip min/avg/max/stddev = 160.242/193.763/256.605/39.511 ms

icmp_seq

54.150.0.255

request

timeout

16 replies • 2019-02-08 19:22:21 +08:00

CernetBoom

Feb 7, 2019 via Android

先发 MTR

txydhr

Feb 7, 2019

traceroute to 54.150.0.255 (54.150.0.255), 64 hops max, 52 byte packets
1 192.168.1.1 1.881 ms 1.280 ms 1.423 ms
2 49.86.24.1 (49.86.24.1) 5.666 ms 23.425 ms 5.528 ms
3 58.220.107.169 (58.220.107.169) 6.152 ms 6.642 ms 7.867 ms
4 58.220.105.129 (58.220.105.129) 7.138 ms 6.408 ms 7.862 ms
5 202.97.27.13 (202.97.27.13) 12.980 ms 15.119 ms 15.785 ms
6 202.97.50.222 (202.97.50.222) 10.340 ms 10.634 ms 11.938 ms
7 202.97.33.154 (202.97.33.154) 12.829 ms 12.328 ms 12.839 ms
8 202.97.6.62 (202.97.6.62) 38.724 ms 37.203 ms 38.124 ms
9 203.215.236.34 (203.215.236.34) 106.852 ms
203.215.236.38 (203.215.236.38) 106.867 ms 106.827 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * 52.95.31.71 (52.95.31.71) 162.818 ms
20 52.95.31.165 (52.95.31.165) 163.493 ms
52.95.31.175 (52.95.31.175) 311.054 ms
52.95.31.211 (52.95.31.211) 93.985 ms
21 * 52.95.31.188 (52.95.31.188) 98.178 ms
52.95.31.204 (52.95.31.204) 95.954 ms
22 52.95.31.120 (52.95.31.120) 99.841 ms
52.95.31.122 (52.95.31.122) 132.215 ms 121.151 ms
23 52.95.30.220 (52.95.30.220) 97.286 ms
52.95.30.208 (52.95.30.208) 108.778 ms *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 54.150.0.255 (54.150.0.255) 158.396 ms 76.222 ms 76.465 ms

CernetBoom

Feb 7, 2019 via Android

@txydhr 还有回向

hlz0812

Feb 7, 2019 via iPhone

无锡电信表示，ip 池里有些 ip 走 163，有些走 ntt （都是说的回程，去程都是 163 ）
180 开头的就是 ntt，114 开头就是 163，公网 ip 根据需求随意换 ip 段

txydhr

Feb 7, 2019

@hlz0812 ec2-reachability.amazonaws.com 里面一段一段测试么

txydhr

Feb 7, 2019

@hlz0812 发现了，往江苏电信的 ip 都是走的 ntt，用上海电信的 ip 测试都是出了 aws 就直接进 163 了，应该还是 aws 自己路由表的问题？

xencdn

Feb 7, 2019

--- 54.150.0.255 ping statistics ---
15 packets transmitted, 15 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 51.739/56.276/59.884/3.550 ms

湖南长沙电信

txydhr

Feb 7, 2019

@hlz0812 试了好久，自己家 ip 全都是走 ntt，没有例外，ping 150ms+！上海电信的 ip 全都走的直连也没有例外！坑死了

hlz0812

Feb 7, 2019 via iPhone

@txydhr 无锡电信 ip 池多，114.223-114.225 ，180.112-180.114 ，117.84-117.85 ，221.227 ，218.90 ，58.214 ，58.219 ，121.235 ，121.238 ，49.66 ，49.76 ，222.191 等都是，但是现在每个局端没那么多段能拿了，以前基本所有的都能拿到，现在能拿到哪一段跟你家在哪有关

txydhr

Feb 7, 2019 via iPhone

@hlz0812 同一个运营商不同待遇好气哦

txydhr

Feb 7, 2019 via iPhone

@txydhr 首尔新加坡也是走 ntt 😠

hlz0812

Feb 7, 2019 via iPhone

@txydhr 我这边自己换 ip 段就行，如果你那里锁 C 段就没办法了，路由是集团公司统一协调，跟分公司没关系