There are some interesting results from the Japanese earthquake of March 11th 2011. Accordingto http://www.renesys.com/blog/2011/03/japan-quake.shtml the big (8.9) one was Friday, March 11, 2011 at 05:46:23 UTC.h3
53cottrell@pinger:~>ping www.tohoku.ac.jp
ping: unknown host www.tohoku.ac.jp
Exit 2
| Code Block |
|---|
53cottrell@pinger:~>ping www.tohoku.ac.jp
ping: unknown host www.tohoku.ac.jpExit 2
|
Also though www.
PingER results
None of the 6 hosts that PingER monitors in Japan went down for an extended period of time (although right now I cannot ping www.kek.jp). Also we do not monitor a Japanese host near the epicenter. Tohoku University (www.tohoku.ac.jp), which were not monitoring previously, on the outskirts of Sendai was not responding on 3/12/2011 12:46pm PST.
60cottrell@pinger:~>ping www.jp.kek
...
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
, pipe 2
Exit 1
Japanese hosts seen From SLAC
# 1. Looking from SLAC there are big increases in the avg RTT and min RTT for some Japanese sites (but not all)
According to http://earthquake.usgs.gov/earthquakes/eqinthenews/2011/usc0001xgp/ the big (8.9) one was Friday, March 11, 2011 at 05:46:23 
RIKEN seen from the world
# UTC
2. 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 RTTwe RTT we see:
a. ## No effect seen from Africa, E. Asia, Europe, L. America, M. East
b. ## Big effect from N. America (Canada 163ms=>264ms, US 120ms=>280ms)
c. ## India CDAC Mumbia no effect, Pune 380ms=> 460ms, VSNL Mumbia 360ms=>400ms
d. ## Sri Lanka no effect
d. ## Pakistan (we have lots of monitors so should be interesting).
i. ### NIIT sees no effect (nb not on PERN)
ii. ### The PERN nodes starting with 111. (apart from UAAR see later) see 420ms=>500ms
iii. ### The PERN nodes starting with 121. See no effect
iv. I am suspicious of UAAR since every other Pakistan node has 400+ms to RIKEN whereas UAAR has 190ms. Someone should look at this.
Conclusion It is not the site RIKEN that has gone bad, rather it is some of the routes
3.
Japanese hosts seen from JP.RIKEN.N3 (RIKEN) see no impact on RTT
It looks the route to Japan not Japan itself. I wonder if the undersea earthquake has disrupted some cables?
Routes
Comparing the routes (see below) from SLAC of RIKEN (ping.riken.jp) and 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
...
Does someone want to put together a case study? I have to do my taxes!
Traceroutes
===========
53cottrell@pinger:~>traceroute ping.riken.jp 200
traceroute to snoopy.riken.go.jp (134.160.4.17), 30 hops max, 200 byte packets
1 rtr-servcore1-serv01-iepm (134.79.104.66) 0.326 ms 0.260 ms 0.235 ms
2 rtr-core2-p2p-servcore1 (134.79.252.162) 0.355 ms 0.272 ms 0.261 ms
3 rtr-border2-p2p-core2 (134.79.252.145) 0.536 ms 0.359 ms 0.330 ms
4 slac-mr2-p2p-rtr-border2 (192.68.191.249) 0.250 ms 0.229 ms 0.237 ms
5 sunnsdn2-ip-slacmr2.es.net (134.55.217.2) 0.629 ms 0.649 ms 0.632 ms
6 sunncr1-sunnsdn2.es.net (134.55.209.98) 0.778 ms 0.739 ms 0.712 ms
7 denvcr2-sunncr1.es.net (134.55.220.49) 28.295 ms 27.861 ms 27.889 ms
MPLS Label=321392 CoS=6 TTL=1 S=0
8 kanscr1-ip-denvcr2.es.net (134.55.209.46) 41.048 ms 40.982 ms 41.033 ms
MPLS Label=357088 CoS=6 TTL=1 S=0
9 chiccr1-ip-kanscr1.es.net (134.55.221.58) 51.719 ms 51.627 ms 51.637 ms
MPLS Label=302528 CoS=6 TTL=1 S=0
10 clevcr1-ip-chiccr1.es.net (134.55.217.53) 60.673 ms 60.652 ms 60.673 ms
MPLS Label=366704 CoS=6 TTL=1 S= 0
11 bostcr1-ip-clevcr1.es.net (134.55.41.146) 73.838 ms 73.778 ms 73.818 ms
MPLS Label=363424 CoS=6 TTL=1 S=0
12 aofacr2-ip-bostcr1.es.net (134.55.41.122) 78.534 ms 78.530 ms 78.535 ms
MPLS Label=300768 CoS=6 TTL=1 S=0
13 aofasdn1-ip-aofacr2.es.net (134.55.38.50) 83.867 ms 78.413 ms 78.403 ms
14 198.124.216.154 (198.124.216.154) 79.404 ms 78.533 ms 78.537 ms
15 tokyo1-dc-RM-P-2-3-0-11.sinet.ad.jp (150.99.203.57) 270.323 ms 270.283 ms 270.250 ms
16 * * *
17 riken-LAN.gw.sinet.ad.jp (150.99.192.170) 277.472 ms 277.412 ms 277.447 ms
18 134.160.6.2 (134.160.6.2) 277.686 ms 277.544 ms 277.833 ms
19 snoopy.riken.go.jp (134.160.4.17) 277.362 ms !<10> 277.415 ms !<10> 277.415 ms !<10>
55cottrell@pinger:~>traceroute ns.jp.apan.net
...