Is anyone seeing a huge latency jump from Asia Pac to US again?
Sample traceroute:
4 2 ms 1 ms 1 ms 210.13.64.14
5 2 ms 1 ms 4 ms 210.13.64.13
6 2 ms 2 ms 2 ms 218.105.0.69
7 41 ms 35 ms 35 ms 218.105.6.102
8 36 ms 36 ms 36 ms 218.105.5.82
9 36 ms 36 ms 37 ms 210.52.132.230
10 38 ms 39 ms 38 ms 210.53.126.2
11 38 ms 38 ms 39 ms 217.6.49.181
12 * 296 ms 295 ms lax-sa1-i.LAX.US.NET.DTAG.DE [62.154.5.170]
13 1033 ms 1029 ms 1028 ms 192.205.33.101
14 1087 ms 1090 ms 1094 ms cr2.la2ca.ip.att.net [12.122.129.98]
15 1086 ms 1084 ms 1085 ms cr1.slkut.ip.att.net [12.122.30.29]
The above was taken from a user in China tracing to New York about 30 mins ago
It seems that the FNAL system outage at 14:15 GMT+8.
Not sure it is related or not.
cheers,
Ethern
Do you have any more details of the outage? Another cut in the region?
As I know, the FNAL system is down and from Taiwan to Hongkong and
from Japan to Hongkong. But I don't have further info about this
outage now.
cheers,
Ethern
Is anyone seeing a huge latency jump from Asia Pac to US again?
<snip>
The above was taken from a user in China tracing to New York about 30 mins ago
There was another earthquake today in Asia, this one between Japan and Taiwan. Is this possibly related?
Randy
Randy Epstein wrote:
Is anyone seeing a huge latency jump from Asia Pac to US again?
<snip>
The above was taken from a user in China tracing to New York about 30 mins ago
There was another earthquake today in Asia, this one between Japan and Taiwan. Is this possibly related?
Randy
Just got word that TGN-1 near Taiwan has been cut off the coast of Taiwan.
--J
All I know the un-damaged cable systems are: TPE and C2C.
The outage cause f FNAL is debris flow as the same as 8/7.
Please have more info supplmented if you have.
cheers,
Ethern