[173982] in North American Network Operators' Group
Re: Is LinkedIn down?
daemon@ATHENA.MIT.EDU (stuart clark)
Sat Aug 16 12:45:11 2014
X-Original-To: nanog@nanog.org
Date: Sat, 16 Aug 2014 17:45:01 +0100
From: stuart clark <stuarteclark@yahoo.com>
To: Frank Bulk <frnkblk@iname.com>, "nanog@nanog.org" <nanog@nanog.org>
In-Reply-To: <000001cfb96b$97aa8dd0$c6ffa970$@iname.com>
Reply-To: stuart clark <stuarteclark@yahoo.com>
Errors-To: nanog-bounces@nanog.org
Thanks 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=A0) i dont see any problems.=0A=0A[root@=
ops-netops-util1 ~]# tcptraceroute linkedin.com=0ASelected device eth0, add=
ress 10.3.4.38, port 42311 for outgoing packets=0ATracing the path to linke=
din.com (216.52.242.86) on TCP port 80 (http), 30 hops max=0A=0A[removed]=
=0A=0A=A06 =A0xe-5-0-0.edge5.London1.Level3.net (212.187.138.209) =A01.078 =
ms =A01.040 ms =A01.159 ms=0A=A07 =A0* * *=0A=A08 =A0ae-56-221.ebr2.London1=
.Level3.net (4.69.153.129) =A076.147 ms =A075.863 ms =A075.901 ms=0A=A09 =
=A0* * *=0A10 =A0* * *=0A11 =A0ae-48-48.ebr2.Washington1.Level3.net (4.69.2=
02.61) =A075.557 ms =A075.550 ms =A075.511 ms=0A12 =A0ae-82-82.csw3.Washing=
ton1.Level3.net (4.69.134.154) =A075.700 ms =A075.502 ms =A075.644 ms=0A13 =
=A0ae-3-80.edge3.Washington4.Level3.net (4.69.149.146) =A075.639 ms =A075.7=
26 ms =A075.692 ms=0A14 =A0LINKEDIN-CO.edge3.Washington4.Level3.net (4.53.1=
16.150) =A075.888 ms =A075.924 ms =A075.912 ms=0A15 =A0* * *=0A16 =A0* * *=
=0A17 =A0* * *=0A18 =A0* * *=0A19 =A0199.101.162.230 =A0149.661 ms =A0151.1=
58 ms =A0149.616 ms=0A20 =A0careers.linkedin.com (216.52.242.86) [open] =A0=
149.264 ms =A0149.369 ms =A0149.448 ms=0A=0A=0A[root@ops-netops-util1 ~]# t=
cptraceroute www.linkedin.com=0ASelected device eth0, address 10.3.4.38, po=
rt 57760 for outgoing packets=0ATracing the path to www.linkedin.com (108.1=
74.2.129) on TCP port 80 (http), 30 hops max=0A=0A[removed]=0A=0A=A05 =A0xe=
-5-0-0.edge5.London1.Level3.net (212.187.138.209) =A01.060 ms =A01.082 ms =
=A01.041 ms=0A=A06 =A0* * *=0A=A07 =A0ae-58-223.ebr2.London1.Level3.net (4.=
69.153.137) =A075.830 ms =A075.929 ms =A075.739 ms=0A=A08 =A0* * *=0A=A09 =
=A0* * *=0A10 =A0ae-47-47.ebr2.Washington1.Level3.net (4.69.202.57) =A075.9=
50 ms =A076.001 ms =A075.942 ms=0A11 =A0* ae-82-82.csw3.Washington1.Level3.=
net (4.69.134.154) 75.713 ms =A075.589 ms=0A12 =A0ae-3-80.edge3.Washington4=
.Level3.net (4.69.149.146) =A075.702 ms =A075.769 ms =A075.748 ms=0A13 =A0L=
INKEDIN-CO.edge3.Washington4.Level3.net (4.53.116.150) =A075.973 ms =A075.9=
24 ms =A076.664 ms=0A14 =A0* * *=0A15 =A0* * *=0A[timesouts]=0A=0ACheers!=
=0A=0A-SC (ASN25605)=0A=0A=0A=0AOn Saturday, 16 August 2014, 17:03, Frank B=
ulk <frnkblk@iname.com> wrote:=0A =0A=0A=0AStuart,=0A=0AYou don't tell us i=
f it's www.linkedin.com or linkedin.com, but in any case,=0Abecause they se=
rve up that site around the world using some form of GLB it=0Amay resolve t=
o different IP depending on where you are.=A0 From my perspective=0Ait is w=
orking via Cogent, and I can hit 108.174.2.129, too:=0A=0Aroot@nagios:# tcp=
traceroute www.linkedin.com=0ASelected device eth0.3, address 96.31.0.5, po=
rt 43355 for outgoing packets=0ATracing the path to www.linkedin.com (199.1=
01.163.129) on TCP port 80 (www),=0A30 hops max=0A1=A0 router-core-inside.m=
tcnet.net (96.31.0.254)=A0 0.253 ms=A0 0.193 ms=A0 0.203=0Ams=0A2=A0 sxct.s=
xcy.mtcnet.net (167.142.156.197)=A0 0.194 ms=A0 0.131 ms=A0 0.129 ms=0A3=A0=
premier.sxcy-mlx.fbnt.netins.net (173.215.60.5)=A0 1.632 ms=A0 1.601 ms=0A=
1.583 ms=0A4=A0 38.104.184.26=A0 7.004 ms=A0 6.373 ms=A0 6.437 ms=0A5=A0 te=
0-0-1-1.rcr11.dsm01.atlas.cogentco.com (38.104.184.25)=A0 5.913 ms=0A6.083 =
ms=A0 5.877 ms=0A6=A0 te0-2-0-0.ccr41.ord01.atlas.cogentco.com (154.54.46.2=
37)=A0 13.057 ms=0A13.114 ms=A0 13.075 ms=0A7=A0 be2156.ccr21.mci01.atlas.c=
ogentco.com (154.54.6.85)=A0 24.995 ms=A0 24.942=0Ams=A0 25.053 ms=0A8=A0 b=
e2012.ccr21.dfw01.atlas.cogentco.com (154.54.2.114)=A0 35.013 ms=A0 34.942=
=0Ams=A0 34.928 ms=0A9=A0 be2144.ccr21.iah01.atlas.cogentco.com (154.54.25.=
105)=A0 40.455 ms=A0 40.749=0Ams=A0 40.709 ms=0A10=A0 be2065.ccr21.lax01.at=
las.cogentco.com (154.54.5.66)=A0 76.269 ms=A0 76.119=0Ams=A0 75.970 ms=0A1=
1=A0 * * *=0A12=A0 154.24.22.126=A0 76.351 ms=A0 76.296 ms=A0 76.257 ms=0A1=
3=A0 38.88.244.2=A0 73.135 ms=A0 73.101 ms=A0 73.182 ms=0A14=A0 border1.po1=
-20g-bbnet1.lax008.pnap.net (216.52.255.46)=A0 73.354 ms=0A73.355 ms=A0 73.=
585 ms=0A15=A0 linkedin-16.border1.lax008.pnap.net (216.52.220.122)=A0 74.0=
17 ms=A0 74.005=0Ams=A0 73.965 ms=0A16=A0 * * *=0A17=A0 199.101.162.226=A0 =
74.766 ms=A0 74.391 ms=A0 74.582 ms=0A18=A0 199.101.163.129 [open]=A0 74.52=
8 ms=A0 74.381 ms=A0 74.421 ms=0Aroot@nagios:#=0A=0A=0Aroot@nagios:/# tcptr=
aceroute 108.174.2.129=0ASelected device eth0.3, address 96.31.0.5, port 49=
338 for outgoing packets=0ATracing the path to 108.174.2.129 on TCP port 80=
(www), 30 hops max=0A1=A0 router-core-inside.mtcnet.net (96.31.0.254)=A0 0=
.295 ms=A0 0.210 ms=A0 0.237=0Ams=0A2=A0 sxct.spnc.mtcnet.net (167.142.156.=
194)=A0 0.206 ms=A0 0.144 ms=A0 0.129 ms=0A3=A0 premier.spnc-mlx.fbnt.netin=
s.net (173.215.60.1)=A0 15.282 ms=A0 4.743 ms=0A4.750 ms=0A4=A0 ins-kb3-et-=
0-7-0-0.kmrr.netins.net.67.142.167.in-addr.arpa=0A(167.142.67.50)=A0 8.787 =
ms=A0 8.705 ms=A0 8.505 ms=0A5=A0 ins-kc2-et-9-3.kmrr.netins.net (167.142.6=
7.49)=A0 7.170 ms=A0 7.183 ms=0A7.189 ms=0A6=A0 ins-dc1-po20.desm.netins.ne=
t (167.142.67.29)=A0 7.623 ms=A0 8.936 ms=A0 8.135=0Ams=0A7=A0 207.87.180.1=
49=A0 12.733 ms=A0 52.226 ms=A0 12.740 ms=0A8=A0 ae1d0.mcr1.minneapolis-mn.=
us.xo.net (216.156.1.85)=A0 23.368 ms=A0 22.132 ms=0A22.052 ms=0A9=A0 vb171=
0.rar3.chicago-il.us.xo.net (216.156.0.169)=A0 22.984 ms=A0 23.536 ms=0A24.=
016 ms=0A10=A0 207.88.14.194.ptr.us.xo.net (207.88.14.194)=A0 21.861 ms=A0 =
21.882 ms=0A21.880 ms=0A11=A0 206.111.2.65.ptr.us.xo.net (206.111.2.65)=A0 =
23.583 ms=A0 22.722 ms=A0 22.876=0Ams=0A12=A0 ae-8.r05.chcgil09.us.bb.gin.n=
tt.net (129.250.4.221)=A0 22.630 ms=A0 22.751=0Ams=A0 22.817 ms=0A13=A0 165=
.254.191.82=A0 22.760 ms=A0 22.726 ms=A0 22.722 ms=0A14=A0 * * *=0A15=A0 * =
* *=0A16=A0 108.174.2.129 [open]=A0 36.065 ms=A0 36.058 ms=A0 36.042 ms=0Ar=
oot@nagios:/#=0A=0A=0Aroot@nagios:/usr/lib/nagios/plugins# ./check_http -H =
www.linkedin.com -I=0A199.101.163.129=0AHTTP OK: HTTP/1.1 301 Moved Permane=
ntly - 1706 bytes in 0.167 second=0Aresponse time |time=3D0.166917s;;;0.000=
000 size=3D1706B;;;0=0Aroot@nagios:/usr/lib/nagios/plugins#=0Aroot@nagios:/=
usr/lib/nagios/plugins# ./check_http -H www.linkedin.com -I=0A108.174.2.129=
=0AHTTP OK: HTTP/1.1 301 Moved Permanently - 1702 bytes in 0.088 second=0Ar=
esponse time |time=3D0.088261s;;;0.000000 size=3D1702B;;;0=0Aroot@nagios:/u=
sr/lib/nagios/plugins#=0A=0ARegards,=0A=0AFrank=0A=0A-----Original Message-=
----=0AFrom: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of stuart cla=
rk=0ASent: Saturday, August 16, 2014 10:30 AM=0ATo: nanog@nanog.org=0ASubje=
ct: Is LinkedIn down?=0A=0ATrace/tcptrace to 108.174.2.129 =A0via Level3 - =
last hop is on the=0ALinked/Level3 edge:=0A=0A14 =A0LINKEDIN-CO.edge3.Washi=
ngton4.Level3.net (4.53.116.150) =A076.034 ms=0A=A076.069 ms =A076.066 ms=
=0A=0A=0AVia=A0telia.net=0A=0A=A016 =A0 236 ms =A0 221 ms =A0 =A0 * =A0 =A0=
linkedin-ic-301441-ash-b1.c.telia.net=0A[213.248.103.190]=0A=A017 =A0 =A0 =
* =A0 =A0 =A0 =A0* =A0 =A0 =A0 =A0* =A0 =A0 Request timed out.=0A=A018 =A0 =
259 ms =A0 265 ms =A0 =A0 * =A0 =A0 108.174.2.129=0A=A019 =A0 257 ms =A0 29=
9 ms =A0 256 ms =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)
