[173986] in North American Network Operators' Group
Re: Is LinkedIn down?
daemon@ATHENA.MIT.EDU (stuart clark)
Sat Aug 16 15:43:52 2014
X-Original-To: nanog@nanog.org
Date: Sat, 16 Aug 2014 18:49:18 +0100
From: stuart clark <stuarteclark@yahoo.com>
To: Frank Bulk <frnkblk@iname.com>, "nanog@nanog.org" <nanog@nanog.org>
In-Reply-To: <000201cfb977$41f07c40$c5d174c0$@iname.com>
Reply-To: stuart clark <stuarteclark@yahoo.com>
Errors-To: nanog-bounces@nanog.org
Frank,=0A=0AReverse is ok from L3's looking glass in Washington. SRC prefix=
for our London DC is 108.171.128.0/24.=0A=0ACheers!=0AOn Saturday, 16 Augu=
st 2014, 18:26, Frank Bulk <frnkblk@iname.com> wrote:=0A =0A=0A=0AStuart,=
=0A=C2=A0=0AYou haven=E2=80=99t shared your IPs but you could go to Level3=
=E2=80=99s Washington Looking Glass and see if you can trace back to your U=
K and Frankfurt IPs.=0A=C2=A0=0AFrank=0A=C2=A0=0AFrom:stuart clark [mailto:=
stuarteclark@yahoo.com] =0ASent: Saturday, August 16, 2014 11:45 AM=0ATo: F=
rank Bulk; nanog@nanog.org=0ASubject: Re: Is LinkedIn down?=0A=C2=A0=0AThan=
ks Frank - www.linkedin.com is the one i see problems with testing from two=
locations UK and Frankfurt. London TR is below.=0AIf i jump out of our AMS=
location (ASN109 - via AS1299=C2=A0) i dont see any problems.=0A=C2=A0=0A[=
root@ops-netops-util1 ~]# tcptraceroute linkedin.com=0ASelected device eth0=
, address 10.3.4.38, port 42311 for outgoing packets=0ATracing the path to =
linkedin.com (216.52.242.86) on TCP port 80 (http), 30 hops max=0A=C2=A0=0A=
[removed]=0A=C2=A0=0A=C2=A06 =C2=A0xe-5-0-0.edge5.London1.Level3.net (212.1=
87.138.209) =C2=A01.078 ms =C2=A01.040 ms =C2=A01.159 ms=0A=C2=A07 =C2=A0* =
* *=0A=C2=A08 =C2=A0ae-56-221.ebr2.London1.Level3.net (4.69.153.129) =C2=A0=
76.147 ms =C2=A075.863 ms =C2=A075.901 ms=0A=C2=A09 =C2=A0* * *=0A10 =C2=A0=
* * *=0A11 =C2=A0ae-48-48.ebr2.Washington1.Level3.net (4.69.202.61) =C2=A07=
5.557 ms =C2=A075.550 ms =C2=A075.511 ms=0A12 =C2=A0ae-82-82.csw3.Washingto=
n1.Level3.net (4.69.134.154) =C2=A075.700 ms =C2=A075.502 ms =C2=A075.644 m=
s=0A13 =C2=A0ae-3-80.edge3.Washington4.Level3.net (4.69.149.146) =C2=A075.6=
39 ms =C2=A075.726 ms =C2=A075.692 ms=0A14 =C2=A0LINKEDIN-CO.edge3.Washingt=
on4.Level3.net (4.53.116.150) =C2=A075.888 ms =C2=A075.924 ms =C2=A075.912 =
ms=0A15 =C2=A0* * *=0A16 =C2=A0* * *=0A17 =C2=A0* * *=0A18 =C2=A0* * *=0A19=
=C2=A0199.101.162.230 =C2=A0149.661 ms =C2=A0151.158 ms =C2=A0149.616 ms=
=0A20 =C2=A0careers.linkedin.com (216.52.242.86) [open] =C2=A0149.264 ms =
=C2=A0149.369 ms =C2=A0149.448 ms=0A=C2=A0=0A=C2=A0=0A[root@ops-netops-util=
1 ~]# tcptraceroute www.linkedin.com=0ASelected device eth0, address 10.3.4=
.38, port 57760 for outgoing packets=0ATracing the path to www.linkedin.com=
(108.174.2.129) on TCP port 80 (http), 30 hops max=0A=C2=A0=0A[removed]=0A=
=C2=A0=0A=C2=A05 =C2=A0xe-5-0-0.edge5.London1.Level3.net (212.187.138.209) =
=C2=A01.060 ms =C2=A01.082 ms =C2=A01.041 ms=0A=C2=A06 =C2=A0* * *=0A=C2=A0=
7 =C2=A0ae-58-223.ebr2.London1.Level3.net (4.69.153.137) =C2=A075.830 ms =
=C2=A075.929 ms =C2=A075.739 ms=0A=C2=A08 =C2=A0* * *=0A=C2=A09 =C2=A0* * *=
=0A10 =C2=A0ae-47-47.ebr2.Washington1.Level3.net (4.69.202.57) =C2=A075.950=
ms =C2=A076.001 ms =C2=A075.942 ms=0A11 =C2=A0* ae-82-82.csw3.Washington1.=
Level3.net (4.69.134.154) 75.713 ms =C2=A075.589 ms=0A12 =C2=A0ae-3-80.edge=
3.Washington4.Level3.net (4.69.149.146) =C2=A075.702 ms =C2=A075.769 ms =C2=
=A075.748 ms=0A13 =C2=A0LINKEDIN-CO.edge3.Washington4.Level3.net (4.53.116.=
150) =C2=A075.973 ms =C2=A075.924 ms =C2=A076.664 ms=0A14 =C2=A0* * *=0A15 =
=C2=A0* * *=0A[timesouts]=0A=C2=A0=0ACheers!=0A=C2=A0=0A-SC (ASN25605)=0A=
=C2=A0=0AOn Saturday, 16 August 2014, 17:03, Frank Bulk <frnkblk@iname.com>=
wrote:=0A=C2=A0=0AStuart,=0A=0AYou don't tell us if it's www.linkedin.com =
or linkedin.com, but in any case,=0Abecause they serve up that site around =
the world using some form of GLB it=0Amay resolve to different IP depending=
on where you are.=C2=A0 From my perspective=0Ait is working via Cogent, an=
d I can hit 108.174.2.129, too:=0A=0Aroot@nagios:# tcptraceroute www.linked=
in.com=0ASelected device eth0.3, address 96.31.0.5, port 43355 for outgoing=
packets=0ATracing the path to www.linkedin.com (199.101.163.129) on TCP po=
rt 80 (www),=0A30 hops max=0A1=C2=A0 router-core-inside.mtcnet.net (96.31.0=
.254)=C2=A0 0.253 ms=C2=A0 0.193 ms=C2=A0 0.203=0Ams=0A2=C2=A0 sxct.sxcy.mt=
cnet.net (167.142.156.197)=C2=A0 0.194 ms=C2=A0 0.131 ms=C2=A0 0.129 ms=0A3=
=C2=A0 premier.sxcy-mlx.fbnt.netins.net (173.215.60.5)=C2=A0 1.632 ms=C2=A0=
1.601 ms=0A1.583 ms=0A4=C2=A0 38.104.184.26=C2=A0 7.004 ms=C2=A0 6.373 ms=
=C2=A0 6.437 ms=0A5=C2=A0 te0-0-1-1.rcr11.dsm01.atlas.cogentco.com (38.104.=
184.25)=C2=A0 5.913 ms=0A6.083 ms=C2=A0 5.877 ms=0A6=C2=A0 te0-2-0-0.ccr41.=
ord01.atlas.cogentco.com (154.54.46.237)=C2=A0 13.057 ms=0A13.114 ms=C2=A0 =
13.075 ms=0A7=C2=A0 be2156.ccr21.mci01.atlas.cogentco.com (154.54.6.85)=C2=
=A0 24.995 ms=C2=A0 24.942=0Ams=C2=A0 25.053=0A ms=0A8=C2=A0 be2012.ccr21.d=
fw01.atlas.cogentco.com (154.54.2.114)=C2=A0 35.013 ms=C2=A0 34.942=0Ams=C2=
=A0 34.928 ms=0A9=C2=A0 be2144.ccr21.iah01.atlas.cogentco.com (154.54.25.10=
5)=C2=A0 40.455 ms=C2=A0 40.749=0Ams=C2=A0 40.709 ms=0A10=C2=A0 be2065.ccr2=
1.lax01.atlas.cogentco.com (154.54.5.66)=C2=A0 76.269 ms=C2=A0 76.119=0Ams=
=C2=A0 75.970 ms=0A11=C2=A0 * * *=0A12=C2=A0 154.24.22.126=C2=A0 76.351 ms=
=C2=A0 76.296 ms=C2=A0 76.257 ms=0A13=C2=A0 38.88.244.2=C2=A0 73.135 ms=C2=
=A0 73.101 ms=C2=A0 73.182 ms=0A14=C2=A0 border1.po1-20g-bbnet1.lax008.pnap=
.net (216.52.255.46)=C2=A0 73.354 ms=0A73.355 ms=C2=A0 73.585 ms=0A15=C2=A0=
linkedin-16.border1.lax008.pnap.net (216.52.220.122)=C2=A0 74.017 ms=C2=A0=
74.005=0Ams=C2=A0=0A 73.965 ms=0A16=C2=A0 * * *=0A17=C2=A0 199.101.162.226=
=C2=A0 74.766 ms=C2=A0 74.391 ms=C2=A0 74.582 ms=0A18=C2=A0 199.101.163.129=
[open]=C2=A0 74.528 ms=C2=A0 74.381 ms=C2=A0 74.421 ms=0Aroot@nagios:#=0A=
=0A=0Aroot@nagios:/# tcptraceroute 108.174.2.129=0ASelected device eth0.3, =
address 96.31.0.5, port 49338 for outgoing packets=0ATracing the path to 10=
8.174.2.129 on TCP port 80 (www), 30 hops max=0A1=C2=A0 router-core-inside.=
mtcnet.net (96.31.0.254)=C2=A0 0.295 ms=C2=A0 0.210 ms=C2=A0 0.237=0Ams=0A2=
=C2=A0=0A sxct.spnc.mtcnet.net (167.142.156.194)=C2=A0 0.206 ms=C2=A0 0.144=
ms=C2=A0 0.129 ms=0A3=C2=A0 premier.spnc-mlx.fbnt.netins.net (173.215.60.1=
)=C2=A0 15.282 ms=C2=A0 4.743 ms=0A4.750 ms=0A4=C2=A0 ins-kb3-et-0-7-0-0.km=
rr.netins.net.67.142.167.in-addr.arpa=0A(167.142.67.50)=C2=A0 8.787 ms=C2=
=A0 8.705 ms=C2=A0 8.505 ms=0A5=C2=A0 ins-kc2-et-9-3.kmrr.netins.net (167.1=
42.67.49)=C2=A0 7.170 ms=C2=A0 7.183 ms=0A7.189 ms=0A6=C2=A0 ins-dc1-po20.d=
esm.netins.net (167.142.67.29)=C2=A0 7.623 ms=C2=A0 8.936 ms=C2=A0 8.135=0A=
ms=0A7=C2=A0 207.87.180.149=C2=A0 12.733 ms=C2=A0 52.226 ms=C2=A0 12.740 ms=
=0A8=C2=A0 ae1d0.mcr1.minneapolis-mn.us.xo.net (216.156.1.85)=C2=A0 23.368 =
ms=C2=A0 22.132 ms=0A22.052 ms=0A9=C2=A0 vb1710.rar3.chicago-il.us.xo.net=
=0A (216.156.0.169)=C2=A0 22.984 ms=C2=A0 23.536 ms=0A24.016 ms=0A10=C2=A0 =
207.88.14.194.ptr.us.xo.net (207.88.14.194)=C2=A0 21.861 ms=C2=A0 21.882 ms=
=0A21.880 ms=0A11=C2=A0 206.111.2.65.ptr.us.xo.net (206.111.2.65)=C2=A0 23.=
583 ms=C2=A0 22.722 ms=C2=A0 22.876=0Ams=0A12=C2=A0 ae-8.r05.chcgil09.us.bb=
.gin.ntt.net (129.250.4.221)=C2=A0 22.630 ms=C2=A0 22.751=0Ams=C2=A0 22.817=
ms=0A13=C2=A0 165.254.191.82=C2=A0 22.760 ms=C2=A0 22.726 ms=C2=A0 22.722 =
ms=0A14=C2=A0 * * *=0A15=C2=A0 * * *=0A16=C2=A0 108.174.2.129 [open]=C2=A0 =
36.065 ms=C2=A0 36.058 ms=C2=A0 36.042 ms=0Aroot@nagios:/#=0A=0A=0Aroot@nag=
ios:/usr/lib/nagios/plugins# ./check_http -H www.linkedin.com -I=0A199.101.=
163.129=0AHTTP OK: HTTP/1.1 301 Moved Permanently - 1706 bytes in 0.167 sec=
ond=0Aresponse time |time=3D0.166917s;;;0.000000 size=3D1706B;;;0=0Aroot@na=
gios:/usr/lib/nagios/plugins#=0Aroot@nagios:/usr/lib/nagios/plugins# ./chec=
k_http -H www.linkedin.com -I=0A108.174.2.129=0AHTTP OK: HTTP/1.1 301 Moved=
Permanently - 1702 bytes in 0.088 second=0Aresponse time |time=3D0.088261s=
;;;0.000000 size=3D1702B;;;0=0Aroot@nagios:/usr/lib/nagios/plugins#=0A=0ARe=
gards,=0A=0AFrank=0A=0A-----Original Message-----=0AFrom: NANOG [mailto:nan=
og-bounces@nanog.org] On Behalf Of stuart clark=0ASent: Saturday, August 16=
, 2014 10:30 AM=0ATo: nanog@nanog.org=0ASubject: Is LinkedIn down?=0A=0ATra=
ce/tcptrace to 108.174.2.129 =C2=A0via Level3 - last hop is on the=0ALinked=
/Level3 edge:=0A=0A14 =C2=A0LINKEDIN-CO.edge3.Washington4.Level3.net (4.53.=
116.150) =C2=A076.034 ms=0A=C2=A076.069 ms =C2=A076.066 ms=0A=0A=0AVia=C2=
=A0telia.net=0A=0A=C2=A016 =C2=A0 236 ms =C2=A0 221 ms =C2=A0 =C2=A0 * =C2=
=A0 =C2=A0 linkedin-ic-301441-ash-b1.c.telia.net=0A[213.248.103.190]=0A=C2=
=A017 =C2=A0 =C2=A0 * =C2=A0 =C2=A0 =C2=A0 =C2=A0* =C2=A0 =C2=A0 =C2=A0 =C2=
=A0* =C2=A0 =C2=A0 Request timed out.=0A=C2=A018 =C2=A0 259 ms =C2=A0 265 m=
s =C2=A0 =C2=A0 * =C2=A0 =C2=A0 108.174.2.129=0A=C2=A019 =C2=A0 257 ms=0A =
=C2=A0 299 ms =C2=A0 256 ms =C2=A0108.174.2.129=0A=0ANo reply from LinkedIn=
support, but i see plenty of Verizon and Level3=0Acustomers cannot access =
LinkedIn for 24 hrs.=0A216.52.242.113 works ok.=0A=0A=0A-SC (ASN25605)
