...
From 134.79.252.133 icmp_seq=114 Destination Host Unreachable
-- - 130.87.104.107 ping statistics - --
121 packets transmitted, 0 received, +4 errors, 100% packet loss, time 119996ms
...
RIKEN seen from the world
# Looking at RIKEN (a monitoring mode and so easy to select on and also one of the most affected as seen from SLAC) seen from the world looking at avg RTT and min RTT we see:##
- No effect seen from Africa, E. Asia, Europe, L. America, M.
...
- East
...
- Big effect from N. America (Canada 163ms=>264ms, US 120ms=>280ms)
...
- India CDAC Mumbia no effect, Pune 380ms=> 460ms, VSNL Mumbia 360ms=
...
- >400ms
...
- Sri Lanka no
...
- effect
...
- Pakistan (we have lots of monitors so should be interesting).
...
- NIIT sees no effect (nb not on PERN)
...
- The PERN (Pakistan Education and Research Network) nodes starting with 111. (apart from UAAR see later, this needs more investigation) see 420ms=
...
- >500ms
...
- The PERN nodes starting with 121. See no
...
- effect
...
Conclusion It is not the site RIKEN that has gone bad, rather it is some of the routes
RIKEN Looking at Japan
Japanese hosts seen from JP.RIKEN.N3 (RIKEN) see no impact on RTT
It looks the problem is in the route to Japan not within Japan itself. I wonder if the undersea earthquake has disrupted some cables?
...
Comparing the routes from SLAC of to RIKEN (ping.riken.jp) and from SLAC to NET.APAN.N2 (ns.jp.apan.net) we see RIKEN has more hops and goes Eastwards via the Avenue of the Americas in NY, while APAN goes directly via Sunnyvale near SLAC and then via Pacific Wave directly to Japan. OSAKA and U-TOKYO are similar to RIKEN. See below
...